Issue with Multilink Universal Rev D Debugger – Session Termination During Flashing

By Dhanoosh B. : Sep 22, 2025 at 08:32 AM (08:32 hours)
Staff: Takao Y. : 5 comments

Overview:

Debugger: Multilink Universal Rev D

Port Used: Port A – JTAG/ONCE

Target MCU: MPC5775B

Software: S32 Design Studio for Power Architecture v2.1

Debugger Settings in IDE:

Debug Shift Freq: 5000 KHz

GDBMI Port: 6225

Server Port: 7225

Problem Description
We are facing repeated flashing issues on multiple Multilink Universal Rev D debuggers (around 4 units). When attempting to flash the firmware via JTAG, the debug session is terminated with the following errors:

Initial Warning:
“Device is not detected or may be censored. Please check connections or enter password in GDB server parameters using -uncensorpassword=n, then restart the debug session.”

Connection Error:
“An error occurred while connecting to the interface hardware or target specified in the launch configuration dialog. You may retry/re-specify the connection with the following parameters.”

Port is correctly detected.

BDM Debug Shift Freq shown:

Multilink = 1.00 MHz

Multilink FX = 25.00 MHz

OSJTAG = 0.25 MHz

Retrying leads to the same failure.

Abort Error:
“Error in services launch sequence – PEMicro GDB Launch Failure: The GDB Server was not able to establish a connection to the target processor. Please check your connection and power. Verify that the launch settings in the Debug configuration are accurate.”

Additional Notes

The MCU hardware and wiring have been validated — flashing works correctly with other working Multilink Universal Rev D debuggers.

The issue is only with certain units.

Multilink Firmware Update Attempt:
We tried updating using the Universal Multilink Firmware Update and Architecture Selection Utility v8.98.00.00. The process shows success (Current Firmware: 11.52). However, on reconnecting, the tool still detects the old firmware and repeats the update cycle without resolving the problem.

Reference Video
We have recorded the full process for clarity. Here is the Google Drive link: https://drive.google.com/file/d/1-_oWidsy5JYJX9mOOImHeNWduV_lxpTg/view?usp=sharing
(If this format is not accessible, please advise on the preferred way to share the video.)

Request
We kindly request your support to resolve this issue, as most of our Multilink Universal Rev D units are affected, and only a few work as expected.

Greetings,

I am sorry you are having difficulty with some of your mulilinks.
In your post you indicated rev D, however, watching your video I see rev E was used. Can you please confirm which revision you are using and which are working and which are not?


Takao

Hi Takao,

Thank you for the heads-up, and apologies for the earlier confusion. We observed the issue on one Rev E.2 board and three Rev D boards. The video shared was recorded on the Rev E.2 board, but we are experiencing a similar issue with the Rev D boards as well.

We also noticed that the issue sometimes resolves on its own without any corrective action, but it reappears randomly even after a proper flashing.

Additionally, we are facing challenges with flashing time. On some laptops, the process either takes unusually long or gets stuck, while on others, the same Multilink flashes without any problem.

Could you please share your suggestions on how we might address this issue?

Hi Takao,
A gentle reminder,
Can you please help us with possible solution addressing the issue mentioned above.

Hi Takao,
A gentle remainder regarding solution for the issue.