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

JulianR · April 4, 2024 at 10:51 AM

The latest version of the Ozone Debugger fails to connect to the NXP S32K344 microcontroller. This can be reproduces with the sample project from https://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:

Code

Device "S32K344" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 40us
InitTarget() start
SDA_AP detected
Checking if debug access is already enabled...
  Core already enabled
Checking if HSE firmware is installed...
  HSE firmware not installed
Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
  Lock step mode enabled
InitTarget() end - Took 1.85ms
TotalIRLen = 8, IRPrint = 0x0001
JTAG chain detection found 1 devices:
 #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: MEM-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[4]: AHB-AP (IDR: Not set)
AP[5]: AHB-AP (IDR: Not set)
AP[6]: MEM-AP (IDR: Not set)
AP[7]: MEM-AP (IDR: Not set)
AP[3]: Skipped. Not an AHB-AP
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Connect failed. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 36us
InitTarget() start
SDA_AP detected
Checking if debug access is already enabled...
  Debug access is not enabled yet. Performing enable debug access sequence...
  Debug access enabled
Checking if HSE firmware is installed...
  HSE firmware not installed
Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
  Lock step mode enabled
InitTarget() end - Took 10.5ms
TotalIRLen = 8, IRPrint = 0x0001
JTAG chain detection found 1 devices:
 #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: MEM-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[4]: AHB-AP (IDR: Not set)
AP[5]: AHB-AP (IDR: Not set)
AP[6]: MEM-AP (IDR: Not set)
AP[7]: MEM-AP (IDR: Not set)
AP[3]: Skipped. Not an AHB-AP
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 27us
InitTarget() start
SDA_AP detected
Checking if debug access is already enabled...
  Debug access is not enabled yet. Performing enable debug access sequence...
  Debug access enabled
Checking if HSE firmware is installed...
  HSE firmware not installed
Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
  Lock step mode enabled
InitTarget() end - Took 10.3ms
TotalIRLen = 8, IRPrint = 0x0001
JTAG chain detection found 1 devices:
 #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: MEM-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[4]: AHB-AP (IDR: Not set)
AP[5]: AHB-AP (IDR: Not set)
AP[6]: MEM-AP (IDR: Not set)
AP[7]: MEM-AP (IDR: Not set)
AP[3]: Skipped. Not an AHB-AP
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Connect failed. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 28us
InitTarget() start
SDA_AP detected
Checking if debug access is already enabled...
  Debug access is not enabled yet. Performing enable debug access sequence...
  Debug access enabled
Checking if HSE firmware is installed...
  HSE firmware not installed
Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
  Lock step mode enabled
InitTarget() end - Took 11.8ms
TotalIRLen = 8, IRPrint = 0x0001
JTAG chain detection found 1 devices:
 #0 Id: 0x0996001D, IRLen: 04, JTAG-DP
Found 1 device in JTAG chain, IRPost/DRPost != 0. Reset IRPost/DRPost to 0.
DPv0 detected
AP map detection skipped. Manually configured AP map found.
AP[0]: MEM-AP (IDR: Not set)
AP[1]: APB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[4]: AHB-AP (IDR: Not set)
AP[5]: AHB-AP (IDR: Not set)
AP[6]: MEM-AP (IDR: Not set)
AP[7]: MEM-AP (IDR: Not set)
AP[3]: Skipped. Not an AHB-AP
Attach to CPU failed. Executing connect under reset.
Failed to power up DAP
Connection failed.

Display More

SEGGER - AlexD · April 8, 2024 at 1:48 PM

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

JulianR · April 9, 2024 at 7:38 AM

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.

SEGGER - AlexD · April 9, 2024 at 11:15 AM

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

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

Participate now!

Users Viewing This Thread