We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
What could be the problem if a code doesn't start the main function at the beginning? My code does start the function after the main function (if I take a look into the map-file) - the usart in the line 19.
0x100002dc 0x000000e0 Code RO 12 .text main.o 0x100003bc 0x000000d8 Code RO 46 .text usart.o
A part of the memory map of the external flash.
Which part of the whole code could overwrite the flash memory - the variables are not initialize at this moment are they? Could that be a pointer which is not correct initialized in a lib function?
Paul
Have you tried to set a breakpoint in the startup code No but I will test it tomorrow.
A lot of strange things can happen if you get a stack overflow
that's true, but I take a look in the memory window, too - and there's no stack overflow...
thanks for your hints...