Posts by InterruptRequest

    Thank you for your response. I am trying to specify the location of the ETF using your link here:

    Quote from Nino

    With some multi core target devices it may be additionally needed to set the base addresses for the Coresight components that the J-Trace Pro could not autodetect:
    kb.segger.com/Arm_trace_techni…f_trace_components_failed

    Once I include the init script, the M33 core is no longer detected.


    I have an STM32Mp257F board with a MIPI 10 connector for debug. If I attach this to my J-Trace by using the left half of the MIPI 20 cable, I am able to debug with Ozone successfully. :thumbup:

    The hope for this setup is to be able to do any sort of instruction tracing. I have tried many combinations of trace settings, both with the J-Trace connected as JTAG and SWD, yet nothing seems to work. I do not expect "trace pins" to be a viable option due to their not being present on the MIPI 10 connector. Would that configuration be expected to work if I had a MIPI 20 on an STM32MP257F board?

    The M33 is running at 400 MHz. Is there some sort of enable that needs to happen in a script or in the firmware? What is expected to work?

    Hoping for any tips! ?(