Hi,
We have multiple Flasher ARMs - I have however only tried this with on a version 4.02 unit with latest firmware (15th June 2022).
I have tried with both the J-Link v.7.92k and an older v7.64 - same results:
I get the following in J-Flash when using Production Programming (F7):
Display All
When I use the generated cfg and dat files on the same Flasher ARM in serial/ASCII control mode I get (#AUTO is issued by user):
We don't have any issues with other more moderns MCUs like Renesas RA6 series or NXP Kinetis series.
The only way I'm able to connect with the ADuC7124 is with a fixed frequency of <800 kHz, which is noted as an errata in the data sheet. I cannot use Adaptive Mode, even though RTCK is connected.
Another thing that I find confusing is the JTAG chain identifiers.
In J-link Commander I get the following, when connecting:
Display All
Shouldn't this ID be the same as in the J-Flash project? No matter what, J-Flash determines two IDs, and when entering 0x028031CB as #1 and pressing verify, I receive the following info as shown in the attached picture.
The behavior is exactly the same with version 7.92k.
Any help would be greatly appreciated in solving this, as this stalls everything unfortunately.
Many thanks.
EDIT: Prior to editing, it was mentioned that RESET was not connected from Flasher ARM to MCU - this is not true, it was connected, and pulled up externally by 33kOhm.
We have multiple Flasher ARMs - I have however only tried this with on a version 4.02 unit with latest firmware (15th June 2022).
I have tried with both the J-Link v.7.92k and an older v7.64 - same results:
I get the following in J-Flash when using Production Programming (F7):
Source Code
- Application log started
- - J-Flash V7.64 (J-Flash compiled Apr 1 2022 16:09:44)
- - JLinkARM.dll V7.64 (DLL compiled Apr 1 2022 16:09:20)
- Reading flash device list [C:\Program Files\SEGGER\JLink_V764\ETC/JFlash/Flash.csv] ...
- - List of flash devices read successfully (451 Devices)
- Reading MCU device list ...
- - List of MCU devices read successfully (9241 Devices)
- Opening project file [C:\HIDDENDATA.jflash] ...
- - Project opened successfully
- Opening data file [C:\HIDDENDATA.hex] ...
- - Data file opened successfully (20409 bytes, 3 ranges, CRC of data = 0xBBAA184C, CRC of file = 0x99C0DE3D)
- Connecting ...
- - Connecting via USB to probe/ programmer device 0
- - Probe/ Programmer firmware: J-Link ARM / Flasher ARM V4 compiled Jun 15 2022 11:03:00
- - Device "ADUC7124" selected.
- - Target interface speed: 400 kHz (Fixed)
- - VTarget = 3.314V
- - ADI system TAP: Connecting to device with system TAP.
- - TotalIRLen = 5, IRPrint = 0x11
- - JTAG chain manually configured. JTAG chain auto-detection skipped
- - JTAG chain detection found 2 devices:
- - #0 Id: 0x4F1F0F0F, IRLen: 04, Unknown device
- - #1 Id: 0x006397FF, IRLen: 05, Unknown device
- - Executing init sequence ...
- - Initialized successfully
- - Target interface speed: 400 kHz (Fixed)
- - Found 2 JTAG devices. Core ID: 0x4F1F0F0F (None)
- - Connected successfully
- Auto programming target (20409 bytes, 3 ranges) ...
- - Checking if selected data fits into selected flash sectors.
- - Start of preparing flash programming
- - End of preparing flash programming
- - Start of determining dirty areas in flash cache
- - End of determining dirty areas
- - CPU speed could not be measured.
- - Start of erasing sectors
- - Blank checking 0x00080000 - 0x00084FFF
- - Erasing range 0x00080000 - 0x00084FFF ( 40 Sectors, 20 KB)
- - Blank checking 0x00086000 - 0x000861FF
- - End of erasing sectors
- - Start of flash programming
- - Programming range 0x00080000 - 0x00084FFF ( 40 Sectors, 20 KB)
- - Programming range 0x00086000 - 0x000861FF ( 1 Sector, 512 Bytes)
- - End of flash programming
- - Flash programming performed for 2 ranges (20992 bytes)
- - 0x80000 - 0x84FFF ( 40 Sectors, 20 KB)
- - 0x86000 - 0x861FF ( 1 Sector, 512 Bytes)
- - Start of verifying flash
- - End of verifying flash
- - Start of restoring
- - End of restoring
- - Executing exit sequence ...
- - De-initialized successfully
- - Target erased, programmed and verified successfully - Completed after 2.989 sec
When I use the generated cfg and dat files on the same Flasher ARM in serial/ASCII control mode I get (#AUTO is issued by user):
We don't have any issues with other more moderns MCUs like Renesas RA6 series or NXP Kinetis series.
The only way I'm able to connect with the ADuC7124 is with a fixed frequency of <800 kHz, which is noted as an errata in the data sheet. I cannot use Adaptive Mode, even though RTCK is connected.
Another thing that I find confusing is the JTAG chain identifiers.
In J-link Commander I get the following, when connecting:
Source Code
- SEGGER J-Link Commander V7.64 (Compiled Apr 1 2022 16:10:38)
- DLL version V7.64, compiled Apr 1 2022 16:09:20
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link ARM / Flasher ARM V4 compiled Jun 15 2022 11:03:00
- Hardware version: V4.02
- S/N: 164215482
- License(s): JFlash, GDB
- IP-Addr: 192.168.6.12
- VTref=3.309V
- Type "connect" to establish a target connection, '?' for help
- J-Link>connect
- Please specify device / core. <Default>: ADUC7124
- Type '?' for selection dialog
- Device>
- Please specify target interface:
- J) JTAG (Default)
- TIF>
- Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. <Default>: 4000 kHz
- Speed>400
- Device "ADUC7124" selected.
- Connecting to target via JTAG
- ADI system TAP: Connecting to device with system TAP.
- TotalIRLen = 5, IRPrint = 0x11
- TotalIRLen = 5, IRPrint = 0x11
- JTAG chain detection found 1 devices:
- #0 Id: 0x028031CB, IRLen: 05, System level TAP
- ARM7 identified.
- J-Link>
The behavior is exactly the same with version 7.92k.
Any help would be greatly appreciated in solving this, as this stalls everything unfortunately.
Many thanks.
EDIT: Prior to editing, it was mentioned that RESET was not connected from Flasher ARM to MCU - this is not true, it was connected, and pulled up externally by 33kOhm.