Error: Break at address "0x20c734" with no debug information available, or outside of program code.

cancel
Showing results for 
Search instead for 
Did you mean: 

Error: Break at address "0x20c734" with no debug information available, or outside of program code.

Jump to solution
589 Views
ivy_shi
Contributor II

I am using MCUXPresso IDE V11.5.1 on windows 10 computer with J-LINK Plus as a debug tool and NXP MIMX1052CVL5B as a target. I load a SDK example and try to load the example to my target board. So maybe I need modify some configurations to make the SDK project match with my board. but I am sure how to config the flash type in MCUXPresso IDE. my flash is QSPI NOR flash (IS25LP128F), and BOOT_MODE[1:0] is 0b00 (boot from fuses), BOOT_CFG2[2:0] is 0b111(QSPI device supports 3B read by default), BOOT_CFG1[7:4] is 0b0000(serial NOR boot via FlexSPI). when I start the debug session, after loading, I got the following error.

With pressing buttons Suspend and Resume I get the following error:

ivy_shi_2-1653534092927.png

 

While Console shows the message:

ivy_shi_1-1653534065510.png

 

Debugger Console shows the following:

[26-5-2022 11:00:36] Executing Server: "C:\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -nosilent -swoport 2334 -select USB=601002319 -telnetport 2335 -singlerun -endian little -noir -speed auto -port 2336 -vd -device MCIMXRT1052 -if SWD -halt -reportuseraction
SEGGER J-Link GDB Server V7.66a Command Line Version

JLinkARM.dll V7.66a (DLL compiled May 19 2022 15:18:08)

Command line: -nosilent -swoport 2334 -select USB=601002319 -telnetport 2335 -singlerun -endian little -noir -speed auto -port 2336 -vd -device MCIMXRT1052 -if SWD -halt -reportuseraction
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2336
SWO raw output listening port: 2334
Terminal I/O port: 2335
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: MCIMXRT1052
Target interface: SWD
Target interface speed: auto
Target endian: little

