T4240 Custom Board/CWPA 10.3.3: Could not connect to the requested core

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

T4240 Custom Board/CWPA 10.3.3: Could not connect to the requested core

788件の閲覧回数
dannygale
Contributor II

We are trying to bring up a custom board with a T4240 on it. We're using the CodeWarrior USB TAP and a vanilla CodeWarrior project on CodeWarrior PA 10.3.3.

 

We are having issues connecting the debugger to the custom board. We also have a T4240QDS, and can connect the debugger with the same debug configuration to that with no problems.

 

At the moment, we are receiving the error, "Could not connect to the requested core: core 0". We have already verified that the USB TAP can see the T4240, using "source IDcode.tcl" in the ccs console.

 

What can cause this problem and what are potential solutions?

ラベル(1)
タグ(3)
0 件の賞賛
返信
3 返答(返信)

507件の閲覧回数
catalindemergia
Contributor IV

Hello,

Can you check the JTAG speed setting in CodeWarrior ?

(<your_debug_configuration>/Target Settings/Connection/Edit/JTAG Clock Speed)

Maybe the default value is too big, try using 2000 or less.

And check your hardware JTAG as well, but if you say that IDcode.tcl detects the core,

this means something is working, the script performs JTAG scanning to detect the device.

regards,

Catalin

0 件の賞賛
返信

507件の閲覧回数
dannygale
Contributor II

The JTAG speed is set to 1000 kHz.

This seems to have been a problem with the debugger configuration. Starting fresh with a new configuration has allowed us to connect the debugger.

0 件の賞賛
返信

507件の閲覧回数
lunminliang
NXP Employee
NXP Employee

That's common problem in initial stage of new board.

0 件の賞賛
返信