Sent from my iPhone
On Dec 25, 2008, at 5:33 AM, "Kees Jongenburger" <[email protected] > wrote: > On Fri, Dec 19, 2008 at 5:46 PM, Rick Altherr <[email protected]> > wrote: >> 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. > This is only the case when you use the opensource ftd driver. the > libftd2xx > does not have this one shot only problem. > My experiments and the TI doc confirm that it has more to do with the sequence used than the interface driver. The idcode IR is unknown so once you do an irscan you can't get the idcode again. > > on my setup > http://www.flickr.com/photos/51025...@n00/2821970903/ > > I have also attached the reset so i do not have to press the reset > button > > >> 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. > Indeed I tried finding the problem area by checking out different > version of openocd and running a script > against it. I do not have access to my computer atm so I can not give > more details. > I have seen no indications of a problem with the ft2232 driver, the flyswatter layout, or either supporting library (libftdi or d2xx). All known behavior can be explained by documented or infered behavior of the icepick. > greetings _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
