Can't connect to NXP's S32K322 after flashing the target

    • Can't connect to NXP's S32K322 after flashing the target

      Hello,

      I'm working on bringing up a prototype board which has S32K322 device. After writing some image to the flash memory using J-Link Flash via SWD, I'm unable to re-flash the target again. This was probably 30th time I flashed the device, before that I was able to connect, flash, erase and debug.

      I've reached out to NXP for assistance, but this did not yield any results yet: community.nxp.com/t5/S32K/Can-…t-to-S32K322/td-p/2035700


      Brief summary of the issue:
      -MCU was operational, I was able to flash the target using JFlash tool.
      -I've "managed" to brick the device by just flashing with a software image which did not do much, it was supposed to initialize the external oscillator and start some simple queries over the I2C bus.
      -"Bricked" MCU does not look like it is executing code, the external oscillator is not enabled, although it was until the MCU stopped working.
      -If the reset pin is set to low(MCU is in reset), JLink is able to read something, but fails to connect:

      Source Code

      1. J-Link>connect
      2. Device "S32K322_M7_0" selected.
      5. Connecting to target via SWD
      6. ConfigTargetSettings() start
      7. ConfigTargetSettings() end - Took 11us
      8. InitTarget() start
      9. SDA_AP detected
      10. Checking if debug access is already enabled...
      11. Debug access is not enabled yet. Performing enable debug access sequence...
      12. Debug access enabled
      13. Checking if HSE firmware is installed...
      14. HSE firmware not installed
      15. Checking if Cortex-M7_0 and Cortex-M7_1 are operating in lockstep mode
      16. Lock step mode enabled
      17. InitTarget() end - Took 27.5ms
      18. Found SW-DP with ID 0x6BA02477
      19. DPIDR: 0x6BA02477
      20. CoreSight SoC-400 or earlier
      21. AP map detection skipped. Manually configured AP map found.
      22. AP[0]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      23. AP[1]: APB-AP (IDR: Not set, ADDR: 0x00000000)
      24. AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      25. AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      26. AP[4]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      27. AP[5]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      28. AP[6]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      29. AP[7]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      30. AP[4]: Skipped ROMBASE read. CoreBaseAddr manually set by user
      31. AP[4]: Core found
      32. ConfigTargetSettings() start
      33. ConfigTargetSettings() end - Took 36us
      34. InitTarget() start
      35. SDA_AP detected
      36. Checking if debug access is already enabled...
      37. Core already 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 9.54ms
      43. Found SW-DP with ID 0x6BA02477
      44. DPIDR: 0x6BA02477
      45. CoreSight SoC-400 or earlier
      46. AP map detection skipped. Manually configured AP map found.
      47. AP[0]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      48. AP[1]: APB-AP (IDR: Not set, ADDR: 0x00000000)
      49. AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      50. AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      51. AP[4]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      52. AP[5]: AHB-AP (IDR: Not set, ADDR: 0x00000000)
      53. AP[6]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      54. AP[7]: MEM-AP (IDR: Not set, ADDR: 0x00000000)
      55. AP[4]: Skipped ROMBASE read. CoreBaseAddr manually set by user
      56. AP[4]: Core found
      58. ****** Error: DAP error while reading AIRCR.
      60. Error occurred: Could not connect to the target device.
      61. For troubleshooting steps visit: https://wiki.segger.com/J-Link_Troubleshooting
      Display All


      -If the reset pin is set to high, JLink is not able to read anything:

      Source Code

      1. Connecting to target via SWD
      2. ConfigTargetSettings() start
      3. ConfigTargetSettings() end - Took 12us
      4. InitTarget() start
      5. Unknown SDA AP Id detected: 0xFFFFFFFF
      6. InitTarget() end - Took 105ms
      7. Connect failed. Resetting via Reset pin and trying again.
      8. ConfigTargetSettings() start
      9. ConfigTargetSettings() end - Took 14us
      10. InitTarget() start
      11. Unknown SDA AP Id detected: 0xFFFFFFFF
      12. InitTarget() end - Took 105ms
      13. Error occurred: Could not connect to the target device.
      14. For troubleshooting steps visit: https://wiki.segger.com/J-Link_Troubleshooting
      Display All

      -The issue occurs on two pieces of hardware, of which one was in factory state, and I was unable to connect once I flashed the target with offending binary.
      -I've attached the logs I've created, there's a Saleae's logic analyzer files which contains dumps of SWD traffic.

      My questions:
      -How is it possible the JLink is unable to connect to the target, even if it is held in reset state? Does that mean that MCU is broken/bricked/locked-out somehow?
      -Does it look like MCU problem, or perhaps JLink's?
      -Is there a way to "unbrick" the devices?

      If something is unclear, please let me know.

      Thank you
      Files

      • logs.zip

        (21.46 kB, downloaded 422 times, last: )

    • Hi,

      We had same issue with S32K324.

      Our fix was to connect on another core (i.e. S32K324_M7_1) and erase from there.

      After that, we could connect to S32K324_M7_0 again.

      In our case HSE was not installed.