Could not read registers; remote failure reply 'E22'

pupu_ji — Thu, 25 Apr 2024 08:58:19 GMT

Hi ,all :

Use CMSIS-DAP download my project on demo board rt1170 getting error as follow:

"Could not read registers; remote failure reply ‘E22’ ”.

But the demo SDK have will be no errors.

What are the possible reasons?

Please advise me how to solve this problem.

Re: Could not read registers; remote failure reply 'E22'

Pavel_Hernandez — Thu, 25 Apr 2024 20:50:57 GMT

Hello, my name is Pavel, and I will be supporting your case, could elaborate further about this issue? and could you add the image of the popup message or the LOG? Are you using the IDE?

Best regards,
Pavel

Re: Could not read registers; remote failure reply 'E22'

pupu_ji — Fri, 26 Apr 2024 02:04:49 GMT

hi Pavel,

Thanks for your help !

SDK version is 2.15

Log as follow :

MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:02:10 - crt_emu_cm_redlink build 2)
Found chip XML file in C:/Users/13662/Documents/MCUXpressoIDE_11.9.0_2144/workspace/MIMXRT1176_Project/Debug\MIMXRT1176xxxxx.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1170_connect_M7_wake_M4.scp =============
RT1170 Connect M7 and Wake M4 Script
DpID = 6BA02477
APID = 0x84770001
Setting M4 spin code
Setting M4 clock
Resetting M4 core
View cores on the DAP AP
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
============= END SCRIPT ========================================
Probe Firmware: CMSIS-DAP (ARM)
Serial Number: 024400002faba2a000000000000000000000000097969905
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#8&1c056edf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = CoreSight DP (DAP DP ID 6BA02477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0043000: CID B105900D PID 04001BB908 CSt CSTF type 0x12 Trace Link - Trace funnel/router
NXP: MIMXRT1176xxxxx
DAP stride is 1024 bytes (256 words)
Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1170_SFDP_QSPI.cfx
Image 'iMXRT1170_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:24'
Opening flash driver MIMXRT1170_SFDP_QSPI.cfx
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:24' detected (16MB = 256*64K at 0x30000000)
Closing flash driver MIMXRT1170_SFDP_QSPI.cfx
Connected: was_reset=false. was_stopped=false
Awaiting telnet connection to port 3333 ...
GDB nonstop mode enabled
FreeRTOS stack backtrace is disabled
Opening flash driver MIMXRT1170_SFDP_QSPI.cfx (already resident)
Sending VECTRESET to run flash driver
Flash variant 'iMXRT1170_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:24' detected (16MB = 256*64K at 0x30000000)
Writing 708952 bytes to address 0x30002000 in Flash
30004000 done 2% (16384 out of 717144)
30008000 done 4% (32768 out of 717144)
3000C000 done 6% (49152 out of 717144)
30010000 done 9% (65536 out of 717144)
(100) at 30010000: 655360 bytes - 720896/717144
Sectors written: 1, unchanged: 10, total: 11
Erased/Wrote sector 0-10 with 708952 bytes in 3372msec
Closing flash driver MIMXRT1170_SFDP_QSPI.cfx
Flash Write Done
Flash Program Summary: 708952 bytes in 3.37 seconds (205.32 KB/sec)
============= SCRIPT: RT1170_reset.scp =============
SYSTEM Reset
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 AP 1: APID: 24770011 ROM Table: E00FF003
TAP 0: 6BA02477 AP 2: APID: 54770002 ROM Table: 00000002
APID = 0x84770001
Setting M4 spin code
Setting M4 clock
Resetting M4 core
Releasing M4
View cores on the DAP AP
DpID = 6BA02477
TAP 0: 6BA02477 Core 0: M7 APID: 84770001 ROM Table: E00FD003*
TAP 0: 6BA02477 Core 1: M4 APID: 24770011 ROM Table: E00FF003
R15 = 0x00223104
Vector table SP/PC is the reset context.
PC = 0x30077AFD
SP = 0x20340000
XPSR = 0x01000000
VTOR = 0x30002000
Set DEMCR = 0x010007F1
============= END SCRIPT ===========================
16: Target error from status-poll: Nn(05). Wire ACK Fault in DAP access
Unknown/broken state: Nn(05). Wire ACK Fault in DAP access: <cannot read registers>Unknown
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access
Target error from Register access: Nn(05). Wire ACK Fault in DAP access

And debug configuration use default.

Is it possible that there is a problem with the project configuration?

Re: Could not read registers; remote failure reply 'E22'

Pavel_Hernandez — Fri, 26 Apr 2024 22:02:23 GMT

Hello, thanks for the really helpful information, I reviewed the information maybe the MCU is in an unknown state, the error "ACK wire" sometimes means, the MCU is not halted by the Debugger.

RT board recovery for debugger connect issues - NXP Community

Maybe this thread could help you.

Best regards,
Pavel

topic Re: Could not read registers; remote failure reply 'E22' in MCX Microcontrollers

Could not read registers; remote failure reply 'E22'

Re: Could not read registers; remote failure reply 'E22'

Re: Could not read registers; remote failure reply 'E22'

Re: Could not read registers; remote failure reply 'E22'