• State Suggested Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 76 subscribers
  • Views 6495 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 230229
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Do I need to buy a Segger external debugger to get debug trace in Segger embedded studio?

Jason

Hello Nordic,

I hope you can help me. I'm using an NRF52840 DK development board. 

I followed the instructions on this video to enable debug trace in Segger embedded studio (https://www.youtube.com/watch?v=uP8RYgYGRvI)

When I debug I do not see any trace output. My build configuration is set to debug. 

I googled and found this page (https://devzone.nordicsemi.com/nordic/b/blog/posts/debugging-nrf52-series-devices-using-trace) which says

  • IMPORTANT: To use trace you need to have an external debugger that supports trace (trace won't work using the on-board debugger on our development kits). www.segger.com/jlink-debug-probes.html (see debug probes with built-in trace memory). IAR and ULink also offer debuggers that support trace and work with our devices.

The Segger debug probes are over $500.

I then found this page (https://devzone.nordicsemi.com/nordic/b/blog/posts/programming-and-debugging-custom-nrf5x-devices) which says 

  • When developing applications on a nRF5x Development Kit, you can program it by simply connecting it to your PC with a USB cable. This is possible because the Development Kit has an on-board debug unit supporting the JLINK debug interface.

I do not understand what I need to do to get debug trace in Segger embedded studio. 

My sdk_config.h has 

  • #define NRF_LOG_BACKEND_RTT_ENABLED 1
  • #define NRF_LOG_ENABLED 1

Thanks for your help,

-Jason

Parents
  • 0

    Yes if you want to use actual trace you need a Segger external debugger which supports trace. Trace uses a separate set of lines from the ARM microprocessor. Not many people actually need to use trace however. 

     Your second quote has nothing to do with the first, note that doesn't even mention 'trace'. You can program it using the onboard JLink just as it says you can but the onboard debugger does not support the trace outputs just as your first quote says. 

    None of that has anything at all to do with what you have enabled in your sdk_config.h, RTT, which is Real Time Terminal which allows a log output via any JLink device which then appears in the terminal pane of SES. It doesn't use the trace pins, it has nothing to do with trace. This is probably what you actually wanted in the first place, just use the logging macros with those defines enabled and the log will go to SES. 

  • 0 in reply to RK

    Thank you.

    Do you mean logging macros like NRF_LOG_ERROR for example? Because I do not see those lines (or any others) appearing in my Debug Terminal window. 

    Running in the debugger, debug build. v15.3. Connected to my PC with USB.

    If I set a breakpoint or step through the code I can see that it is asserting with NRF_FAULT_ID_SDK_ERROR.

    Thanks again for your help.

  • 0 in reply to Jason

    Hi,

    It should be sufficient to change the logger backend to RTT. To narrow down the issue, please try the ble_app_uart example which has logging over RTT enabled by default and see if you get the same result. 

Reply Children
  • 0 in reply to Vidar Berg

    Ok so I tried running ble_app_uart with a debug build and I still get no trace output. And after about a minute or something I noticed that it had stopped here (with id=16385 which is NRF_FAULT_ID_SDK_ERROR)

    As you can see there is still nothing printed in the Debug Terminal window in the lower right of the display. 

     

  • 0 in reply to Jason

    Thanks for testing this. It indicates that it's not a FW problem at least. What version of SES and which OS are you using? You can try to update to the latest J-link driver and see if that helps. Link: https://www.segger.com/downloads/jlink/ 

    Jason said:
    And after about a minute or something I noticed that it had stopped here (with id=16385 which is NRF_FAULT_ID_SDK_ERROR)

    Sure it's not 3 minutes? Then it would be expected as the app attempts to enter deep sleep (system OFF) after 3 minutes of inactivity, which is not possible in debug mode.

  • 0 in reply to Vidar Berg

    Yes, 3 minutes sounds right. Latest SES I think. I moved from Windows 7 to Windows 10 last night so tonight I'll try testing again and reinstalling jlink and maybe SES. Thanks for your excellent help Grinning

  • 0 in reply to Vidar Berg

    reinstalled j-link driver but it didn't fix it. Then I reinstalled Segger embedded studio for ARM V4.16 (64-bit) Hobbyist license. It's still the same. I can see from my Subversion diff that my nRF5_SDK_15.3.0_59ac345 has no diffs in that example. 

    When I do "Build and Debug" I can see it pop up the progress bars. I know it's updating the software because I've been able to develop various examples. I press F5 to run in the debugger and nothing appears in the "Debug Terminal". When it breakpoints at 3 minutes I still see nothing in the "Debug Terminal" 

    Am I looking at the wrong window? Is it called "Debug Terminal"?

  • 0 in reply to Jason

    Ok, so I see the same problem after updating the latest Segger driver (v.6.46C). Please try to uninstall the version you installed, then install an older version, 622g for instance. The antivirus SW is preventing me from downgrading for some reason so couldn't verify this on my side.  

    The log should be displayed in the debug terminal. 

Related
Terms of service