[SOLVED] Ozone V3.32a fails to connect to NXP S32K344

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

  • [SOLVED] Ozone V3.32a fails to connect to NXP S32K344

    The latest version of the Ozone Debugger fails to connect to the NXP S32K344 microcontroller. This can be reproduces with the sample project from wiki.segger.com/NXP_S32K3xx#Streaming_trace NXP_S32K344_TracePins.zip
    Open the project with Ozone V3.32 and connect -> Works, open the project with Ozone V3.32a and connect -> Fails.


    I am using an older j-Trace Pro for ARM Cortex-M (Part No. 8.18.00) and my operating System is Windows 10 Professional.

    This is the Console output with the failing connection:

    Source Code

    1. Device "S32K344" selected.
    2. ConfigTargetSettings() start
    3. ConfigTargetSettings() end - Took 40us
    4. InitTarget() start
    5. SDA_AP detected
    6. Checking if debug access is already enabled...
    7. Core already enabled
    8. Checking if HSE firmware is installed...
    9. HSE firmware not installed
    10. Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
    11. Lock step mode enabled
    12. InitTarget() end - Took 1.85ms
    13. TotalIRLen = 8, IRPrint = 0x0001
    14. JTAG chain detection found 1 devices:
    15. #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
    16. Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
    17. DPv0 detected
    18. AP map detection skipped. Manually configured AP map found.
    19. AP[0]: MEM-AP (IDR: Not set)
    20. AP[1]: APB-AP (IDR: Not set)
    21. AP[2]: MEM-AP (IDR: Not set)
    22. AP[3]: MEM-AP (IDR: Not set)
    23. AP[4]: AHB-AP (IDR: Not set)
    24. AP[5]: AHB-AP (IDR: Not set)
    25. AP[6]: MEM-AP (IDR: Not set)
    26. AP[7]: MEM-AP (IDR: Not set)
    27. AP[3]: Skipped. Not an AHB-AP
    28. Attach to CPU failed. Executing connect under reset.
    29. Failed to power up DAP
    30. Connect failed. Resetting via Reset pin and trying again.
    31. ConfigTargetSettings() start
    32. ConfigTargetSettings() end - Took 36us
    33. InitTarget() start
    34. SDA_AP detected
    35. Checking if debug access is already enabled...
    36. Debug access is not enabled yet. Performing enable debug access sequence...
    37. Debug access enabled
    38. Checking if HSE firmware is installed...
    39. HSE firmware not installed
    40. Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
    41. Lock step mode enabled
    42. InitTarget() end - Took 10.5ms
    43. TotalIRLen = 8, IRPrint = 0x0001
    44. JTAG chain detection found 1 devices:
    45. #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
    46. Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
    47. DPv0 detected
    48. AP map detection skipped. Manually configured AP map found.
    49. AP[0]: MEM-AP (IDR: Not set)
    50. AP[1]: APB-AP (IDR: Not set)
    51. AP[2]: MEM-AP (IDR: Not set)
    52. AP[3]: MEM-AP (IDR: Not set)
    53. AP[4]: AHB-AP (IDR: Not set)
    54. AP[5]: AHB-AP (IDR: Not set)
    55. AP[6]: MEM-AP (IDR: Not set)
    56. AP[7]: MEM-AP (IDR: Not set)
    57. AP[3]: Skipped. Not an AHB-AP
    58. Attach to CPU failed. Executing connect under reset.
    59. Failed to power up DAP
    60. ConfigTargetSettings() start
    61. ConfigTargetSettings() end - Took 27us
    62. InitTarget() start
    63. SDA_AP detected
    64. Checking if debug access is already enabled...
    65. Debug access is not enabled yet. Performing enable debug access sequence...
    66. Debug access enabled
    67. Checking if HSE firmware is installed...
    68. HSE firmware not installed
    69. Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
    70. Lock step mode enabled
    71. InitTarget() end - Took 10.3ms
    72. TotalIRLen = 8, IRPrint = 0x0001
    73. JTAG chain detection found 1 devices:
    74. #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
    75. Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
    76. DPv0 detected
    77. AP map detection skipped. Manually configured AP map found.
    78. AP[0]: MEM-AP (IDR: Not set)
    79. AP[1]: APB-AP (IDR: Not set)
    80. AP[2]: MEM-AP (IDR: Not set)
    81. AP[3]: MEM-AP (IDR: Not set)
    82. AP[4]: AHB-AP (IDR: Not set)
    83. AP[5]: AHB-AP (IDR: Not set)
    84. AP[6]: MEM-AP (IDR: Not set)
    85. AP[7]: MEM-AP (IDR: Not set)
    86. AP[3]: Skipped. Not an AHB-AP
    87. Attach to CPU failed. Executing connect under reset.
    88. Failed to power up DAP
    89. Connect failed. Resetting via Reset pin and trying again.
    90. ConfigTargetSettings() start
    91. ConfigTargetSettings() end - Took 28us
    92. InitTarget() start
    93. SDA_AP detected
    94. Checking if debug access is already enabled...
    95. Debug access is not enabled yet. Performing enable debug access sequence...
    96. Debug access enabled
    97. Checking if HSE firmware is installed...
    98. HSE firmware not installed
    99. Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
    100. Lock step mode enabled
    101. InitTarget() end - Took 11.8ms
    102. TotalIRLen = 8, IRPrint = 0x0001
    103. JTAG chain detection found 1 devices:
    104. #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
    105. Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
    106. DPv0 detected
    107. AP map detection skipped. Manually configured AP map found.
    108. AP[0]: MEM-AP (IDR: Not set)
    109. AP[1]: APB-AP (IDR: Not set)
    110. AP[2]: MEM-AP (IDR: Not set)
    111. AP[3]: MEM-AP (IDR: Not set)
    112. AP[4]: AHB-AP (IDR: Not set)
    113. AP[5]: AHB-AP (IDR: Not set)
    114. AP[6]: MEM-AP (IDR: Not set)
    115. AP[7]: MEM-AP (IDR: Not set)
    116. AP[3]: Skipped. Not an AHB-AP
    117. Attach to CPU failed. Executing connect under reset.
    118. Failed to power up DAP
    119. Connection failed.
    Display All

  • Hi JulianR,
    could you please check if the issue persists after having updated the J-Link DLL in your Ozone installation? The J-Link installer for Windows comes with an option to update the J-Link DLL in other applications as well.
    Best regards
    -- AlexD
    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.

  • Hello AlexD,
    you are right, it is definitely a problem with the JLink_x64.dll shipped with Ozone V3.32a (7.96).
    I replaced the DLL with version 7.94k (this version is shipped with Ozone V3.32) and that works and I also used the one from the latest J-Link Package, 7.96c, which also works.

  • Hi JulianR,
    great to hear you are up and running again.
    The next Ozone release will contain the then most recent version of the J-Link DLL, thus resolving the issue you've encountered.
    We will consider this topic as closed now.
    Best regards
    -- AlexD
    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.