I get this error when I'm using Segger
I selected the segger configuration
Why doesn't this work?
I get this error when I'm using Segger
I selected the segger configuration
Why doesn't this work?
Hi Adrain Muresan,
What's the chip part number you are using now? Do you use the official board or your own designed board?
At first, I suggest you use the JLINK commander to check whether you can find the ARM core or not?
If even JLINK commander which in the JLINK driver install path also can't find the ARM core, it means your hardware have problems, you need to check the hardware connections.
Please test this point at first, and give me the the JLINK commander screen shoot.
With is helps you!
Have a great day,
Kerry
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
If you already have the GDB server running locally (see Command Line Programming and Debugging with GDB | MCU on Eclipse ), then you shall not launch yet another copy, so uncheck this:
I hope this helps,
Erich
I did. Still same issue.
Do not start the J-Link Server exectuable externally. Let the debugger launch it (unless you know exactly what you are doing).
And do not forget to specify the project name (see other reply).
I hope this helps,
Erich
If I don't start it externally and I uncheck that box, how is the server launched?
Also I'm pretty sure I started it correctly.
It starts the server locally (as indicated in the checkbox).
I tried switching to MCUXpresso but alas, you guys appear to not want to support SEGGER.
Can you share/show your launch configuration settings?
That message usually tells you that it was not able to find binary, see Troubleshooting Tips: Failed Debugging with GDB | MCU on Eclipse
I hope this helps,
Erich
No it doesn't help.
KDS is calling the wrong executable: it's not supposed to be calling "arm-none-eabi-gdb" for the SEGGER.
I set the Segger GDB path
you have the launch config wrong:
You need to specify a project there.
And yes: gdb is the client talking to the SEGGER gdb server, see Command Line Programming and Debugging with GDB | MCU on Eclipse
I hope this helps,
Erich
I figured it out:
I had to manually specify the highlighted field
I figured it out:
I had to manually specify the highlighted field