Honored Contributor
Honored ContributorMy first thought too was stack overflow which is why I cut my code down to just that in Post# 2. There is no other large static data or anything like that. I'm not sure which stack ecos uses while it is booting though and it would have to be this stack which is overflowing BEFORE the cyg_start routine is called much less the cyg_user_start. I see sizes for the interrupt and idle stack, which is used for startup? I doubled the idle stack size with no effect.
It appears that I have similar behaviour to some other reports, in that it does appear that when I fail to boot I am running code from the flash. My flash is currently completely erased but if I halt the debugger I get an address within the flash memory region. Looking at Post# 2 code, I don't know if it actually the addition of the lines which is causing problems or just some random problem that manifests itself based on the built image size or data somehow. This is especially true as this code is not being run. I see a new post with what I believe will be a similar issue as well. Thanks for all your help, Stefan
