• State Verified Answer
  • Replies 10 replies
  • Subscribers 62 subscribers
  • Views 8167 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 113477
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

J-Link Debugger with SEGGER Embedded Studio on Mac

RichieJH

Continuing my mission to have SES set up to be the complete development environment on a Mac I am struggling to get the Jlink Debugger to behave with SES.

It appears I cannot use the J-Link RTT Viewer since I have a Mac and this looks like it is Windows only. So I have fallen back to using the SEGGER J-Link Debugger V2.14 which is for Windows, Mac and Linux.

In terms of the Target Device, I see the nRF52832_xxAA and can set the Target Interface (JTAG: 1 MHz) with a USB host. So far so good.

SES imports the RTT Files folder so I added the relevant headers at the top of Main.

The problem is that every time I try to Download & Reset, Attach to Running Program or Attach and Halt Program I get a Connection Failed message in the J-Link Debugger Console. Also I notice the SES becomes unstable and often freezes and I have to restart it (I have reported the logs to SEGGER).

Is there something I am missing or is this a known bug?

Thanks

Parents
  • 0

    Hey, while there isn't an RTT Viewer on Mac, it is very easy to use RTT just following the answer in this post: devzone.nordicsemi.com/.../. You just connect to the device using JLink.exe and then open JLinkRTTClient and can view all RTT logging in that terminal.

    You need to be using SWD, not JTAG. 1 mhz should be fine but up to 5 mhz should work. I'm guessing this is the problem. nRF52 devices implement an SWD interface. The connection is failing probably because of this.

  • 0 in reply to Michael Dietz

    And that sounds like Embedded Studio is not playing well being ran together with J-Link Debugger, my guess is they aren't intended to be used together, but it sounds like a bug. I'll ask SEGGER about it.

    I think really we need to be debugging in Embedded Studio and not using the J-Link debugger at all. Hopefully we can figure out the problems you are having to make this possible. But definitely stick with SWD instead of JTAG as thats needed.

    you might also get better answers, quicker than I can provide here: forum.segger.com/index.php. Johannes from SEGGER seems to be answering questions right away there and he's the guy I ask.

Reply
  • 0 in reply to Michael Dietz

    And that sounds like Embedded Studio is not playing well being ran together with J-Link Debugger, my guess is they aren't intended to be used together, but it sounds like a bug. I'll ask SEGGER about it.

    I think really we need to be debugging in Embedded Studio and not using the J-Link debugger at all. Hopefully we can figure out the problems you are having to make this possible. But definitely stick with SWD instead of JTAG as thats needed.

    you might also get better answers, quicker than I can provide here: forum.segger.com/index.php. Johannes from SEGGER seems to be answering questions right away there and he's the guy I ask.

Children
No Data
Related

core_v2_widget.Hide()