Giovanni wrote: Sun Feb 23, 2025 4:22 pm
OpenOCD support is not yet updated to the latest ChibiOS versions.
Is there any chance this happening? I tried changing `ch` to `ch_system` in `src/rtos/chibios.c` but didn't do the trick alone. Here's what I get now:
Code: Select all
[stm32f1x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000248 msp: 0x20000400
Warn : ChibiOS/RT memory signature claims to be bigger than expected. Assuming compatibility...
Info : Successfully loaded memory map of ChibiOS/RT target running version 7.0.4
Error: Failed to read memory at 0x5555556d
Error: ChibiOS registry integrity check failed, double linked list violation
Info : Only showing current execution because of a broken ChibiOS thread registry.
Error: Failed to read memory at 0x5555556d
Error: ChibiOS registry integrity check failed, double linked list violation
Info : Only showing current execution because of a broken ChibiOS thread registry.
[stm32f1x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000248 msp: 0x20000400
Info : Padding image section 0 at 0x08000164 with 12 bytes
[stm32f1x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000248 msp: 0x20000400
[stm32f1x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000248 msp: 0x20000400
Error: ChibiOS registry integrity check failed, NULL pointer
Info : Only showing current execution because of a broken ChibiOS thread registry.
Error: Failed to read memory at 0x20005018
Error: ChibiOS registry integrity check failed, double linked list violation
Info : Only showing current execution because of a broken ChibiOS thread registry.
It looks like `rlist` has moved quite a bit in ChibiOS 7.x due to the introduction of instances, so this might be a bigger change. Looking into it, but not sure I can get to the bottom of this soon.
Giovanni wrote: Sun Feb 23, 2025 4:22 pm
You may try the ChibiOS Debugger View in ChibiStudio, it provides even better functionality.
Except that it doesn't provide the stack trace which makes debugging really difficult. Or am I missing something?
Thanks, Szabi