Hi Guys,
I am getting the same compile error with the __int64 data type in our JLinkScript which has been already reported by Jiri and marked as solved.
The mentioned solution should be a replacement with the data type int, but how should this work in the following script and how has is worked in the past?
__int64 ScanData;
ScanData = 0;
ScanData |= (Reg << 32);
ScanData |= (0 << 37);
JTAG_StoreDR(ScanData, 38);
Joerg

Hi guys,
I've searched the install directory of JLink V6.16e and found the "__int64" string used in the following seven segger sample files:
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JFlash\ProjectFiles\Spansion\MB9EF126.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JFlash\ProjectFiles\Spansion\MB9DF126.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JFlash\ProjectFiles\Spansion\MB9DF125.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JFlash\ProjectFiles\Spansion\MB9EF226.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JLink\Scripts\DigiConnectCoreWi-iMX51.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JLink\Scripts\CogentCSB740Board_OMAP3550.JLinkScript
C:\Program Files (x86)\SEGGER\JLink_V616e\Samples\JLink\Scripts\ScriptBeagleBoard_OMAP3530.JLinkScript
So why are you guys removing the "__int64" data type without correcingt your script samples?
Regards
Joerg