topic Re: Problems debuging: chip initialization failed - Em(17) error in MCUXpresso IDE

Problems debuging: chip initialization failed - Em(17) error

oscarniño — Tue, 24 Jul 2018 17:55:11 GMT

I´m working with the LPCXpresso54018 board and the LPCXpresso54608 board, I was working fine but then, it started to have troubles some times I can debug and some times I cannot. Then when I tried to debug it started to show this error:

MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink build 510)
Found chip XML file in C:/Users/Ant/Documents/MCUXpressoIDE_10.2.0_759/workspace/lpcxpresso54018_emwin_touch_and_draw/Debug\LPC54018.xml
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.183 (NXP Semiconductors)
Serial Number: KXBUA3AU
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&384c4213&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0:0 after searching for a good core
Expecting vector catch on SYSRESETREQ signal
debug interface type = Cortex-M3/4 (DAP DP ID 2BA01477) over SWD TAP 0
processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM dev (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C ChipIP dev SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 ChipIP dev DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 ChipIP dev FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 ChipIP dev ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CoreSight dev TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CoreSight dev ETM type 0x13 Trace Source - core
Inspected v.2 External Flash Device on SPI LPC540xx_SPIFI_GENERIC.cfx
Image 'LPC5460x Generic SPIFI Nov 14 2017 15:01:10'
Opening flash driver LPC540xx_SPIFI_GENERIC.cfx
using SOFT reset to run the flash driver
After error Ee(04). Wire Error -
Failed to read address register in DAP - Nn(05). Wire ACK Fault in DAP access
flash driver polled mailbox (8 bytes at 0x2000B728) read failed (on poll 1/301) - retrying after 1ms - rc Em(17). Debug port inaccessible after access at location 0x2000B728
After error Ee(04). Wire Error -
Failed to read address register in DAP - Nn(05). Wire ACK Fault in DAP access
flash driver polled mailbox (8 bytes at 0x2000B728) read failed (on poll 1/301) - halting for postmortem - rc Em(17). Debug port inaccessible after access at location 0x2000B728
Cannot halt processor
failed to halt target for postmortem - rc Ep(04). Cannot halt processor.
failed to read registers - Ep(08). Cannot access core regs when target running.
Flash Driver V.2 startup failed - rc Em(17). Debug port inaccessible after access at location 0x2000B728
chip initialization failed - Em(17). Debug port inaccessible after access at location 0x2000B728
NXP: LPC54018
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
Cannot halt processor
Could not stop execution from running: Ep(04). Cannot halt processor.

I got stock in this and this is urgent to my work could anybody help me?

I´m working with MCUXpresso IDE, I´m using LPCXpresso54018 and LPCXpresso54608 boards, I´m using LPC-Link 2 board like a second option and USB port of the board like my first one.

Re: Problems debuging: chip initialization failed - Em(17) error

converse — Tue, 24 Jul 2018 21:25:14 GMT

Try this

https://community.nxp.com/thread/389112

Re: Problems debuging: chip initialization failed - Em(17) error

oscarniño — Wed, 25 Jul 2018 17:34:33 GMT

I have done, it is not pretty clear to me, but infact I saw that maybe it could works because MCUXpresso let me debug after I have try to run a software in LPCXpresso, I have changed the reset option indicates in https://community.nxp.com/thread/389040 question. but It still doesn´t work fine. I have to debug first an aplication on LPCXpresso and then try to debug in MCUXpresso in order to debug my application. Any other idea?

thanks

Re: Problems debuging: chip initialization failed - Em(17) error

lpcxpresso_supp — Mon, 30 Jul 2018 09:49:57 GMT

Oscar,

Please can you break your issue down so we can help here.

From the debug log shown in your first post, the QSPI flash driver fails to initialise when started with a Soft reset.

Please can you create a new project (a simple hello world should be fine) that demonstrates the issue on your target boards. Please confirm whether this only occurs when writing to QSPI flash (on both boards) ?

Note: these board have a number of ISP buttons. I would recommend using the on board ISP0 button to ensure board recovery i.e. hold down this button and click the board reset button.. If this is used, I would also recommend unselecting the 'Pull ISP reset' feature found at 'Windows -> Properties -> MCUXpresso IDE -> LinkServer Options'

Yours,

MCUXpresso IDE Support

Re: Problems debuging: chip initialization failed - Em(17) error

oscarniño — Mon, 30 Jul 2018 22:19:31 GMT

Hello

I still trying with this problem, I can´t resolve it, when I try to debug it this report is showed.

MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink build 510)
Found chip XML file in C:/Users/Ant/Documents/MCUXpressoIDE_10.2.0_759/workspace/lpcxpresso54018_hello_world/Debug\LPC54018.xml
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.182 (NXP Semiconductors)
Serial Number: NRA2CQFR
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&654b1f4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0:0 after searching for a good core
Expecting vector catch on SYSRESETREQ signal
debug interface type = Cortex-M3/4 (DAP DP ID 2BA01477) over SWD TAP 0
processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM dev (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C ChipIP dev SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 ChipIP dev DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 ChipIP dev FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 ChipIP dev ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CoreSight dev TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CoreSight dev ETM type 0x13 Trace Source - core
Inspected v.2 External Flash Device on SPI LPC540xx_SPIFI_GENERIC.cfx
Image 'LPC5460x Generic SPIFI Nov 14 2017 15:01:10'
Opening flash driver LPC540xx_SPIFI_GENERIC.cfx
using SOFT reset to run the flash driver
AFTER driver startup timeout
Driver Addresses
Start: 20000000
Entry: 20000035
End: 20002718
Stack: 20003718
Mailbox:2000B718
Driver Register State
R0: 200036E0
R1: 200000F6
R2: 0000FFFF
R3: 0000BEAB
R4: 2000B718
R5: 00000000
R6: 00000000
R7: 00000000
R8: 00000000
R9: 00000000
R10: 00000000
R11: 00000000
R12: 00000000
SP: 200036E0
LR: FFFFFFF9 (exception from main thread)
PC: 000093DA
xPSR: 21000003
MSP: 200036E0
PSP: 20003718
CFBP: 00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Stacked Exception information
200036FC: xPSR: 21000000
200036F8: VECTPC: 200000F6
200036F4: LR: 200019CB
200036F0: R12: 00000000
200036EC: R3: 00002000
200036E8: R2: 00000002
200036E4: R1: 40000000
200036E0: R0: 00000000
Exception registers
E000ED04: ICSR: 00400803 (ISRPEND, VECTPEND=0(none), RETTOBASE, VECTACTIVE=3(hard fault))
E000ED08: VTOR: 00000000 TBLBASE=0(INCODE), TBLOFF=0x0
E000ED28: MMFSR: 00
E000ED29: BFSR: 00
E000ED2A: UFSR: 0001 (UNDEFINSTR)
E000ED2C: HFSR: 40000000 (FORCED)
E000ED30: DFSR: 00000001 (HALTED)
E000ED3C: AFSR: 00000000
E000ED24: SHCSR: 00000000
E000ED34: MMAR: E000EDF8
E000ED38: BFAR: E000EDF8
E000EDFC: DEMCR: 01000001 (TRCENA, VC_CORERESET)
VECTPC instructions near 200000F6
200000F0: 5300
200000F2: F8C1
200000F4: FFFF
200000F6: FFFF
200000F8: F240
200000FA: 3206
Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
chip initialization failed - Ef(34): Timed-out initializing flash.
NXP: LPC54018
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3337 ...
GDB nonstop mode enabled
Starting execution using soft reset with PC 0x0 SP 0x0 from load at 0x10000000
Cannot halt processor
Could not stop execution from running: Ep(04). Cannot halt processor.

about unselecting Pull ISP reset I have done but it still si happened, This report is done with a simple Hello World example.

Thanks for reply