Cannot debug Rigado BMD 340 evaluation kit (Beginner Help!)

Currently messing with the NRF52840 chip and given examples (NRF Connect SDK v1.7.0) on two different eval boards (the nRF52840-DK from Nordic and the BMD 340 Eval board from uBlox) 

I am able to program and verify the examples fine on both boards, but I am not able to debug the examples on the BMD 340 whereas the nRF52840-DK works as you would expect. Am I missing something? Using Segger Embedded Studio as the IDE. Any and all help is appreciated.

Thanks!

Parents
  • Hi Pain

    What exactly happens when you try debugging using the BMD 340 evaluation kit? Is the issue that it seems to run debugging, but that you don't get any output in your terminal? If so, try using the RTT backend instead of the UART backend for logging as I'm not sure the BMD 340 kit is able to send UART data to the computer like the nRF52 DK.

    Best regards,

    Simon

  • Thanks for the reply Simon. 

    I guess the main issue I'm running into is that I cannot set breakpoints in the code and step through the code with the BMD 340 kit like I can nRF52 kit. On the BMD 340 kit, SES IDE says the code is "Running" but I can't pause / set break points and step through the lines. 

    Also I should mention that I am using a J link Base (the one with 20 pin ribbon cable) for programming/debugging both kits. (I assume that uses RTT). I plug it into the Debug-In (10 pin connector) on the board via a 20 pin to 10 pin adapter. Both kits are powered off of a coin cell battery. I assume this setup is fine because it works fine on the nRF52 kit, I can step through lines of code with no issues. Not on the BMD 340 kit :( 

    Thanks again. 

Reply
  • Thanks for the reply Simon. 

    I guess the main issue I'm running into is that I cannot set breakpoints in the code and step through the code with the BMD 340 kit like I can nRF52 kit. On the BMD 340 kit, SES IDE says the code is "Running" but I can't pause / set break points and step through the lines. 

    Also I should mention that I am using a J link Base (the one with 20 pin ribbon cable) for programming/debugging both kits. (I assume that uses RTT). I plug it into the Debug-In (10 pin connector) on the board via a 20 pin to 10 pin adapter. Both kits are powered off of a coin cell battery. I assume this setup is fine because it works fine on the nRF52 kit, I can step through lines of code with no issues. Not on the BMD 340 kit :( 

    Thanks again. 

Children
  • Both the nRF52DK and the BMD 340 EK should have an onboard debugger. You don't need an extra J-Link on top of that. You should be able to power them from a USB port on your computer and use the onboard debugger for debugging. I'm not sure why the BMD 340 debug IN pin header wouldn't work. Unfortunately I don't have one present to test myself at the moment.

    Best regards,

    Simon

Related