Trying to debug with MCUBOOT enabled fails to boot.

RE: Trying to debug with MCUBOOT enabled fails to boot.

MatjazK — Mon, 30 Sep 2024 06:04:02 GMT

Looking a bit further into this I found I need two things to make sure this works:
- disable flash breakpoint
- load mcuboots .elf file during debug launch

for cortex debugs launch.json configuration on VSCode that was resolved by adding following lines to debug launch:

      "loadFiles": [
        "/workspaces/project/app/build/mcuboot/zephyr/zephyr.elf"
      ],
      "preLaunchCommands": ["monitor flash breakpoints = 0"]

RE: Trying to debug with MCUBOOT enabled fails to boot.

Torsten Robitzki — Fri, 27 Sep 2024 09:08:27 GMT

According to the documentation, there is a GDB monitor command to disable flash breakpoints: https://wiki.segger.com/J-Link_GDB_Server#flash_breakpoints

RE: Trying to debug with MCUBOOT enabled fails to boot.

MatjazK — Fri, 27 Sep 2024 09:01:06 GMT

Any idea how to achieve that? I have tried various things in effort to disable those with no luck.
Another interesting finding is, that using "debug" command breaks bootloader, using "attach" however - works fine. Even when resetting MCU after attach bootloader works fine

RE: Trying to debug with MCUBOOT enabled fails to boot.

Torsten Robitzki — Fri, 27 Sep 2024 08:53:10 GMT

Basically, the Cortex M4 core should have enough hardware breakpoints for basic debugging. I would try to find a way, to disable Seggers software break points, to see if this makes a differences.