S32K3X4EVB-T172 Unable to Program using OpenSDA

[tllorens]

I have a fresh-out-the-box S32K3X4EVB-T172 Eval board. The S32 processor seems to be running some factory default code, but when I try to debug/reprogram using the on-board debugger (connected to my computer using USB) both the S32 and the on-board debugger go into reset.

I am using the correct Power On/Plug in procedure as described by the S32K3X4EVB-T172 quick start guide. I also have installed the software and addons described there as well.

Tried same process with a co-worker's S32K3X4EVB-Q172 and it worked just fine.\

Thanks in advance,

-Tobiah

[Robin_Shen]

1. Please refer to the discussion: PEmicro Connection Assistant Issue on S32K3X4EVB-T172. Do the red LEDs D15(RST_OSDA) and D3(RESET_K3) remain lit, or do they flash periodically? Is your board experiencing the same issue as this customer?

2. Is FS26(U12) hot?

3. Did you follow the steps "3.2 Plug in the Power Supply" and then "3.3 Connect the Debugger Cable"?

4. Plug in the J40 micro-USB cable and observe the D14STATUS OSDA LED.
If the D14 orange LED does not light up: Check whether the USB cable is a data cable, verify if the PC enumerates the OpenSDA device, and ensure the USB port and drivers are functioning correctly. Connecting the USB cable to the PC via a USB hub is not recommended.

5. The onboard debugger is provided by PEMicro, it is recommended to download the latest "USB Multilink Resources Installer" from the "Support & Downloads" category of the "Multilink Debug Probes". After installation, open PEFirmwareConfig.exe located in C:\PEMicro\Multilink_Resources to check the firmware version. My onboard debugger's firmware version is 10.98. What version is your board? If the version is too old, it is recommended to update. If the update fails, it is recommended to contact PEMicro technical support.

check the version of firmware on S32K3X4EVB-T172.png

6. Please use a multimeter in voltage mode or an oscilloscope to observe the voltage of P3V3_SDA (J34).

S32K3X4EVB-T172_PackRevB2_Schematic P3V3_SDA J34.png

7. The SDA_RST_TGTMCU is controlled by the output of the onboard debugger K26. If the SDA_RST_TGTMCU outputs a low level, both red LEDs D15 and D3 will light up.

Please observe the SDA_RST_TGTMCU (J36) level using an oscilloscope. Is it always low, or is it periodically pulled low?

Normally, when downloading a program or resetting the S32K3 via the onboard debugger, a 10ms low level should be observed in the SDA_RST_TGTMCU, causing red LEDs D15 and D3 to light up briefly.

8. Is it possible to debug the onboard S32K3 chip after connecting via J12 using an external debugger?

Best Regards,
Robin

[tllorens]

Finally got a JTAG adapter that works for J12. I can debug the S32K344 chip using an external debugger. OpenSDA still doesn't work.

[tllorens]

After some more testing:
5. I was able to update the onboard debugger firmware using the PEFirmwareConfig exe.  The behavior remains the same though when I try to debug/program.

6. J34 voltage is at 3.25V when USB is plugged in.

7. J36 is high until I try to debug/program. At which point it goes low and stays low until the micro USB is disconnected.

Still waiting on an adapter for point 8.  It should arrive today.

Thank you,

-Tobiah

[Robin_Shen]

Please check whether the jumper settings match those described in "3.1 Set Up Jumpers in the S32K3X4EVB-T172 Evaluation Board."

Is the input voltage for J14 12V?

Which project did you debug? Would it be possible for you to record a video of the debugging process and share it with me?

[tllorens]

The jumper settings do match.

J16 is showing 12V (seemed easier than measuring the jack directly).

I am using the project Port_Example_S32K344 as recommended in the quick start guide.  I don't think I will be able to video.

-Tobiah

[Robin_Shen]

Please take a photo of the S32K3X4EVB-T172 board after connecting the external 12V power supply to J14 and plugging in the USB cable; the image must be clear enough to show the jumper settings and which LEDs are lit.

Please record a video of the S32DS interface, starting from when you click the debug button and continuing until the error screen appears. This will allow me to see exactly what is happening and help troubleshoot the issue quickly. If you cannot record a video of the operations performed in S32DS on the screen, could you take a few screenshots to show the error?

[tllorens]

Good morning,

00_evb.jpg

 ^ Initial state of board after power on and connection of USB

00_dashboard.png

 ^ Example project dashboard

03_debug3.png

01_debug1.png

02_debug2.png

   ^Debug configuration

04_error1.png

 ^ first error after debug

04_evb.jpg

 ^ EVB after attempted debug (happens at the same time as the above error)

05_error2.png

 ^ error after clicking abort

 

[Robin_Shen]

I am not sure which version of the RTD Port_Example_S32K344 you are currently testing.
However, I suggest setting J31 to positions 2-3 and trying again.

[tllorens]

How can I determine what the version of the example project is?

I switched J31 to 2-3. Same behavior.
Thanks,
-Tobiah

[tllorens]

Hello Robin,

1. Once I attempt to debug/program, both LEDs (D15 and and D3) remain lit. They do not flash.  I believe my board is experiencing the same issue as the customer in https://community.nxp.com/t5/S32K/PEmicro-Connection-Assistant-Issue-on-S32K3X4EVB-T172/m-p/2252525, but it seems he bypassed his issue by purchasing another EVB, which is unfortunate.

2. no

3. yes

4. D14 does light up when I plug in the micro-USB cable.  Device Manager shows "OpenSDA - CDC Serial Port (http://www.pemicro.com/opensda)".  There is no USB hub in the system, and my PC+cable can program other S32K344 EVBs using S32DS.  The issue seems tied specifically to this board.

5-7.  Give me some time to run these down.  I will respond shortly.

8. I have yet to try to JTAG directly as I am waiting on an adapter so I can interface with J12.

Thank you for your detailed response,

-Tobiah