On Dec 18, 2008, at 11:55 PM, Dirk Behme wrote:
ke...@ijssijs:~/projects/beagle/openocd$ make sudo openocd Open On-Chip Debugger 1.0 (2008-07-04-09:01) svn:738M$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/ openocd.c $ Info: options.c:50 configuration_output_handler(): jtag_speed: 1, 1Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x0b7ae02f (Manufacturer: 0x017, Part: 0xb7ae, Version: 0x0)I can get this far too, but it doesn't make me very excited.Rick: How do you get this? Do you like to share the details with people being a little more excited about this? I.e. me ;)
Use the attached .cfg. It has the script for turning on the DAP at least from what I've been able to glean from the various mailing lists and wiki pages. I can verify that the dap enable script _runs_, but I have been unable to verify that the DAP is actually enabled. As I said, my experiments with manually performing irscan and drscan to get the ID code have led to strange results.
omap3530.cfg
Description: Binary data
-- 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
