Hi Triffid, Thanks for clearing these things up. I am going to try to use your libraries, unfortunately, I couldn't locate them on your website, can you point

Hi Triffid, Sorry, I got the libraries as well as the kernel, thanks a lot for your help. I am going to try using them soon. Jellouli

... printf calls sprintf to format strings, unless they're very simple in which case the call is optimised to simply dump the characters. If you pass it a

x_daveerickson_x, I've modified your source, and it seems to work this way: /** standalone example to flash PE7 LED on Adapt912 (slow); Here is the memory.x: [

... You're right. I didn't look closely at the source, only the object. Jeff, you put in two writes, and the compiler did it twice. I suspect that if the

... Sounds fair to me, esp. if you automate the conversion so people can do it quicker with later GCC releases. Of course for backwards compatibility, I think

I kinda got your test.c to compile. I see that after fixing "memory.x" as I had suggested, it is loading section "pvectors" to the wrong location. At least I

... 43bastian, I guess you are saying that I'm focusing too much on: *((volatile word*) &offset[_eeprom_base]) = 0; 4e98: cc 00 00 ldd #0 4e9b:

The saga with the GEL libraries continues: Hi all!!! I finaolly figured out how to rebuild the "infamous" GEL libraries, and started using them, but now I am

Jeff, ... (*) ... (**) ... This one if for : (*) above. ... This one is for (**). ... Try another address for the (*) line. -- 42Bastian

... [snip] ... Weird! I wonder if it is one per clr in the other code? Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} This message

... As a followup, I found that by using the ar tool, I just unpacked libgcc and did an objcopy --rename-section .text=.nonbank on each object that was

... I finally decided to try your idea with the function from 42Bastian. Using "gcc version 3.3.6-m68hc1x-20060122" (rel 3.1)... It's sure interresting. With

Hi All, I was trying to compile the GCC, I followed the instruction in these link http://www.gnu.org/software/m68hc11/m68hc11_inst_ptc.html or even running the

... For standalone (using only the D-Bug12 bootloader), I used this: MEMORY { page0 (rwx) : ORIGIN = 0x0, LENGTH = 256 eeprom (rx) : ORIGIN = 0x0D00, LENGTH =

... Not quite. For your HC12 it might look like this, which I typically load with the D-Bug12 bootloader.: MEMORY { page0 (rwx) : ORIGIN = 0x0, LENGTH = 256

... OK, thanks. I think I understand, the page0 is a specific region set aside for things like soft registers etc. This chip has 1KRAM so I should rewrite

... Yes, the mystery functions are the .near functions definied in larith.asm which then get compiled in several flavors for libgcc.a. They are premain,

... Real quick I see two strange things you should not do, but I don't know yet what makes your code not work. 1. See, page0 means page0, not "data" or "RAM

Hello; I have had problems getting this to work on my Adapt912 board that uses the MC68HC12B32. I am just trying to turn on the LED at port P 7 and I borrowed