nRF52832: Ozone fails when JLinkGDBServer succeeds

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • nRF52832: Ozone fails when JLinkGDBServer succeeds

    I manage to debug against the nRF52832_xxAA with JLinkGDBServer and arm-none-eabi-gdb.

    When I try with Ozone, it fails with the following message:

    Source Code

    1. Debug.Start();
    2. J-Link: connected to target device
    3. Instruction trace could not be started: hardware does not support instruction trace"


    What's going wrong?

    Configuration
    • J-Link Edu
    • Firmware: J-Link V9 compiled Apr 21 2017 11:08:06
    • Hardware: V9.40
    • JLinkARM.dll V6.14e (DLL compiled Apr 27 2017 18:29:07)
    • Ozone 2.32 on macOS 10.12.4
    • GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20151217-cvs


    Thank you!

  • Hi,


    Does it fail?
    The output just says that the trace view of Ozone is currently open, but the debugger hardware (J-Link V9) does not support trace.
    This warning can be omitted by closing the Trace View before connecting to the target.

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.