Attachments (0)
Nordic Case Info
  • Case ID: 343185
Options

Passing board frequency to jlink command as argument

GalBrandwine

Hello, Not sure if this is the place for these questions, but here it is:

I've configured new board, and when I try to debug using the ncsconnect vscode plugin (linux) - Im getting this error `disconnected from gdb-server` and the debugging session quits.

I can debug without a problem using gdb cli.

From investigating `journalctl -f`:

You can see that the `speed` argument is 12000khz. 

When I manually add speed=4000 vecode's launch.json:

It works.

I don't want to add manually to vscode's launch files.

What can I do so that these arguments will be read from the board directory?

Thanks, gal

Parents
  • 0

    Hi Gal,

    I see that the debugger speed is specified in Nordic board files like so:
    https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs2-1/boards/nordic/nrf52840dk/board.cmake#L3

    Could you try replicate that in your board files?

    Hieu

  • 0 in reply to Hieu

    Hello, I've used your suggestion. Placed this board.cmake in the canary_r4010_imu board (line 413)

    Its looks like its not reading it from there. Because the speed is 12000

    Thakns

  • 0 in reply to GalBrandwine

    Hi Gal,

    Please wait while I consult our extension team. I will keep you updated.

    Hieu

  • 0 in reply to Hieu

    Hi Gal,

    I was informed that 12000 is the default speed that the extension will try to work with. The file I referred to in my first reply is used with west debug, so we have another alternative of modifying the debug task to use the west debug server.

    However, I understand that you don't want to modify launch.json, so that won't help.

    In that case, I think our interest should shift to why 12000 didn't work for your board setup. Could you review your setup to see if there is any weak point in the connection? What debugger are you using?

    Hieu

Reply
  • 0 in reply to Hieu

    Hi Gal,

    I was informed that 12000 is the default speed that the extension will try to work with. The file I referred to in my first reply is used with west debug, so we have another alternative of modifying the debug task to use the west debug server.

    However, I understand that you don't want to modify launch.json, so that won't help.

    In that case, I think our interest should shift to why 12000 didn't work for your board setup. Could you review your setup to see if there is any weak point in the connection? What debugger are you using?

    Hieu

Children
  • 0 in reply to Hieu

    Hey Hieu, thanks for replying.

    Out of curiosity - how I change the launch.JSON to work with the west debug server?

    I think if I set west-debu-server in the lunch.json, it'll be preferred to take the arguments from the per-board-runners.

    Thanks

  • 0 in reply to GalBrandwine

    Hi Gal,

    You can refer to the following link for configuring the west debug server in launch.json : https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/debug_custom.html.

  • 0 in reply to Hieu

    Hey Hieu, thanks for replying.

    An update:

    I've used your referenced link, and now I can debug with west debugserver

    Do you know how I can use `activeConfig` as argument to the launch-config?

    When I pass this "serverArgs": "debugserver --build-dir ${activeConfig}", 

    it doesn't work.

    Thanks

  • +1 in reply to GalBrandwine

    Hi Gal,

    activeConfig not being resolved correctly is a known issue. It is going to be fixed in a future release. Our apology for the inconvenience.

  • 0 in reply to Hieu

    Okay, you've helped enough by pointing out that when debugging with the west-server it takes the arguments from the runners in the board.cmake files.

    Thanks!

Terms of service