P1011 Custom JTAG config

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

P1011 Custom JTAG config

跳至解决方案
3,621 次查看
juhalaukkanen
Contributor III

Hello,

I noticed that there is no template jtag chain for P101x target under Freescale\CodeWarrior PA V10.4.0\PA\PA_Support\Initialization_Files\jtag_chains

I need to create custom JTAG config since P1011 based board doesn't work with default JTAG target P1011.

It just gives "CCS last error: Draco/m HIP8: Core not responding" when doing reset or pause after connect.

The board is recognized properly with idcode.tcl script under Freescale\CodeWarrior PA V10.4.0\PA\ccs\bin

TDO -----

        |

        * Device 0  IDCODE: 068E301D  Device: FSL P1011/P1012 rev 1.x

        |

TDI -----

So my question is how do I make/generate proper JTAG config file for this target?

Thanks.

标签 (1)
标记 (5)
1 解答
3,290 次查看
addiyi
NXP Employee
NXP Employee

Most probably it is a hardware issue. You should recheck the jtag interface.

Adrian

在原帖中查看解决方案

0 项奖励
回复
6 回复数
3,290 次查看
lunminliang
NXP Employee
NXP Employee

Hi,

You may try this:

PQ38 (0x80000000 1)

Attached also.


Have a great day,
Lunmin

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

0 项奖励
回复
3,290 次查看
juhalaukkanen
Contributor III

CW 10.4 doesn't seem to recognize this target PQ38...

0 项奖励
回复
3,290 次查看
addiyi
NXP Employee
NXP Employee

jtag_chain files are used for RCW override feature and this is available only for high-end cpu (e500mc, e5500, e6500). P101x is based on low-end cpu (e500v2) and no RCW is used for cpu/board configuration.


Please provide more details about your board. It is a custom board?


Adrian

3,291 次查看
addiyi
NXP Employee
NXP Employee

Most probably it is a hardware issue. You should recheck the jtag interface.

Adrian

0 项奖励
回复
3,290 次查看
juhalaukkanen
Contributor III

Yes, this issue was that I2C boot sequence CRC failed and prevented any communication towards the CPU since it was halted.

0 项奖励
回复
3,290 次查看
juhalaukkanen
Contributor III

Thanks for clearing this out! Now I know it is not about RCW.

Yes it is custom board.

However what causes JTAG connection not to work properly? Connection works with defaults settings really well with P1020 RDB Reference Development Board

0 项奖励
回复