MCUXpresso IDE v10.3.0 [Build 2200] Problem [BUG?]

cancel
Showing results for 
Search instead for 
Did you mean: 

MCUXpresso IDE v10.3.0 [Build 2200] Problem [BUG?]

Jump to solution
1,508 Views
davaa-u
Contributor II

I just installed new version of MCUXpresso and can not debug.

MCUXpresso IDE v10.3.0 [Build 2200] [2018-12-03] (MacOSX 10.14.1)

Here is the console log:

MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:37:51 - crt_emu_cm_redlink build 748)
Found part description in XML file LPC82x.xme
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number:  I3FSJUKQ
VID:PID:  1FC9:0090
USB Path: USB_1fc9_0090_14100000_ff00
Using memory from core 0 after searching for a good core
On debug connection reset using system reset
debug interface type      = Cortex-M0+ (DAP DP ID 0BC11477) over SWD TAP 0
processor type            = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
number of h/w breakpoints = 4
number of flash patches   = 0
number of h/w watchpoints = 2
Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
Content of CoreSight Debug ROM(s):
RBASE F0000000: CID B105100D PID 0500081000 ROM (type 0x1)
ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
NXP: LPC824
DAP stride is 1024 bytes (256 words)
Inspected v.2 On-chip Flash Memory LPC800_32.cfx
Image 'LPC800 (32K) Oct 25 2018 11:57:50'
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
Opening flash driver LPC800_32.cfx
SYSRESETREQ reset omitted - already reset
XPSR register failed - rc Ep(08). Cannot access core regs when target running.
Target error from Commit Flash write: Ep(08). Cannot access core regs when target running.
GDB stub (crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
Labels (1)
1 Solution
990 Views
lpcxpresso_supp
NXP Employee
NXP Employee

No problems being seen using LPC824 via LPC-Link2 with MCUXpresso IDE v10.3.0.

I would suggest that you try the following:

  1. Click on "Clean up debug" button in IDE.
  2. Power your board and debug probe down and back up again
  3. Delete your launch configuration
  4. Try debugging again
  5. If debug still doesn't work, try doing an ISP reset as well as the above :

If you are still having problems, please provide some details of the actual board being used. And also confirm whether you have been able to use this board with previous IDE versions.

Regards,

MCUXpresso IDE Support

View solution in original post

3 Replies
990 Views
rex_lam
Contributor IV

I have also experienced a similar problem with MCUXpresso IDE v10.3.0 build 2200 while using the GUI Flash Tool. After a successful flash, the next attempt gives the error "XPSR register failed - rc Ep(08). Cannot access core regs when target running. Here is the console output.

Executing flash operation 'Program' (Program file into flash: test.bin) - Tue Feb 19 13:47:48 PST 2019
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:33:57 - crt_emu_cm_redlink.exe build 748)
(  0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in D:/ARM/projects/test/Debug\LPC54608J512.xml
(  5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.173 (NXP Semiconductors)
Serial Number:  FTATBQBR
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#11&28d209ff&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
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: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CSt ETM type 0x13 Trace Source - Core
NXP: LPC54608J512
DAP stride is 4096 bytes (1024 words)
Inspected v.2 On-chip Flash Memory LPC5460x_512K.cfx
Image 'LPC5460x (512K Flash) Aug 23 2017 12:13:28'
Inspected v.2 External Flash Device on SPI LPC5460x_SPIFI_GENERIC.cfx
Image 'LPC5460x Generic SPIFI Sep 25 2017 16:15:07'
Opening flash driver LPC5460x_SPIFI_GENERIC.cfx
Sending VECTRESET to run flash driver
Flash variant 'MT25QL128AB' detected (16MB = 256*64K at 0x10000000)
Closing flash driver LPC5460x_SPIFI_GENERIC.cfx
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=false
( 70) License Check Complete
Loading 'test.bin' Binary 0x00000000 len 0x10000
Opening flash driver LPC5460x_512K.cfx
Sending VECTRESET to run flash driver
XPSR register failed - rc Ep(08). Cannot access core regs when target running.
(100) Writing Flash ended with an error.
File 'test.bin' load failure: Ep(08). Cannot access core regs when target running.
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

The problem is fixed by pressing the 'Clean Up Debug' button or cycling power to the LPCXpresso54608 development board. I think this problem only started occurring recently. It used to take many flashes before this error shows up. Now, it occurs every other time.

0 Kudos
991 Views
lpcxpresso_supp
NXP Employee
NXP Employee

No problems being seen using LPC824 via LPC-Link2 with MCUXpresso IDE v10.3.0.

I would suggest that you try the following:

  1. Click on "Clean up debug" button in IDE.
  2. Power your board and debug probe down and back up again
  3. Delete your launch configuration
  4. Try debugging again
  5. If debug still doesn't work, try doing an ISP reset as well as the above :

If you are still having problems, please provide some details of the actual board being used. And also confirm whether you have been able to use this board with previous IDE versions.

Regards,

MCUXpresso IDE Support

View solution in original post

990 Views
davaa-u
Contributor II

Thank you for support. It worked now.

It might was problem something from previous version caused problem.

Now it worked.

0 Kudos