FRDM-KE06Z Hello World Connection Closed by GDB server Issue

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

FRDM-KE06Z Hello World Connection Closed by GDB server Issue

Jump to solution
8,850 Views
chris_lambrecht
Contributor III

I am using MCUXpresso v.11.2.0 Build 4120 with SDK 2.8.0 for the FRDM-KE06Z Evaluation Board. I have the Hello World example application compiling and was attempting to launch the debugger. I have not made any code modifications. I am running this on a Windows 10 laptop.

When I do this, unfortunately, I receive a "Connection closed by GDB server." message in the console window.

pastedImage_1.png

When I look at the Debugger Console window, I have the following:

pastedImage_2.png

I've done some searching on this without any luck yet. Has anyone else seen this issue? Any thoughts on next steps? The help is greatly appreciated. Thanks!

Labels (1)
0 Kudos
Reply
1 Solution
8,680 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

Thanks. This has been very helpful.

I was able to erase the KE06 with the Utility, but the P&E debugger still did not work. It gave me the GDB Server Connection error still.

When I installed the JLink tools, I didn't realize that something needed to be loaded onto the KE06 Eval Board.

The following link gave me a way to download the SW for the PC.

https://www.segger.com/products/debug-probes/j-link/models/other-j-links/opensda-sda-v2/#updating-a-... 

I found the following link so that I could download the binary file for the KE06 board for the JLink software.

https://www.segger.com/downloads/jlink#JLinkOpenSDABoardSpecificFirmwares 

I had to copy over the binary when the board booted up as bootloader. After that, it is displayed as FRDM-KE06KJ disk

pastedImage_4.png

After that I can connect to it via the JLink Debug and can step through the program.

I really appreciate the patience. Thanks for the help.

Chris

View solution in original post

0 Kudos
Reply
14 Replies
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi Chris,

First, please check if P&E driver is installed correctly.

You FRDM board may still have old openSDA bootloader. Please see here OpenSDA Serial and Debug Adapter | NXP 

PE bootloader v1.09 doesn't support win10 well. You can go into FRDM-KE06 virtual disk and double click SDA_INFO.HTM to see its version. If it's lower than v1.10, you must upgrade it.

http://www.pemicro.com/opensda/faqs/faqs.cfm

Regards,

Jing

0 Kudos
Reply
8,680 Views
chris_lambrecht
Contributor III

Hi [email protected]‌. Thanks for the suggestions. I believe that the P&E driver is installed correctly. At least there are no obvious warnings:

pastedImage_1.png

I also verified that the bootloader is v1.10:

pastedImage_2.png

I did uninstall and reinstall the P&E Drivers just to be sure. I tried it again and I'm still having the issue that the "Connection closed by the GBD server.".

Any other suggestions? Thanks for the help!

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi Chris,

Bootloader v1.10 is also not support win10.

pastedImage_1.png

Please find a windows XP or Windows 7 PC to perform update.

Regards,

Jing

0 Kudos
Reply
8,680 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

I found a Win 7 computer and updated the BootLoader to version 1.11.

pastedImage_1.png

I also updated the Application Version to 1.18. Unfortunately, I'm still receiving the "Connection closed by the GDB server." error.

pastedImage_2.png

I received the following error:

pastedImage_3.png

And in the Disassembly window, there is a "Failed to execute MI command:" message.

pastedImage_4.png

I believe that the Hello World program is fine. I can compile it and load the S record onto the FRDM-KE06Z board and it works with the PuTTY window. I think that there is an issue with the Debug connection itself, but I still haven't stumbled onto a solution with my searching.

Any ideas? Thanks!!

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

Please try Jlink firmware. 

Regards,

Jing

0 Kudos
Reply
8,680 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

I'm slightly confused with the JLink firmware.

In the MCUXpresso IDE User Guide, Section 10.8 says that the SEGGER Software is installed automatically with the IDE.

pastedImage_1.png

I verified that I have a C:\Program Files (x86)\SEGGER\JLink folder.

However, when I try to debug the program using the JLink drop down menu:

pastedImage_2.png

The MCUXpresso doesn't see any supported JLink probes.

pastedImage_3.png

It seems like there might be something missing (something needing to be installed), but that is contrary to what the IDE User Guide states. Can you help clear up my confusion?

Thanks.

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

Please try to install manually. If the firmware is download correct, it should not have any problem.

https://www.segger.com/downloads/jlink/JLink_Windows.exe 

Regards,

Jing

0 Kudos
Reply
8,681 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

Thanks for the link. I installed it and rebooted my maching (just in case it needed it).

During the installation, the following window popped up:

pastedImage_1.png

It didn't display that it found the MCUXpresso IDE. I still attempted to debug the program, but it still displays that there are no available probes:

pastedImage_2.png

It seems like I'm missing a step connecting the MCUXpresso to the JLink SW. But I haven't been able to determine what that step is. Ideas?

Thanks,

Chris

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

can you try to reinstall MCUXpresso?

Regards,

Jing

0 Kudos
Reply
8,680 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

I uninstalled MCUXpresso and reinstalled it. I also installed the latest JLink drivers again. It sill only found the Kinetis Design Studio during the installation (not the MCUXpresso).

I still have the same issue where there are no JLink Probes found.

The GDB Servers still closes the debugging session if I try to use the PEMicro connection.

Chris

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

segger's package has several tools. Please open J-link commander, input 'connect' command. Then step by step, can it find j-link and the chip?

Regards,

Jing

0 Kudos
Reply
8,680 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

When I open J-Link Commander, it automatically attempts to connect to a USB emulator. It can't find it and then asks if I would like to connect to one via Ethernet. Here is a screen capture of what I'm seeing:

pastedImage_1.png

The KE06 is up and running just fine when this is going on. It's up in Windows Explorer as Driver F:

pastedImage_2.png

Thoughts? Thanks for the help.

Chris

0 Kudos
Reply
8,680 Views
jingpan
NXP TechSupport
NXP TechSupport

Hi,

The firmware is not jlink. If you copied jlink firmware to openSDA, the disk name should be FRDM-KE06ZJ.

It is P&E. Please try to copy jlink firmware again.

By the way, There is a P&E tool which can erase kinetis. You can run it to see if P&E can work. (kinetis_recovery_utility)

https://community.nxp.com/message/946202?commentID=946202#comment-946202 

Regards,

Jing

0 Kudos
Reply
8,681 Views
chris_lambrecht
Contributor III

Hi jingpan‌,

Thanks. This has been very helpful.

I was able to erase the KE06 with the Utility, but the P&E debugger still did not work. It gave me the GDB Server Connection error still.

When I installed the JLink tools, I didn't realize that something needed to be loaded onto the KE06 Eval Board.

The following link gave me a way to download the SW for the PC.

https://www.segger.com/products/debug-probes/j-link/models/other-j-links/opensda-sda-v2/#updating-a-... 

I found the following link so that I could download the binary file for the KE06 board for the JLink software.

https://www.segger.com/downloads/jlink#JLinkOpenSDABoardSpecificFirmwares 

I had to copy over the binary when the board booted up as bootloader. After that, it is displayed as FRDM-KE06KJ disk

pastedImage_4.png

After that I can connect to it via the JLink Debug and can step through the program.

I really appreciate the patience. Thanks for the help.

Chris

0 Kudos
Reply