On Dec 19, 2008, at 4:25 AM, Dirk Behme wrote:
Rick Altherr wrote: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.Thanks! Unfortunately, I still getError: JTAG communication failure, check connection, JTAG interface, target power etc.Error: trying to validate configured JTAG chain anyway...Error: Error validating JTAG scan chain, IR mismatch, scan returned 0xffError: Could not validate JTAG chain, continuing anyway... See log in attachment.Maybe there is really an issue with Flyswatter, or I'm doing anything else totally wrong :(Best regards Dirk
Hit the reset button on the BeagleBoard and then start openocd. As my other experiments show, you only get one shot at getting the ID code. You also get some odd results for the first scan regardless of type. I _really_ doubt this has anything to do with the Flyswatter as the code for the ft2232 interface has not changed in any meaningful way since at least r1080 or so. As I said, I will validate the Flyswatter against a LM3S6965 to rule out that possibility. I'm wondering if we are a) hitting a JTAG clock speed issue, b) not quite following the JRC's necessary procedure, or c) hitting some odd case in our JTAG state machine.
-- 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
