GDB server fails to start

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

GDB server fails to start

Jump to solution
4,119 Views
stevescott
Contributor II

Target is FRDM-KL27Z .

Running on Windows 7, 64-bit

Kinetis Design Studio, Version: 3.2.0

GNU ARM PEMicro Interface Debugging Support 2.6.0.201610062322

 

Trying to launch debugger using OpenSDA USB, I get an error:

 

166175_166175.pngpastedImage_2.png

 

Followed by:

 

166176_166176.pngpastedImage_3.png

 

 

I'm not sure if it's a hardware problem with my target board or an installation problem with the SDK, or other...???

 

Any help/feedback would be appreciated.

 

 

Thanks.

Labels (1)
0 Kudos
1 Solution
3,270 Views
stevescott
Contributor II

This was a hardware issue. Several jumpers (J5,J6,andJ7) were missing. These jumpers isolated the OpenSDA USB from the MCU. The host could still see the OpenSDA processor, but couldn't get to the MCU. The gdb server launch failure was just a side effect.

View solution in original post

0 Kudos
3 Replies
3,271 Views
stevescott
Contributor II

This was a hardware issue. Several jumpers (J5,J6,andJ7) were missing. These jumpers isolated the OpenSDA USB from the MCU. The host could still see the OpenSDA processor, but couldn't get to the MCU. The gdb server launch failure was just a side effect.

0 Kudos
3,270 Views
BlackNight
NXP Employee
NXP Employee

Have you checked if there is not another instance of the P&E GDB server running? See https://mcuoneclipse.com/2014/11/03/debugging-failure-check-list-and-hints/  and https://mcuoneclipse.com/2015/05/18/gdb-client-and-server-unlocking-gdb/ .

I hope this helps,

Erich

0 Kudos
3,270 Views
stevescott
Contributor II

Yes. There is no other copy of the server running. It appears to be a misleading error message. I think the real problem is not being able to connect to the target. 

0 Kudos