Help with OpenOCD-JTAGKey-LPC3250

Development Boards MicroMod
1

Hi all

I’ve got custome build LPC3250 uC board and using Amontec JTAGKey, and I’m having trouble getting the correct JTAG ID back. I’m using the followings:

  1. OpenOCD version 0.4.0, source code download and compiled, under Cygwin, using FTD32xx.lib. (btw. compile stage was a bit troublesome but finally made it).

  2. Amontec JTAGKey and using config files, under OpenOCD for LPC3250.

  3. While I try to validate the JTAG ID of the board, I’m getting very different ID code 0x88d2402b as oppose to expected 0x17900f0f.

  4. I’ve check the JTAG TCK/TMS/TDI/TDO/TRST/SRTST signals on oscillscopes and they seems ok. And prove that at least JTAG TAP inside LPC3250 is working by reading the ID while the device is off and get nothing back.

  5. I’ve tried two differnt JTAG Key to rule out the dongle issue.

  6. I’ve tried three different boards, which all reports the same wrong JTAG ID (its kind of rule out the board, not entirely, but for all propability).

It suggest, there is something I’m not doing write with config scripts, OpenOCD compilation, and god forbid OpenOCD bug specific to LPC3250.

Any thoughts, help, and prove that LPC3250 is working with someone else with be much appreciated.

Thanks.

2

Update on this issue, I’ve track down the issue back to “Boundary Scan” and “JTAG” selection for LPC3250, its the board issue, once that is fixed, I can now validate the JTAG TAP ids for both debugger and embedded ICE.

However, the hardware tap 0x17926F0F (which is standard ARM926EJ-s), not 0x17900F0F as NXP datasheet said. May be they fixed it new silicon rev.

3

“the hardware tap 0x17926F0F (which is standard ARM926EJ-s), not 0x17900F0F as NXP datasheet said”

Did you communicate this to openocd mailing list ?

Regards,

Laurent

http://www.amontec.com

http://www.amontec.com/jtagkey.shtml