Error in services launch sequence PEmicro GDB Launch Failure : The GDB Server was not able to establ

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error in services launch sequence PEmicro GDB Launch Failure : The GDB Server was not able to establ

3,510 Views
zenging
Contributor I

I recently got an error message on my own board. My board uses S3K311 and the burner is U-MULTILINK, both of the burner's lights are on.
Can you give me some advice?
1.png2.png3.png

0 Kudos
Reply
6 Replies

3,473 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @zenging 

Have you programmed the chip successfully before?

We understand that you are using a custom board. If it is correct, verify your hardware connections (refer to section 4.2 JTAG and TRACE interface of the Hardware Design Guidelines for S32K3xx Microcontrollers) and the power.

Also, observe the waveform of the RESET pin with an oscilloscope and upload a image.

 

BR, VaneB

0 Kudos
Reply

3,462 Views
zenging
Contributor I

Hello, @VaneB

 
1. I've been successful on the same board before. After that, it's the same error regardless of other boards.
2. The picture below is my pin picture and connection picture. I selected J7-2 to connect Port B-7.       J7-4 to connect Port B-9,       J7-6 to connect Port B-13,        J7-8 to connect Port B-5,          and J7-10 to connect Port B-15.        In addition, I also connected the VCC and GND of J7 to Port B.When I do not connect VCC to GND, one of the U-multilink lights will not be lit. I don't have the document you asked me to refer to. If possible, I hope you can send me a copy for my study.
1-1.png1-1.png1-1.png1-1.png1-1.png1-1.png
1-2.png
3. This is the waveform of my RESET pin. I should note that this waveform is only available when I do not connect VCC to GND. When I connected VCC and GND to Port B, the Reset waveform disappeared.
1-3.jpg

best regard,
zenging

0 Kudos
Reply

3,418 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @zenging 

"I've been successful on the same board before. After that, it's the same error regardless of other boards." 

Based on this information, since you were able to flash the MCU before, it seems that a possible root cause of the problem could be your debugger. Could you try with another debugger? Also, just to be sure, did your computer detect the debugger?

0 Kudos
Reply

3,382 Views
zenging
Contributor I

HI,@VaneB 

  1. About the debugger, I recently bought this one, there is no other debugger, in addition, I can find the debugger on my computer.

    2-1.png

  2. I wonder if there are other problems. As for the waveform of reset pin I explained to you in the third point before, is it correct? Its waveform is periodically pulled up and down before the debugger is connected. The output waveform remains low after the debugger is connected
    2-3.jpg2-2.jpg
0 Kudos
Reply

3,304 Views
VaneB
NXP TechSupport
NXP TechSupport

Hi @zenging 

In the debug configurations go to the Startup tab 
 VaneB_0-1723830042249.png

and select the following:

 VaneB_1-1723830042085.png

With this, instead of loading the executable, we will verify if it is possible to attached to the microcontroller with the debugger. 

Also, could you please clarify what you mean by "when I do not connect VCC to GND"?

0 Kudos
Reply

3,428 Views
zenging
Contributor I
Note that the waveform disappearance I mentioned above means that when VCC and GND and Jtag five wires are connected to the multilink burner, the reset pin is always low at this time.
0 Kudos
Reply