Kees Jongenburger 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.
Arg, this some really bad news. Seems I have to use opensource ftd driver for the moment as some libs at my Linux system are too old to link make libftd2xx :( > 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 Are you able to give some details (detailed pictures?) to get a better idea - how you configure EMU0/1 jumper at TinCanTools JTAG adaptor? - how you connect reset from TinCanTools adaptor to which pin at BeagleBoard (expansion connector)? >>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. Recent OpenOCD svn seems to work with Flyswatter. Best regards Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
