On Nov 19, 2008, at 11:28 PM, Brian Wang wrote:

I would first check the board schematic and make sure all the JTAG lines are hooked up appropriately and have correct pull-up/downs where necessary.
From there, you would need someone more familiar with the ARM7/9 JTAG
commands to figure out what it is trying to do.

Well, the pins are properly pulled high and low.  Is it possible that
the device ID is correctly read while the hardware is faulty?
The wiggler cable is good since I tested it with another board with a
different CPU.

--
brian
------------------

Cool-Karaoke - The smallest recording studio, in your palm, open- sourced
http://cool-idea.com.tw/xoops/ck-product.php

iMaGiNaTiOn iS mOrE iMpOrTaNt tHaN kNoWlEdGe



My knowledge of the JTAG protocol and physical interface is pretty minimal. In theory it would be possible to get corruption like that, but I suspect it would be difficult. Could you add "debug_level 3" to your config file and rerun it. That should provide a lot more information about what is happening.

--
Rick Altherr
[EMAIL PROTECTED]

"He said he hadn't had a byte in three days. I had a short, so I split it with him."
 -- Unsigned



Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to