New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tools/openocd: check OPENOCD_VERIFY after IMAGE_OFFSET is computed #17251
Conversation
@yarrick could you test that its still works for |
Note that probing the flash (to get the flash size and base address of a bank) doesn't work anymore on nucleo-l073rz with openocd latest master but it works with 0.11.0. |
I've also noticed issues with the newest OpenOCD versions (not the release ones, but master), but haven't looked into it, and it was on stm32wl based BOARDs. |
Should I open an issue for that so we can keep track of the problem ? |
ESP32 still works for me. Sorry for the breakage |
@aabadie the user that opened the issue and discourse seems to still have issues, do you want to investigate more or should we merge directly? |
His error is unclear and might not be related. I think he's using a latest master version of opemocd. I'm sure this PR is fixing an issue with the L5 board with older versions and it works with openocd 0.11. |
Go then! |
Thanks ! |
Contribution description
This PR fixes the openocd script as reported on the forum.
The problem is that
OPENOCD_VERIFY
is computed beforeIMAGE_OFFSET
is updated in the case of binfile andOPENOCD_VERIFY
might depend on it.This problems breaks
tests/riotboot
onnucleo-l552ze-q
.The bug was introduced by #16911 (found by bisecting).
Testing procedure
tests/riotboot
works as expected:nucleo-l552ze-q
nucleo-l073rz
samr21-xpro
nrf52832-mdk
I don't have ESP32 based board to test that change, since
OPENOCD_VERIFY
was initially introduced for them apparently.Issues/PRs references
Bug introduced by #16911
https://forum.riot-os.org/t/cant-flash-riotboot-test-on-stm32-nucleo-l552ze-q-wrote-0-bytes-timed-out-while-waiting-for-target-halted/3443