[SOLVED] IMXRT1020 will not program on secondary pinmux

dmarples · February 10, 2020 at 11:34 PM

Hi, Current release (V6.62a) and Beta (V6.63b) will not program my device which is on FlashSPI alternate config. Reverting to V6.56d fixes the issue. Interaction sequence is attached. I cannot send the hex file because it's too big for the forum but you can send me PM and I'll send it to you.

Regards

DAVE

Code

$ JLinkExe 
SEGGER J-Link Commander V6.63b (Compiled Feb  7 2020 17:27:18)
DLL version V6.63b, compiled Feb  7 2020 17:27:03


Connecting to J-Link via USB...O.K.
Firmware: J-Trace PRO V2 Cortex compiled Jan  7 2020 16:55:37
Hardware version: V2.00
S/N: 93200XXXX
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 172.26.172.168
Emulator has RAWTRACE capability
VTref=3.309V




Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMXRT1021XXX5A
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMXRT1021XXX5A" selected.




Connecting to target via SWD
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
ROMTbl[0][0]: E00FE000, CID: B105100D, PID: 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
ROMTbl[1][0]: E00FF000, CID: B105100D, PID: 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
ROMTbl[2][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[2][1]: E0001000, CID: B105E00D, PID: 000BB002 DWT
ROMTbl[2][2]: E0002000, CID: B105E00D, PID: 000BB00E FPB-M7
ROMTbl[2][3]: E0000000, CID: B105E00D, PID: 000BB001 ITM
ROMTbl[1][1]: E0041000, CID: B105900D, PID: 001BB975 ETM-M7
ROMTbl[1][2]: E0042000, CID: B105900D, PID: 004BB906 CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BB9A9 TPIU-M7
ROMTbl[0][2]: E0043000, CID: B105F00D, PID: 001BB101 TSG
Cache: Separate I- and D-cache.
I-Cache L1: 16 KB, 256 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 16 KB, 128 Sets, 32 Bytes/Line, 4-Way
Cortex-M7 identified.
J-Link>mem 0x60000000 128
60000000 = FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  ................
60000010 = FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  ................
<SNIP>
60000110 = FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  ................
60000120 = FF FF FF FF FF FF FF FF                           ........
J-Link>loadfile /XXXXX/Builds/circuitpython/ports/mimxrt10xx/build-versiboard2/firmware.hex
Downloading file [/XXXXX/Builds/circuitpython/ports/mimxrt10xx/build-versiboard2/firmware.hex]...
Comparing flash   [100%]Erasing flash     [100%] Done.


****** Error: PC of target system has unexpected value after erasing sectors. (PC = 0x00000000)!
---------------------------------------------------------------------- Registers -------------------------------------------------------------------------------------
    	PC   = 00000000
Current:	R0   = 00000000,	R1   = 00000000,	R2   = 00000000,	R3   = 00000000
    	R4   = 00000000,	R5   = 00000000,	R6   = 00000000,	R7   = 00000000
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Failed to erase sectors.
Can not read register 15 (R15) while CPU is runningCan not read register 7 (R7) while CPU is runningCan not read register 6 (R6) while CPU is runningCan not read register 5 (R5) while CPU is runningCan not read register 4 (R4) while CPU is runningCan not read register 3 (R3) while CPU is runningCan not read register 2 (R2) while CPU is runningCan not read register 1 (R1) while CPU is runningCan not rea
Unspecified error -1
J-Link>q
dmarples@precision:~$ JLinkExe 
SEGGER J-Link Commander V6.56d (Compiled Dec 12 2019 13:05:00)
DLL version V6.56d, compiled Dec 12 2019 13:04:51


Connecting to J-Link via USB...O.K.
Firmware: J-Trace PRO V2 Cortex compiled Jan  7 2020 16:55:37
Hardware version: V2.00
S/N: 93200XXXX
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 172.26.172.168
Emulator has RAWTRACE capability
VTref=3.311V




Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMXRT1021XXX5A
Type '?' for selection dialog
Device>
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMXRT1021XXX5A" selected.




Connecting to target via SWD
Found SW-DP with ID 0x0BD11477
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
ROMTbl[0][0]: E00FE000, CID: B105100D, PID: 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
ROMTbl[1][0]: E00FF000, CID: B105100D, PID: 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
ROMTbl[2][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[2][1]: E0001000, CID: B105E00D, PID: 000BB002 DWT
ROMTbl[2][2]: E0002000, CID: B105E00D, PID: 000BB00E FPB-M7
ROMTbl[2][3]: E0000000, CID: B105E00D, PID: 000BB001 ITM
ROMTbl[1][1]: E0041000, CID: B105900D, PID: 001BB975 ETM-M7
ROMTbl[1][2]: E0042000, CID: B105900D, PID: 004BB906 CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BB9A9 TPIU-M7
ROMTbl[0][2]: E0043000, CID: B105F00D, PID: 001BB101 TSG
Cache: Separate I- and D-cache.
I-Cache L1: 16 KB, 256 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 16 KB, 128 Sets, 32 Bytes/Line, 4-Way
Cortex-M7 identified.
J-Link>mem 0x60000000 128
60000000 = FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
60000010 = FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
<SNIP>
60000110 = FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
60000120 = FF FF FF FF FF FF FF FF 
J-Link>loadfile /XXXXX/Builds/circuitpython/ports/mimxrt10xx/build-versiboard2/firmware.hex
Downloading file [/XXXXX/Builds/circuitpython/ports/mimxrt10xx/build-versiboard2/firmware.hex]...
Comparing flash   [100%]Erasing flash     [100%] Done.
Programming flash [100%] Done.
Verifying flash   [100%] Done.
J-Link: Flash download: Bank 0 @ 0x60000000: 2 ranges affected (196608 bytes)
J-Link: Flash download: Total time needed: 4.444s (Prepare: 0.046s, Compare: 2.590s, Erase: 0.368s, Program: 0.725s, Verify: 0.711s, Restore: 0.002s)
O.K.
J-Link>mem 0x60000000 128
60000000 = 46 43 46 42 00 04 01 56 00 00 00 00 00 03 03 00 
60000010 = 01 00 00 00 01 04 00 00 40 00 00 00 00 00 00 00 
60000020 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60000030 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60000040 = 00 00 00 00 01 04 06 00 00 00 00 00 00 00 00 00 
60000050 = 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 
60000060 = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60000070 = 00 00 00 00 00 00 00 00 10 00 10 00 00 00 00 00 
60000080 = EB 04 18 0A 06 32 04 26 00 00 00 00 00 00 00 00 
60000090 = 81 04 04 24 00 00 00 00 00 00 00 00 00 00 00 00 
600000A0 = 06 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
600000B0 = 20 04 18 08 00 00 00 00 00 00 00 00 00 00 00 00 
600000C0 = 32 04 18 08 04 22 00 00 00 00 00 00 00 00 00 00 
600000D0 = C7 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
600000E0 = 02 04 18 08 04 20 00 00 00 00 00 00 00 00 00 00 
600000F0 = 03 04 18 08 04 24 00 00 00 00 00 00 00 00 00 00 
60000100 = 9F 04 04 24 00 00 00 00 00 00 00 00 00 00 00 00 
60000110 = 31 04 04 20 00 00 00 00 00 00 00 00 00 00 00 00 
60000120 = 00 00 00 00 00 00 00 00 
J-Link>

Display More

SEGGER - Erik · February 17, 2020 at 9:25 AM

Hello,

We were able to reproduce not the same issue but a similar one.
This one will be fixed in the next official version (V6.62b), scheduled to be available later today.

Could you please give this version a quick try and provide feedback?

BTW: I noticed that you do *not* perform a reset prior programming.
This is recommended in order to make sure that the device is in a proper / defined state before programming.

Best regards
Erik

dmarples · February 21, 2020 at 2:40 PM

With this new version, using GDB Server, after an initial 'load' of an elf, 'start' or 'run' for the first time will result in a target disconnect. Restarting GDB Server and gdb allows normal operation thereafter.

I cannot recreate the previously observed issue at the moment.

Regards

DAVE

SEGGER - Erik · February 24, 2020 at 9:28 AM

Thank you for the update.
We will consider this case as closed for now.

Best regards
Erik

Participate now!