Connecting to J-Link...
J-Link is connected.
Device "MCIMXRT1052" selected.
Firmware: J-Link V11 compiled May 18 2022 17:08:14
Hardware: V11.00
S/N: 601002319
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.33 V
Listening on TCP/IP port 2336
Connecting to target...
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
[0][0]: E00FE000 CID B105100D PID 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
[1][0]: E00FF000 CID B105100D PID 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
[2][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[2][1]: E0001000 CID B105E00D PID 000BB002 DWT
[2][2]: E0002000 CID B105E00D PID 000BB00E FPB-M7
[2][3]: E0000000 CID B105E00D PID 000BB001 ITM
[1][1]: E0041000 CID B105900D PID 001BB975 ETM-M7
[1][2]: E0042000 CID B105900D PID 004BB906 CTI
[0][1]: E0040000 CID B105900D PID 000BB9A9 TPIU-M7
[0][2]: E0043000 CID B105F00D PID 001BB101 TSG
Cache: Separate I- and D-cache.

I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
CoreSight SoC-400 or earlier
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
[0][0]: E00FE000 CID B105100D PID 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
[1][0]: E00FF000 CID B105100D PID 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
[2][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[2][1]: E0001000 CID B105E00D PID 000BB002 DWT
[2][2]: E0002000 CID B105E00D PID 000BB00E FPB-M7
[2][3]: E0000000 CID B105E00D PID 000BB001 ITM
[1][1]: E0041000 CID B105900D PID 001BB975 ETM-M7
[1][2]: E0042000 CID B105900D PID 004BB906 CTI
[0][1]: E0040000 CID B105900D PID 000BB9A9 TPIU-M7
[0][2]: E0043000 CID B105F00D PID 001BB101 TSG
Cache: Separate I- and D-cache.

I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x0020C73E (Data = 0x68602500)
Read 2 bytes @ address 0x0020C73E (Data = 0x2500)
Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x0020C73E (Data = 0x68602500)
Read 2 bytes @ address 0x0020C73E (Data = 0x2500)
Received monitor command: reset
ResetTarget() start
Core did not halt on flash image verification. Assuming faulty flash settings.
Halting target manually.
ResetTarget() end
AfterResetTarget() start
AfterResetTarget() end
Resetting target
Downloading 8192 bytes @ address 0x60000000 - Verified OK
Downloading 10020 bytes @ address 0x60002000 - Verified OK
Downloading 4 bytes @ address 0x60004724 - Verified OK
ERROR: Timeout while preparing target, core does not stop. (PC = 0x2000017A, XPSR = 0x41000000, SP = 0x20000B18)!
Failed to initialize RAMCodeTimeout while preparing target, core does not stop. (PC = 0x2000017A, XPSR = 0x41000000, SP = 0x20000B18)!
Failed to initialize RAMCode
Writing register (PC = 0x60002304)
Read 4 bytes @ address 0x60002304 (Data = 0xFFA577FC)
Read 4 bytes @ address 0x60002304 (Data = 0xFFA577FC)
Reading all registers
Read 4 bytes @ address 0x0020C734 (Data = 0x2800B5FE)
Read 2 bytes @ address 0x0020C734 (Data = 0xB5FE)
Reading 64 bytes @ address 0x600025C0
Read 2 bytes @ address 0x600025EC (Data = 0x77FC)
Read 4 bytes @ address 0x0020D136 (Data = 0x28007F20)
Read 2 bytes @ address 0x0020D136 (Data = 0x7F20)
Read 4 bytes @ address 0x0020D136 (Data = 0x28007F20)
Read 2 bytes @ address 0x0020D136 (Data = 0x7F20)
Received monitor command: semihosting enable
Semi-hosting enabled (Handle on BKPT)
Received monitor command: exec SetRestartOnClose=1
Executed SetRestartOnClose=1
Received monitor command: reset
ResetTarget() start
Core did not halt on flash image verification. Assuming faulty flash settings.
Halting target manually.
ResetTarget() end
AfterResetTarget() start
AfterResetTarget() end
Resetting target
Setting breakpoint @ address 0x600025EC, Size = 2, BPHandle = 0x0001
Starting target CPU...

from the log, it shows “faulty flash setting”, so how to resolve this problem?

Labels (1)
0 Kudos
1 Solution
562 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
Thanks for your reply.
For MCUXpresso IDE, it uses its flash driver on the condition that the debugger is CMSIS-DAP, when the debugger is Jlink, it will use the Jlink's flash driver, even if you select the flash driver in the MCUXpresso IDE.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
To provide the fastest possible support, I'd highly recommend you to refer to the post:

View solution in original post

0 Kudos
6 Replies
571 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
For the RT1050, the default flash driver of the Segger Jlink is aimed at the HyperFlash, so I guess the issue is related to the flash driver, as your custom board uses a QSPI.
I'd like to suggest you refer to the post to deploy a suitable flash driver if using the Jlink with the MCUXpresso IDE.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
566 Views
ivy_shi
Contributor II

Hi Jeremy,

Thanks for your feedback. and I have modify the flash drive to QSPI flash, as below

ivy_shi_0-1653619866860.png

 

And I also reseted the linksever flash driver as below,

ivy_shi_1-1653617222182.png

but the issue still here. 

0 Kudos
563 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
Thanks for your reply.
For MCUXpresso IDE, it uses its flash driver on the condition that the debugger is CMSIS-DAP, when the debugger is Jlink, it will use the Jlink's flash driver, even if you select the flash driver in the MCUXpresso IDE.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
To provide the fastest possible support, I'd highly recommend you to refer to the post:

0 Kudos
408 Views
marles
Contributor I

Hi jeremyzhou,

I have exactly the same problem after trying to run an example for the TWR-KE18 board...

Could you please be more specific on how can I solve this problem?

I cannot flash any other program on the microcontroller any more, and this I find pretty aweful, since we are talking about the demo programs from NXP, programs that should be easy to run and not damage anything, right ?!...

 

Best regards,

Paul

0 Kudos
404 Views
jeremyzhou
NXP TechSupport
NXP TechSupport

Hi,
I'd like to suggest you create a new post for your question, as the RT series MCU is completely different from the KE18.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

 

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
To provide the fastest possible support, I'd highly recommend you to refer to the post:

0 Kudos
560 Views
ivy_shi
Contributor II

Hi Jeremy,

Thanks for you feedback. it works now. by the way, my boot_mode should be to internal boot.

0 Kudos