You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide more details about on-board debugging via SWD.
Using ST-Link/V2-ISOL or Segger J-Link: the Buddy board resets but does not halt, rendering debugging effectively impossible.
STM32F4-Discovery (which uses the same STM32F407VG MCU) works fine with the above external debuggers, same wiring harnesses, same software tools.
The Buddy board has the appendix removed.
However, with the Buddy board - none of the setups result in working debugging:
neither Windows + STM32CubeIDE with/without openocd
nor Linux + STM32CubeIDE/openocd/st-util
Tried various searches to find out information about debugging Prusa firmware on the buddy board. None resulted in a working debug setup.
This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.
Please provide more details about on-board debugging via SWD.
Using ST-Link/V2-ISOL or Segger J-Link: the Buddy board resets but does not halt, rendering debugging effectively impossible.
STM32F4-Discovery (which uses the same STM32F407VG MCU) works fine with the above external debuggers, same wiring harnesses, same software tools.
The Buddy board has the appendix removed.
However, with the Buddy board - none of the setups result in working debugging:
Tried various searches to find out information about debugging Prusa firmware on the buddy board. None resulted in a working debug setup.
Thanks in advance!
(Cross-posted from prusa3d/Buddy-board-MINI-PCB#3)
The text was updated successfully, but these errors were encountered: