Issues with Flash (Binary with Flash Offset) Configuration and Debugging on LPCXpresso55S28 Board

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Issues with Flash (Binary with Flash Offset) Configuration and Debugging on LPCXpresso55S28 Board

103 次查看
SegFault0
Contributor II

Hi everyone,

I’m currently working with the LPCXpresso55S28 board and have encountered an issue that I hope someone can help me with. I’ve developed a simple test application that makes an LED blink. When I build the binary normally and flash it using LinkServer, everything works perfectly, and I can debug without any issues.

However, when I adjust the project settings under MCU Settings and define the flash areas as shown in the attached image, the application can still be flashed without errors, but the LED no longer blinks. Furthermore, I am unable to debug the application after making these changes.

Bildschirmfoto vom 2024-07-24 11-38-09.png

Here are the details of my setup:

  • Board: LPCXpresso55S28
  • IDE: MCUXpresso IDE v11.9.1 [Build 2170] [2024-04-19]

I have also attached output of the console, when trying to debug.

破坏者

MCUXpresso IDE RedlinkMulti Driver v11.9 (Apr 5 2024 19:50:07 - crt_emu_cm_redlink build 47)

Found chip XML file in /home/Dokumente/nxp_workspace/LPC55S28_Project_test_hex/Debug/LPC55S28.xml

Reconnected to existing LinkServer process.

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)

Serial Number: ERAXCQCR

VID:PID: 1FC9:0090

USB Path: /dev/hidraw1

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-M33 (CPU ID 00000D21) 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: 00000D21. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)

ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)

ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined

ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined

ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined

ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus

ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU

NXP: LPC55S28

DAP stride is 1024 bytes (256 words)

Inspected v.2 On chip Flash memory using IAP lib LPC55xx.cfx

Image 'LPC55xx Apr 5 2024 18:17:43'

Opening flash driver LPC55xx.cfx

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'LPC55xx (512KB)' detected (512KB = 1024*512 at 0x0)

Closing flash driver LPC55xx.cfx

Inspected v.2 On chip Flash memory using IAP lib LPC55xx.cfx

Image 'LPC55xx Apr 5 2024 18:17:43'

Opening flash driver LPC55xx.cfx

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'LPC55xx (512KB)' detected (512KB = 1024*512 at 0x0)

Closing flash driver LPC55xx.cfx

Connected: was_reset=true. was_stopped=false

Awaiting telnet connection to port 3332 ...

GDB nonstop mode enabled

Opening flash driver LPC55xx.cfx

VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.

Using SOFT reset to run the flash driver

Flash variant 'LPC55xx (512KB)' detected (512KB = 1024*512 at 0x0)

Writing 14372 bytes to address 0x00040000 in Flash

00043000 done 85% (12288 out of 14372)

00043A00 done 100% (14848 out of 14372)

Sectors written: 29, unchanged: 0, total: 29

Erased/Wrote sector 512-540 with 14372 bytes in 218msec

Closing flash driver LPC55xx.cfx

Flash Write Done

Flash Program Summary: 14372 bytes in 0.22 seconds (64.38 KB/sec)

Starting execution using system reset and halt target with a stall address

Retask read watchpoint 1 at 0x50000040 to use for boot ROM stall

state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

Warning - processor did not halt - gave up waiting

flash - system reset failed - Ep(04). Cannot halt processor.

Target error from Commit Flash write: Ep(04). Cannot halt processor.

GDB stub (/usr/local/LinkServer_1.5.30/binaries/crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.

state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

 

Any advice on what might be causing this issue or how to resolve it would be greatly appreciated. Thank you in advance for your help!

标签 (1)
0 项奖励
回复
0 回复数