The Nucleo Board is able to run examples from the STM32CubeIDE so I think the board should be okay.
Has anyone an idea what could cause this issue? Thanks in advance!
I have tried to fall back on previous branches (2021.04-branch and 2021.07-branch). I also tried to merge the PR locally and test riotboot again. Something changed there: I still get the time out and there is still the message error executing cortex_m crc algortihm.
Did I understand you correctly that with these changes the test worked on your boards correctly?
I will continue to see if I am missing something. Thank you so far
do you also encounter issues with riotboot outside of the test framework? i.e. what happens when you try smthing like
BOARD=nucleo-l552ze-q FEATURES_REQUIRED+=riotboot APP_VER=$(date +%s) make -C examples/hello-world riotboot/flash-combined-slot0
Binfile detected, adding ROM base address: 0x00000000
Flashing with IMAGE_OFFSET: 0x00000000
Open On-Chip Debugger 0.11.0+dev-00471-gcaa169813 (2021-11-19-01:12)
Licensed under GNU GPL v2
For bug reports, read
OpenOCD: Bug Reporting
hla_swd
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : DEPRECATED target event trace-config; use TPIU events {pre,post}-{enable,disable}
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : clock speed 500 kHz
Info : STLINK V2J38M27 (API v2) VID:PID 0483:374B
Info : Target voltage: 3.268421
Info : stm32l5x.cpu: Cortex-M33 r0p2 processor detected
Info : stm32l5x.cpu: target has 8 breakpoints, 4 watchpoints
Info : starting gdb server for stm32l5x.cpu on 0
Info : Listening on port 44669 for gdb connections
TargetName Type Endian TapName State
0* stm32l5x.cpu hla_target little stm32l5x.cpu reset
stm32l5x.dap
Error executing event halted on target stm32l5x.cpu:
/usr/local/bin/…/share/openocd/scripts/target/stm32l5x.cfg:116: Error: \
in procedure ‘ocd_process_reset’
in procedure ‘ocd_process_reset_inner’ called at file “embedded:startup.tcl”, line 788
in procedure ‘ahb_ap_non_secure_access’ called at file “/usr/local/bin/…/share/openocd/scripts/target/stm32l5x.cfg”, line 152
at file “/usr/local/bin/…/share/openocd/scripts/target/stm32l5x.cfg”, line 116
target halted due to debug-request, current mode: Thread
xPSR: 0xf9000000 pc: 0xfffffffe msp: 0xfffffffc
Info : device idcode = 0x20016472 (STM32L55/L56xx - Rev ‘unknown’ : 0x2001)
Info : TZEN = 0 : TrustZone disabled by option bytes
Info : RDP level 0 (0xAA)
Info : flash size = 512kbytes
Info : flash mode : dual-bank
Info : device idcode = 0x20016472 (STM32L55/L56xx - Rev ‘unknown’ : 0x2001)
Info : TZEN = 0 : TrustZone disabled by option bytes
Info : RDP level 0 (0xAA)
Info : flash size = 512kbytes
Info : flash mode : dual-bank
Info : device idcode = 0x20016472 (STM32L55/L56xx - Rev ‘unknown’ : 0x2001)
Info : TZEN = 0 : TrustZone disabled by option bytes
Info : RDP level 0 (0xAA)
Info : OTP size is 512 bytes, base address is 0x0bfa0000
Warn : no flash bank found for address 0x00000000
auto erase enabled
wrote 0 bytes from file ($PATH)/RIOT/tests/riotboot/bin/nucleo-l552ze-q/tests_riotboot-slot0-extended.bin in 0.010434s (0.000 KiB/s)
Error: timed out while waiting for target halted
Error: error executing cortex_m crc algorithm
@pilzf98 if you are on Debian buster that means you are not running the openocd packaged version no? Did you compile it from the source is it exactly the v0.11.0 tag or another commit?
That’s good to hear, but it does mean that there is an issue with the latest OpenOCD master. Whether we are not handling some API change or whether something is broken there needs to be investigated. Thanks for reporting.