T2081 customer board bring up issue: core not in debug

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

T2081 customer board bring up issue: core not in debug

786 Views
ken_liu
Contributor II

Hi NXP expert

we have design a customer board based on T2081 processer, we are bring up it under hard-coded mode

the Target Initialization file could executed normally, but the core could not be suspend and error report : core not in debug

Tools:

a) CodeWarrior TAP JTAG : USB

b) CodeWarrior Version: 10.5.1

c) Target Initialization file: T2080RDB-PCIe_init_sram.tcl ( the DDR controller should not enable on hard-coded mode which is note on T2080/T2081 reference manual, and some design are based on T2080RDB, so we used the T2080RDB-SRAM)

Issue found:

1) after executing the target initialization file, we click "suspend" button, a error shown that Fail to stop process [CCS last error: Core not responding]

ken_liu_1-1710643040472.jpeg

a few second later, the CodeWarrior seems show the core is suspend, but we could not see some register value such as IFC, the error shown : Core not in debug

ken_liu_2-1710643194661.png

we open CCS log, the error also shown: CCS last error: core not in debug

2. Although the Target Initialization file is executed normally, actually it is not worked.

   I could see the core register via CodeWarrior, but the register value is not initialized as target initialization script

so please help me to review the issue, another question is how to take core in debug mode?

we have check the "execute reset sequence" in debug configuration tools

ken_liu_4-1710643795631.png

 

 

 

 

 

Tags (1)
0 Kudos
Reply
1 Reply

749 Views
yipingwang
NXP TechSupport
NXP TechSupport

1. Please refer to section "4.6.4.1.1 Hard Coded RCW Options" to configure your target as hard-coded RCW in T2080RM.pdf.

2. When you create a bare board project, please select "Connect SRAM" launch configuration to avoid download the RAM version program to the target board.

0 Kudos
Reply