[SOLVED] Ozone tracing: No clock present

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

  • [SOLVED] Ozone tracing: No clock present

    Hi,

    I am trying to enable the ETM Tracing with Ozone on a TWR-K65 board.

    But when starting a debugging session I get the following error:

    Source Code

    1. Debug.Start();
    2. Executed J-Link command "ScriptFile=D:/temp/Kinetis_Tracing.JLinkScript"
    3. J-Link: Device "MK65FN2M0XXX18" selected.
    4. J-Link: Executing InitTarget()
    5. J-Link: Found SW-DP with ID 0x2BA01477
    6. J-Link: Scanning AP map to find all available APs
    7. J-Link: AP[2]: Stopped AP scan as end of AP map has been reached
    8. J-Link: AP[0]: AHB-AP (IDR: 0x24770011)
    9. J-Link: AP[1]: JTAG-AP (IDR: 0x001C0000)
    10. J-Link: Iterating through AP map to find AHB-AP to use
    11. J-Link: AP[0]: Core found
    12. J-Link: AP[0]: AHB-AP ROM base: 0xE00FF000
    13. J-Link: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    14. J-Link: Found Cortex-M4 r0p1, Little endian.
    15. J-Link: FPUnit: 6 code (BP) slots and 2 literal slots
    16. J-Link: CoreSight components:
    17. J-Link: ROMTbl[0] @ E00FF000
    18. J-Link: ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS
    19. J-Link: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
    20. J-Link: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
    21. J-Link: ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
    22. J-Link: ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
    23. J-Link: ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
    24. J-Link: ROMTbl[0][6]: E0042000, CID: B105900D, PID: 003BB907 ETB
    25. J-Link: ROMTbl[0][7]: E0043000, CID: B105900D, PID: 001BB908 CSTF
    26. J-Link: connected to target device
    27. J-Link: Reset: Halt core after reset via DEMCR.VC_CORERESET.
    28. J-Link: Reset: Reset device via AIRCR.SYSRESETREQ.
    29. J-Link: Executing AfterResetTarget()
    30. J-Link: J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
    31. Executed J-Link command "SelectTraceSource=1"
    32. J-Link: Start: Initializing trace pins
    33. J-Link: End: Initializing trace pins
    34. J-Link: Using main connection for streaming trace. For max. trace throughput, please connect J-Trace via IP
    35. J-Link: No trace clock present, trace may not work correctly.
    36. If application enables trace clock during execution, start of trace data may be missing.
    Display All


    The JLinkScript I use is attached and my Ozone-COnfigurations looks like this:

    Source Code

    1. void OnProjectLoad (void) {
    2. Project.SetDevice ("MK65FN2M0xxx18"); Project.SetHostIF ("USB", ""); Project.SetTargetIF ("SWD");
    3. Project.SetTIFSpeed ("4 MHz"); Project.SetTraceSource ("Trace Pins"); Project.SetTracePortWidth (4); Project.AddSvdFile ("Cortex-M4.svd");
    4. Project.SetJLinkScript("D:/temp/Kinetis_Tracing.JLinkScript");}



    Any Ideas whats going wrong here?

    Thanks!
    Files
  • Hello Stefan,

    Thank you for your inquiry.
    Did you make sure the Trace Pins are connected to the debug header?
    Because according to the TWR-K65 schematics they are not connected by default.
    You will need to populate resistors R54-58 with 0 Ohm resistors so the trace signals can reach the J-Trace PRO.

    Also you are using a K64 JLinkscriptfile, make sure this script file is compatible to K65 devices.
    Some devices require unlock sequences for register access for example.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/
  • Hello Stefan,

    Great to hear that you are up and running again.
    I will consider this case as solved then.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support system can be used as well: segger.com/ticket/