[ANSWERED]J-Link script files are not working in version 4.12

Superbank · Mar 14th 2010, 12:23pm

If I create a J-Link Script file with commands like JTAG.IRLen, JTAG.Speed, CPU etc. and name this file as "Default.JLinkScript", then run JLink.exe - these commands are ignored, only DIALOG.MessageBox is popping up to reveal that the script file is actually being processed.

Probably the scripting language has been changed but the "J-Link / J-Trace ARM Manual Rev. 83" (Document: UM08001 dated February 24, 2010, "User guide of the JTAG emulators for ARM Cores") is not updated to reflect the changes...

SEGGER - Alex · Mar 18th 2010, 8:48am

Hi Superbank,

could you please post or attach the complete scrip file you are using?
Which target MCU/CPU do you use?
The syntax of the script file commands has not been changed, so it should work without any problems.
But if the DIALOG.MessageBox command is executed, I do not see any reason why the other ones
should be ignored (at least if you are using a incorrect syntax, a error message should appear).

Best regards
Alex

Superbank · Mar 19th 2010, 10:07am

The script is very short:

Dialog.MessageBox("Setting up the target");
JTAG.IRLen=4;
JTAG.Speed=5;
CPU=arm926ejs;

SEGGER - Alex · Apr 7th 2010, 9:31am

Hi Superbank,

the scriptfile and all commands of it are executed.
The only misleading thing is the JTAG speed:
All identification routines, automatically performed by JLink.exe at startup, are performed using the JTAG speed which is set in the init file.
But the last action of JLink.exe performed after the auto-startup is, to change the JTAG speed to a default speed.
This does not hurt here, but is misleading since it seems, that the set-speed command in the script file has been ignored.

I think we should change this behavior of JLink.exe for future versions.

Best regards
Alex

Share