In November, we had a problem that the program runs away, but this was caused by a wrong debugger start address which was set in the example.
We got the advice to change the debug start address to 0xffff0000, and this solved the problem.
At the moment we extended the team and start using more Evaluation Boards.The problem is that 3 of the 6 boards we have still have (about the same) problem.
When we start the program, it runs away soon (loops at 0xffff0004).
If we click the debug reset button (in e2Studio), it stops (now at address 0x21000000, vector_table) and we can start it.Then it runs for a few C statements and function calls, and then runs away, somewhere around address 0x230c0000 (many 'addeq r0, r0, r0' instructions, thus 'nonsense').
When I step through the few C statemensts, one time I saw near a instruction 'bx lr' that it jumped to another address then the contents of lr.
Strange things happen.
Is something not correctly initialized that it depends on 'random' contents of memory in the boards ?Or is there indeed a known issue with this.Our program came from 'blinky osless', but we think it is a problem in the hardware / debug environment.
We hope to get a solution