Failed on chip setup: Ep(04). Cannot halt processor.

cancel
Showing results for 
Search instead for 
Did you mean: 

Failed on chip setup: Ep(04). Cannot halt processor.

Jump to solution
381 Views
Contributor III

I am using LPC-link 2 2ith NHS3152TEMOADK: NHS3152 General Starter Kit, with LPCXpresso IDE. 

When debugging blinky example, or any other example, i get: 


LPCXpresso RedlinkMulti Driver v8.2 (Sep 5 2016 10:12:38 - crt_emu_cm_redlink build 725)
Found chip XML file in C:/Users/leo/Documents/LPCXpresso_8.2.2_650/workspace/app_example_blinky/Debug/Generic-M0plus.xml
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.173 (NXP Semiconductors)
Serial Number: I3FUNVCT
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&2bf3e870&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Cannot halt processor
Cannot halt processor
Emu(0): Connected&Reset. DpID: 0BC11477. CpuID: 410CC600. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Cannot halt processor
Failed on chip setup: Ep(04). Cannot halt processor.

How do I solve this? how do i reset it so that it works again ? 

Tags (1)
0 Kudos
1 Solution
263 Views
NXP Employee
NXP Employee

Hi,

 

The example application app_example_dp_ndeft2t doesn't use Power-off or Deep Power Down modes, so once it is running, the debug interface should be readily available too.

With a battery inserted, without an NFC field, measuring 90mv between VDD and P11 indicates a problem with your battery connection..

  • Battery is empty
  • Battery is inversely inserted
  • Diode D2 is missing
  • ...

With a plenished battery inserted, you should be able to measure ~3.4V between VDD and GND contact points.

Without a battery, when an NFC field is present, the whole IC will be powered by the NFC field, giving ~1.8V, as you also have measured. 

 

It is good to read it's working now. I would definitely check on your battery, and play with the blinky demo app_demo_dp_blinky to learn the easiest - least painful - way to reliably connect and debug using this board.

Good luck!
Best,
Dries.

 

View solution in original post

0 Kudos
7 Replies
286 Views
Contributor III

Hi Dries, 

The chip is running again now, i have attached answeres to the questions anyhow cause maybe you can point me to the issue. 

  • Do you know which program is currently flashed inside the NHS3152 IC?

Since it is working again and nhs31xx/example.ndef is on it without reflashing it. I gather this was always on it. 

  • Did you fit a jumper over JP2 on the LPC-Link2 board? This provides power to the board through the SWD lines.

The LPC-Link2 board already came with a jumper over JP2. I haven't removed them.

  • Can you check with a scope that communication is happening over the SWD lines?

The following are Scope results: 

NO NFC field: VDD and P11 have 90mv

WITH NFC: P7, P0,P9 1.8 V

NO NFC; LPC-link powered via USB:  VDD 3.3V, P10 3.3, P11 3V

NFC and LPC-link powered via USB: i must have reset it whilst doing this, because all of a sudden it started to take me to nxp.com/etc.. 

after this it starting to run nhs31xx/example.ndef

  • Do you have battery inserted in the coin cell holder of the demo board? Can you check the battery voltage?

I do, it's working.

 

What is the reset procedure i accidentaly found that i could reuse in the future? 

 

Best, 

Leo

0 Kudos
264 Views
NXP Employee
NXP Employee

Hi,

 

The example application app_example_dp_ndeft2t doesn't use Power-off or Deep Power Down modes, so once it is running, the debug interface should be readily available too.

With a battery inserted, without an NFC field, measuring 90mv between VDD and P11 indicates a problem with your battery connection..

  • Battery is empty
  • Battery is inversely inserted
  • Diode D2 is missing
  • ...

With a plenished battery inserted, you should be able to measure ~3.4V between VDD and GND contact points.

Without a battery, when an NFC field is present, the whole IC will be powered by the NFC field, giving ~1.8V, as you also have measured. 

 

It is good to read it's working now. I would definitely check on your battery, and play with the blinky demo app_demo_dp_blinky to learn the easiest - least painful - way to reliably connect and debug using this board.

Good luck!
Best,
Dries.

 

View solution in original post

0 Kudos
290 Views
NXP Employee
NXP Employee

Hello Leo,

Your problem does not look obvious, let me probe a bit:

  • Do you know which program is currently flashed inside the NHS3152 IC?
  • Did you fit a jumper over JP2 on the LPC-Link2 board? This provides power to the board through the SWD lines.
  • Can you check with a scope that communication is happening over the SWD lines?
  • Do you have battery inserted in the coin cell holder of the demo board? Can you check the battery voltage?
  • You can force the image currently running in the IC to remain awake (not shutting down, not going to deep power down) or to immediately become active again by bringing the IC in an NFC field, e.g. an unlocked Android phone. Be sure to know the optimal location on the back of your phone. Can you try to connect a few times with this setup?

Kind regards,
Dries.

290 Views
Contributor III

not sure if this is useful, but after i run the flash i get this from RedlinkServer

[Started server]
[Connected on port 3025]
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.173
Serial Number = I3FUNVCT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&2bf3e870&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.173
Serial Number = I3FUNVCT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&2bf3e870&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.173
Serial Number = I3FUNVCT
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&2bf3e870&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink>quit
[Closed]

0 Kudos
290 Views
NXP TechSupport
NXP TechSupport

Hi, Leo,

It appears that the LPC-Link2 and MCUXpresso debugger work fine, right?

BR

XiangJun Rong

0 Kudos
290 Views
Contributor III

Hi Xiangjun,

What do you mean ? 
the LPC-link2 led comes on and flashes, But i cannot upload code without getting the  Cannot halt processor message. 

Is the issue with the code i am uploading ? Because i have tried to upload several different examples. 

Best, 

Leo

0 Kudos
290 Views
Contributor III

I tried using the ISP reset over debug, and got: 

Ni: LPCXpresso RedlinkMulti Driver v8.2 (Sep 5 2016 10:12:38 - crt_emu_cm_redlink.exe build 725)
Pc: ( 0) Reading remote configuration
Nc: Found chip XML file in C:/Users/leo/Documents/LPCXpresso_8.2.2_650/workspace/app_example_dp_i2c/Debug_SLAVE/Generic-M0plus.xml
Pc: ( 5) Remote configuration complete
Wc: ============= SCRIPT: ISPResetConnect.scp =============
Wc: Reset to ISP
Wc: ============= END SCRIPT ==============================
Xe:
Nc: Probe Firmware: LPC-LINK2 CMSIS-DAP V5.173 (NXP Semiconductors)
Nc: Serial Number: I3FUNVCT
Nc: VID:PID: 1FC9:0090
Nc: USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&2bf3e870&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Pc: ( 30) Emulator Connected
Xw:
Wc: Cannot halt processor
Wc: Cannot halt processor
Pc: ( 40) No Halt
Pc: ( 50) CPU ID
Nc: Emu(0): Connected&Reset. DpID: 0BC11477. CpuID: 410CC600. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Wc: Cannot halt processor
Ed:03: Failed on chip setup: Ep(04). Cannot halt processor.
Pc: ( 65) Chip Setup Complete

0 Kudos