diff options
| author | Tarek BOCHKATI <tarek.bouchkati@gmail.com> | 2022-02-28 13:55:26 +0100 |
|---|---|---|
| committer | Antonio Borneo <borneo.antonio@gmail.com> | 2022-03-19 09:13:55 +0000 |
| commit | ab43721be6ff7470ff8b9771c95c1d5661a5a689 (patch) | |
| tree | 0a719e9d31fb384b2103fbb4add9bdf94933c181 /src/target/arc.c | |
| parent | 9cdbe61aab418bdf75bc443b16ce4cdf96732e3e (diff) | |
| download | riscv-openocd-ab43721be6ff7470ff8b9771c95c1d5661a5a689.zip riscv-openocd-ab43721be6ff7470ff8b9771c95c1d5661a5a689.tar.gz riscv-openocd-ab43721be6ff7470ff8b9771c95c1d5661a5a689.tar.bz2 | |
flash/stm32l4x: fix auto-probe when RDP is promoted from 0 to 0.5
Considering this use case: (using STM32 L5 or U5)
1- first probe : TZEN enabled, RDP level 0
flash_regs_base |= STM32L5_REGS_SEC_OFFSET => 0x50022000
2- the user promotes the RDP to level 0.5
3- the second probe, fails to read OPTR using secure flags_regs_base:
used OPTR address is 0x50022040
Step 3 fails because when RDP is level 0.5, we should use Non-Secure
flash registers.
To fix this, always use NS flash regs to read OPTR in probe functions.
Fixes: 80d323c6e82b (flash/stm32l4x: introduce auto-probe when OPTR is changed)
Change-Id: I296aa633972b0c410b927488c999584a07b912d3
Signed-off-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Reviewed-on: https://review.openocd.org/c/openocd/+/6864
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
Tested-by: jenkins
Diffstat (limited to 'src/target/arc.c')
0 files changed, 0 insertions, 0 deletions