As Bob Paddock wrote: > > 0x0003c370 __data_load_start = LOADADDR (.data) > > 0x0003c378 __data_load_end = (__data_load_start + SIZEOF (.data))
> My map files has: > 0x0000ff22 __data_load_start = LOADADDR (.data) > 0x0000ffc0 __data_load_end = > I'm not seeing how to deduce any particular width out of either of > those examples? That's because your addresses are /just/ below the 64 KiB boundary, so obviously, you cannot tell it's really going to be a 32-bit value. In my example, you can, as it (severely) overflows the 64 KiB range. (I tried to mockup some example that is for sure going to be large enough. Hacking around with volatile uint64_t data quickly leads to success here. ;) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev