P1011 Custom JTAG config

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

P1011 Custom JTAG config

ソリューションへジャンプ
3,553件の閲覧回数
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,222件の閲覧回数
addiyi
NXP Employee
NXP Employee

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

Adrian

元の投稿で解決策を見る

0 件の賞賛
返信
6 返答(返信)
3,222件の閲覧回数
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,222件の閲覧回数
juhalaukkanen
Contributor III

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

0 件の賞賛
返信
3,222件の閲覧回数
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,223件の閲覧回数
addiyi
NXP Employee
NXP Employee

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

Adrian

0 件の賞賛
返信
3,222件の閲覧回数
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,222件の閲覧回数
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 件の賞賛
返信