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

nrf52832 not working outside debugger.

Arne Laugstøl

Hi

I have a wired situation in my project. Everything is working fine when I am running my heart-rate device with the debugger. When I detach the debugger or just power-cycle the device behaviour becomes wired. The device still advertise, so I can see it from my phone. But, when I try to connect to it from my phone, it will not connect anymore. If I do "connect jLink" from Segger studio, then everything works fine again.

I am using SEGGER_RTT_WriteString a lot, and I suspected that it could be that the output to the debugger via SWD was blocking when I am not running the debugger. So, I have checked in my code that I am doing SEGGER_RTT_Init() at start, and I have set the SEGGER_RTT_CONFIG_DEFAULT_MODE to 0 (i.e SKIP when buffer is full).

I am using nRF52832 with our own HW, Segger Studio and j-Link Ultra. The sdk version 14.2.0.

Any idea where to start looking for a solution?

Regards Arne

Parents
  • 0

    Hi you

    Thanks for trying to help me out!

    I commented out all the code in SEGGER_RTT_printf and SEGGER_RTT_WriteString. That's the only call I am doing to RTT. That gave the same results as earlier. Everything works fine when J-link is connected. When I disconnect j-link or power-cycling, then I am not able to connect anymore, even if my device is advertising.

    Regards Arne

  • 0 in reply to Arne Laugstøl

    Tanks for tips, I will try it out when I am back in office. In the mean time I would like to share another observation that I did: When I connected to the debugger via j-link command window, made a reset and then a g (go) command - Everything works perfect. Just power-cycling without the debugger, then the device will not advertise anymore.

    Also, if I connect to the debugger using RTT-viewer, then everything is perfect. (The RTT-viewer seems to reset the device when I connect) If I then disconnect from debugger by a disconnect in RTT-Viewer - suddenly everything continue to work fine. So, it seems that a reset from the debugger makes a difference compared to a power-up reset. Does that make sense?

Reply
  • 0 in reply to Arne Laugstøl

    Tanks for tips, I will try it out when I am back in office. In the mean time I would like to share another observation that I did: When I connected to the debugger via j-link command window, made a reset and then a g (go) command - Everything works perfect. Just power-cycling without the debugger, then the device will not advertise anymore.

    Also, if I connect to the debugger using RTT-viewer, then everything is perfect. (The RTT-viewer seems to reset the device when I connect) If I then disconnect from debugger by a disconnect in RTT-Viewer - suddenly everything continue to work fine. So, it seems that a reset from the debugger makes a difference compared to a power-up reset. Does that make sense?

Children
No Data
Related