[SOLVED] JLinkGDBServer does not use script file

erazor · Jan 6th 2022, 10:20am

I'm using a JLink EDU under Linux. With the command line JLinkGDBServer -device ARM9 -endian little -speed 15000 -port 2331 I can connect to the device and debug it.
Now I want to use a jlinkscript and to start I wrote a small test.

C Source Code: Test.JLinkScript

int InitTarget(void) {
JLINK_SYS_Report("Test");
CPU = ARM9;
return 0;
}

If I try to start this with JLinkGDBServer -endian little -speed 15000 -port 2331 -jlinkscriptfile "Test.JLinkScript" it doesn't work. It complains about an unspecified device and the "Test" string is nowhere to be seen.

What is wrong with my script?

Other unclear things:
- The prototype for function InitTarget in the documentation is int InitTarget(void) but it is also used as void InitTarget(void). Can these uses be exchanged freely?
- The documentation of global DLL constants state there are values like "ARM926EJS" for the CPU variable. These do not appear in the selection dialog for unspecified targets. Are these values still valid?

SEGGER - Alex · Jan 7th 2022, 10:05am

Hi,

If you pass the device name via the -device option to GDB Server, there is no need to have the "CPU = ARM9" statement in the script.
Also, GDBServer expects you to select the device inside GDBServer (e.g. by passing the -device option).
The script file is a black box for GDB Server and just forwarded to the J-Link DLL.
The "CPU = " option in the script file is mainly there for some exotic overrides for buggy IDEs.

Long story short:
Go for the "-device" option and you are set.

BR
Alex

[SOLVED] JLinkGDBServer does not use script file

[SOLVED] JLinkGDBServer does not use script file

C Source Code: Test.JLinkScript

Share

Tags