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

Getting "no debugger connected to PC" error on my mac with nrf51dk

Maipei

Hey all,

I'm working with the nRF51822 (nRF51dk) on a mac running high sierra, and I've been following this tutorial to try to get started. But when I try to make flash code onto the board, I keep getting ERROR: There is no debugger connected to the PC.. I can see the board show up on my desktop as MBED when I plug it in, so I know my computer's recognizing the device as something. It just seems like it's seeing it as the wrong thing.

I used this same board a couple of years back, with an earlier version of macOS, and I was able to get everything working then, but I also used mbed.org and their cloud compiling stuff to generate hex files that I could just drop into the board, so this approach is a bit different. I'm connecting over a standard usb (usb C converting to A).

Could it be that I formatted my board for a different type of flashing when I was using mbed? I remember doing something like that. Anyway, I haven't been able to connect at all, and I'm a bit stuck. Any advice would be appreciated. Oh, and I've downloaded and installed the latest jlink software and documentation pack, so that's not the issue.

EDIT: I followed Gaute Gamnes' advice here and got the devkit to display as jlink when plugged in. Yay! However, now I'm getting a different error when I try to flash code on. ERROR: Cannot connect to any nRF device. Please make sure a device is connected to the debugger and supplied.

Parents
  • 0

    Hey, Bjorn. Thanks for the response. I checked out the blog posts, but they weren't much help; the problem is that I can't connect to the board, so I couldn't execute any of the troubleshooting steps that they give. When I try to connect over JLink, I get WARNING: RESET (pin 15) high, but should be low. Please check target hardware. This is weird, because I've put looked at p0.15, and it was low during my connection attempts. However, the product spec says that reset is active-low, so maybe this is the problem after all? That it's constantly resetting? Furthermore, once I trigger the reset pin, p0.15 stays high, and does not go low again until I power the board down completely. At this point, I'm suspicious of a hardware issue - maybe the reset is shorted somewhere.

Reply
  • 0

    Hey, Bjorn. Thanks for the response. I checked out the blog posts, but they weren't much help; the problem is that I can't connect to the board, so I couldn't execute any of the troubleshooting steps that they give. When I try to connect over JLink, I get WARNING: RESET (pin 15) high, but should be low. Please check target hardware. This is weird, because I've put looked at p0.15, and it was low during my connection attempts. However, the product spec says that reset is active-low, so maybe this is the problem after all? That it's constantly resetting? Furthermore, once I trigger the reset pin, p0.15 stays high, and does not go low again until I power the board down completely. At this point, I'm suspicious of a hardware issue - maybe the reset is shorted somewhere.

Children
No Data
Related