Sunday, May 20th 2018, 12:09pm UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

gregd

Beginner

Date of registration: Oct 31st 2011

Posts: 14

1

Wednesday, September 13th 2017, 7:45pm

[SOLVED] Error while compiling J-Link script file

Hello,

I just upgraded to IAR EWARM v8.11.3 which includes J-Link 6.18b. When I try to download to my LPC4350 M4 target using my J-trace Cortex M3, I get the following error dialog:

J-Link Driver
Error while compiling J-Link script file. Error while compiling, Line 46, column 3:
__int64 v; // We need 35 bits: 32 data, 2 bit addr, 1 bit RnW
Syntax error
Abort debug session?
Yes No

I also tried upgrading to v6.20 but the exact same problem still occurs.
I have attached the J-Link script file that is being used which came with the IAR v8.11.3 install.

Any ideas what would cause this.

Thanks,
Greg Dunn
gregd has attached the following file:

gregd

Beginner

Date of registration: Oct 31st 2011

Posts: 14

2

Wednesday, September 13th 2017, 8:41pm

For more added information, I just using the J-Link 6.14h Update utility to roll back the J-Link DLL for IAR 8.11.3 and the error went away.

I guess this means that something has changed between J-Link 6.14h and 6.20 that is causing the issue - I am assuming that something related to the __int64 type.

Thanks,
Greg Dunn

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

3

Thursday, September 14th 2017, 11:12am

Hi Greg,



I can confirm your observations.
int64 was a know variable type up to version 6.16, but was only used internally and did not support 64 bit variables (therefore, it was not officially documented).
However, we removed it as we saw that it was used by customers although it was not documented. It was important to remove it as it did not behave as expected. (therefore, it was not officially documented in the first place).

We plan to fully support 64 bit variables in script files later this year,

As a workaround for now:
I adjusted the script file. Could you please give it a try?

LPC4350_DebugCortexM4.JLinkScript.txt

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link

gregd

Beginner

Date of registration: Oct 31st 2011

Posts: 14

4

Friday, September 15th 2017, 3:40am

Thank you very much Niklas! That seems to have done the trick. I can at least download now without any error messages. I will let you know if I see any other issues as I work with it further.

Thanks again!
Greg Dunn

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691

5

Friday, September 15th 2017, 9:17am

Hi Greg,


good to hear that you are up and running again!

Best regards,
Niklas
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link