Hi!
Since v7.88l JLINK.EXE refuses to run my scripts properly (with jlink plus connected):
Skript1 - last command "connect" not executed:
device R7FA2E1A9
si SWD
speed 4000
connect
"C:\Program Files\SEGGER\JLink\jlink.exe" -device R7FA2E1A9 -CommanderScript RA2E1_connect_flash_test.jlink
SEGGER J-Link Commander V7.92d (Compiled Sep 8 2023 09:56:39)
DLL version V7.92d, compiled Sep 8 2023 09:55:04
J-Link Command File read successfully.
Processing script file...
connect000ice R7FA2E1A9
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Jan 30 2023 11:28:07
Hardware version: V10.10
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 600111968
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.248V
Script processing completed.
Type "connect" to establish a target connection, '?' for help
Display More
After further investigation I suppose that only the first line is executed properly, if device, speed and interface is given already as command line parameter before that.
Skript2:
erase 0x40100000, 0x40100FFF, reset
erase 0x40100000, 0x401000FF, reset
loadfile testfile.hex
results in:
"C:\Program Files\SEGGER\JLink\jlink.exe" -device R7FA2E1A9 -if SWD -speed auto -CommanderScript RA2E1_connect_flash_test.jlink
SEGGER J-Link Commander V7.92d (Compiled Sep 8 2023 09:56:39)
DLL version V7.92d, compiled Sep 8 2023 09:55:04
J-Link Command File read successfully.
Processing script file...
loadfile testfile.hex01000FF, reset, reset
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Jan 30 2023 11:28:07
Hardware version: V10.10
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 600111969
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.241V
Target connection not established yet but required for command.
Device "R7FA2E1A9" selected.
Connecting to target via SWD
InitTarget() start
Identifying target device...
SWD selected. Executing JTAG -> SWD switching sequence...
Initializing DAP...
DAP initialized successfully.
InitTarget() end - Took 20.8ms
Found SW-DP with ID 0x5BA02477
DPIDR: 0x5BA02477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x74770001)
AP[1]: APB-AP (IDR: 0x44770002)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0x4001A000
CPUID register: 0x411CD200. Implementer code: 0x41 (ARM)
Feature set: Baseline
Cache: No cache
Found Cortex-M23 r1p0, Little endian.
Cortex-M (ARMv8-M and later): The connected J-Link (S/N 600111969) uses an old firmware module that does not handle I/D-cache corr
ectly. Proper debugging functionality cannot be guaranteed if cache is enabled
FPUnit: 4 code (BP) slots and 0 literal slots
Security extension: not implemented
CoreSight components:
ROMTbl[0] @ 4001A000
[0][0]: E000E000 CID B105900D PID 000BBD20 DEVARCH 47702A04 DEVTYPE 00 Cortex-M23
[0][1]: E0001000 CID B105900D PID 000BBD20 DEVARCH 47701A02 DEVTYPE 00 DWT
[0][2]: E0002000 CID B105900D PID 000BBD20 DEVARCH 47701A03 DEVTYPE 00 FPB
[0][3]: 40019000 CID B105900D PID 000BBD20 DEVARCH 47710A31 DEVTYPE 31 MTB
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M23 identified.
'erase': Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Erasing selected range...
CPU is running at low speed (8000 kHz).
J-Link: Flash download: Total time needed: 0.233s (Prepare: 0.151s, Compare: 0.000s, Erase: 0.052s, Program: 0.000s, Verify: 0.000
s, Restore: 0.029s)
J-Link: Flash download:
Flash sectors within Range [0x40100000 - 0x40100FFF] deleted.
Erasing done.
Script processing completed.
Type "connect" to establish a target connection, '?' for help
Display More
As you can see after "Processing script file...", there is something wrong.
I tested all versions x86_x64 since v7.86f till v7.92d.
Can anyone confirm that behaviour? Did I miss something in the release notes?
Perhaps it has something to do with
7.88l:
Other changes:
Commander
If a C/C++ comment was used in a command that accepts parameters, the comment was accidentally interpreted as parameter. Fixed.
Best regards,
HaJo