This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2634-Q1: Data Abort during boot when stack located in OCSRAM BANK 2

Part Number: AM2634-Q1
Other Parts Discussed in Thread: AM2634

We have been developing our application using the AM2634 for some time now. The application memory usage has now grown in size that the main stacks are now located in memory starting from 0x70100000 (OCSRAM BANK 2) by the linker.

If the stacks are relocated in OCSRAM BANK 2, when executing we then get a data abort raised during the blanking of the bss area in the _system_pre_init() in boot_armv7r.c. If we reduce some memory usage so that it all now can fit within OCSRAM BANK 0 and OCSRAM BANK 1 (first 1MB), the application executes without issue.

Is there something to understand regarding using the 2nd hald of the OCRAM? We are executing from Core R5_0 and the MPU is configured to allow the same access to the entire 2MB OCRAM