Facing problems with JTAG for MC13224 based development boards

[AmitPatil]

Hi,

We are using MC13224 based development kit and J-Link for ARM JTAG of IAR for flashing code on these boards.  We were using the development borad for a while before we have observed that while flashing code on board using JTAG something caused Flashing process to be aborted and we got error  "Can not find supported CPU core on JTAG chain" and Debug log was as following -

Wed Jul 29 18:11:38 2009: Firmware: J-Link ARM V6 compiled Jul 30 2008 11:24:59
Wed Jul 29 18:11:38 2009: JTAG speed is fixed to: 2000 kHz
Wed Jul 29 18:11:38 2009: Initial reset was performed
Wed Jul 29 18:11:38 2009: TotalIRLen = ?, IRPrint = 0x..00000000000000000000000000000000
Wed Jul 29 18:11:38 2009: TotalIRLen = ?, IRPrint = 0x..00000000000000000000000000000000
Wed Jul 29 18:12:16 2009: Fatal error: Could not find supported CPU core on JTAG chain
 

After this it never allowed to flash using JTAG again for that board. We checked the pins of JTAG connector on board and found that one of the pins got shorted to GND [please note that device is working and we can flash it through USB]. This has happened with 2 devices out of the three.The third one is working fine as of now.

So we are worried if this is a chip problem (which is very bad) or something else.  Please let us know if anyone had any similar problems, and if we are missing something here.

errorbox.JPG

Message Edited by t.dowe on 2009-09-04 12:35 PM

[misty]

You mean that after erase FLASH contents then J-Link can connect MC13224？I have the same problem with you.

[jmgelectronika]

i have this problem and i use the schematic for remove mode but my j-link don´t found core.

thanks 

[phlp]

Johnno I solved the problem. The custom connector I made was problematic. If you are interested in using the Freescale solution I can recommend the ZFSM-201-1 from CEL. It is a small module based upon the Freescale solution and they also sell nice dev kits.

[pierpd]

I solved the problem by using the recovery procedure described in the MC1322RM in section 3.11.5.

However I'm still looking for alternate solutions...

Pier 

[phlp]

Anyone found the solution to the problem?

Thanks

Philip

[Johnno]

Considering switching to Freescale zigbee from TI, this is a concern for me though!

[DenisShimizu]

I solved my problem using the recovery mode of the device  - see section 3.11.5 of the reference manual (MC1322XRM)

[misty]

hi, i face this problem now. but i do not know recovery mode which you said, how to resolve this problem using recovery mode?

[phlp]

Misty the process is described in section 3.11.5 of MC1322x Reference Manual, Rev. 1.2 (see attchment).

[saurabh]

We have tried that and that doesn't work.

[DenisShimizu]

Exactly the same problem.Anyone have any idea of how to fix it?

[saurabh]

I have also been facing the same problem. Could anyone help please.