??? 04/12/10 06:36 Read: times Msg Score: +1 +1 Informative |
#174986 - toolchain dependent Responding to: ???'s previous message |
As Andy said above, this is entirely toolchain dependent.
Also, if the data goes to the same FLASH as code, it may be quite easy in the "burning" step, once you solve how to get the data to the output hex. If it would go to say EEPROM which is usually programmed separately, the complexity of the task would increase, as programming tools have different behaviour when it comes to programming both FLASH and EEPROM. JW |
Topic | Author | Date |
Loading Flash EEPROM with defaults | 01/01/70 00:00 | |
this seems to work - any improvements | 01/01/70 00:00 | |
Always a key requirement! | 01/01/70 00:00 | |
toolchain dependent | 01/01/70 00:00 | |
A couple of points | 01/01/70 00:00 | |
volatile | 01/01/70 00:00 | |
separate source | 01/01/70 00:00 | |
So subtle | 01/01/70 00:00 | |
Excel is (also) among your friends | 01/01/70 00:00 | |
Yes missing initialisers do default to 0 | 01/01/70 00:00 | |
My Method... | 01/01/70 00:00 | |
an alternate suggestion (which I use) | 01/01/70 00:00 | |
That uses more memory | 01/01/70 00:00 | |
Oliver ??? | 01/01/70 00:00 | |
I believe that is what most devices do..![]() | 01/01/70 00:00 |