Hi Team,
I am using an S32K344 EVB with a PEmicro 10-pin JTAG/SWD debug probe and S32 Design Studio (S32DS) version 3.6.8.
I would like to flash an application into the normal internal Program Flash of the S32K344. I am not using HSE Secure Boot, Secure Debug, or any other security features.
Could someone please provide the detailed steps for:
- Connecting the PEmicro 10-pin JTAG/SWD debugger to the S32K344 EVB.
- Creating the correct Debug/Run configuration in S32DS 3.6.8.
- Selecting the proper interface (SWD or JTAG).
- Configuring flash programming settings (Erase, Program, Verify).
- Setting the correct target device and connection mode.
- Any required linker or memory configuration for standard internal flash programming.
- Recommended settings to avoid Secure Debug/HSE-related issues.
- Troubleshooting steps if the debugger detects the device but fails during flash programming.
I am looking for a complete flashing procedure and the exact S32DS configuration required for successful programming and debugging of the S32K344 EVB using a PEmicro probe.
Thank you.
Hello @Aravind_Togaralli ,
Thank you for the clarification and screenshots.
Before changing the S32DS configuration, please verify the debugger connection on the board. If you are using the FRDM-A-S32K344, previously referred to as the S32K344MINI-EVB, the external debugger must be connected to the J9 20-pin Cortex Debug + ETM header. According to UM12406, Table 1, jumper JP11 must be removed to enable the external debug interface.
Therefore, please check the following:
- Confirm that the external PEmicro Multilink is connected to J9, which is a 20-pin debug header. Your description mentions an external 10-pin connector, so please verify the connector and any adapter being used.
- Remove JP11 when using the external Multilink debugger.
- Verify the orientation of the debug cable and pin 1 alignment.
- Power-cycle the board and the Multilink after changing JP11, then refresh the Port selection in the PEmicro debug configuration.
As an initial bring-up test, you can alternatively use the on-board debugger with JP11 installed. This can help determine whether the project and MCU are working before switching to the external Multilink.
You can also use the following verified project as a reference:
Example S32K344 EMAC lwIP FreeRTOS miniEVB, S32DS 3.6.1, RTD 6.0.0
This project was tested on the S32K344MINI-EVB using the on-board debugger and the Debug_FLASH configuration. Please try launching this project first and compare its Debug_FLASH settings with your current project.
If the on-board debugger works but the external Multilink does not, the problem is most likely related to the external debug path, particularly JP11, the J9 connection, cable orientation, or adapter. In that case, you may also try another USB port and USB cable, preferably with the Multilink connected directly to the PC without a docking station or USB hub.
Related discussions:
If the issue remains, please provide:
- a photo showing the debugger connection to the board,
- the exact adapter used between the Multilink and J9, if applicable,
- the complete PEmicro GDB server output from the S32DS Console.
Please also note that I will be out of office for the next few days, so my responses may be delayed.
Best regards,
Pavel
Following up on my earlier query. I followed the steps your team suggested, but I'm still unable to flash/debug the device — the connection fails during launch.
Setup:
Board: Custom board with S32K344 (not an NXP EVB)
Probe: P&E Multilink Universal FX Rev D, connected via external 10-pin JTAG connector on the board (I am not using an onboard/embedded debugger — I explicitly selected the external Multilink FX port under "Port" in the debug configuration, as shown in the screenshots)
IDE: S32DS, Debug Configuration = GDB PEmicro Interface Debugging
Interface settings: SWD protocol enabled, Debug Shift Freq = 5000 KHz, "Provide power to target" enabled
What happens:
On clicking Debug, the PEmicro Connection Assistant pops up with: "An error occurred while connecting to the interface hardware or target specified in the Launch Configuration Dialog," prompting me to retry the connection with the same USB Multilink port.
Attached screenshots:
Debug Configuration — Main tab (project/elf selected)
PEmicro Debugger tab — Interface, Port, Target device (S32K344), Core (M7), SWD enabled, Power settings
PEmicro Debugger tab (scrolled) — Debug Shift Freq, GDB Server/Client settings
PEmicro Connection Assistant error popup after failed connect attempt
Thanks,
Hello @Aravind_Togaralli ,
This setup was discussed recently in the following thread:
For the detailed PEmicro debug configuration procedure, please also refer to:
For standard internal flash programming without HSE or AB Swap, the automatically generated PEmicro debug configuration and the default flash programming algorithm should be used. No special linker configuration is required.
Please follow the referenced procedure first. If it fails, provide the exact board name, PEmicro probe model and revision, screenshots of the debug configuration, and the complete PEmicro console log. This will allow us to identify the actual point of failure.
Best regards,
Pavel