Hi Dmitry,
Isn't that just a workaround? Shouldn't the infomem section just not be
initialised? Initialising it is actually wrong, just as initialising a
memory address that is really a peripheral register is wrong. The RAM
area is only initialised by the startup code. Why isn't infomem like that?
Regards,
Steve
Dmitry wrote:
just do not download data to infomem.
can you make remote command
load [section] ? where section is one of data/dext/infomem/vectors
~d
On Wednesday 04 December 2002 16:19, Steve Underwood wrote:
Hi,
Something like the following:
uint8_t __attribute__((section(".infomem"))) stuff[128];
puts "stuff" into the correct address in info memory. However, it is
initialised to zero. When I download my code to flash it screws the
config data I have in info memory. How can this initialisation be
prevented. It certainly isn't what I want. :-(
Regards,
Steve
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
