[ABANDONED] Unable to continue past bkpt instruction

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hello,

    Thank you for your inquiry.
    Please be aware that the referenced post is over 4 years old so it is highly unlikely that the issues are related.
    The J-Link software version you are using is rather old, could you try the latest one and see if the behaviour improves?

    What target device are you looking to debug here?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hello Nino,

    We can try to upgrade and see if that makes a difference. The reference post (and the problem referenced in the post) is exactly what I am running into.

    We are using an STM32L4R5ZI Nucleo board.

    The fundamental issue we are trying to solve by adding the ASM breakpoint is that when attempting to execute from RAM (small piece of ROM code copies main code to RAM then jumps to main code), we are unable to hit breakpoints set before executing the ROM to RAM copy. This, as I understand it, is expected since the breakpoints are loaded on start/restart and when the code is copied from ROM to RAM, the breakpoints are overwritten.

    The idea was that by forcing a breakpoint right before RAM execution, and then having the developer continue, they would be able to hit their RAM breakpoints as expected, but because we cannot "continue" when hitting an ASM breakpoint, this is proving to be a bit more cumbersome than anticipated.

    I will note that we do not experience our original issue when using a different vendor's MCU, and breakpoints in RAM work the same as breakpoints in ROM.

    -Felix