cancel
Showing results for 
Search instead for 
Did you mean: 

SRAM2 parity checking.

GFalz.1
Associate

I am using an STM32L452CE. I copy an executable (.bin) from Flash to SRAM2. I zero out the remaining SRAM2. I then 'jump' to the executable now in SRAM2. When I have the parity error checking off (FLASH_OPTR_SRAM2_PE = 1) it works fine. When I turn it on it does not work. Any ideas / suggestions would be much appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
I found the issue. The app I am ‘jumping to’ changed the bits in the OPTR register back to disabling parity error checking, so the chip was constantly resetting.
Thanks for your reply though…

View solution in original post

3 REPLIES 3

> it does not work

What are exactly the symptoms?

How do you exactly set the parity checking bit, in the option bytes (i.e. programmed into the nonvolatile area), or in the FLASH_OPTR register?

Try reading after writing to SRAM2, before jumping to it.

JW

I found the issue. The app I am ‘jumping to’ changed the bits in the OPTR register back to disabling parity error checking, so the chip was constantly resetting.
Thanks for your reply though…

Nice catch!

Please select your post as Best so that thread is marked as solved.

JW