Hi, On Sat, May 2, 2009 at 6:52 PM, Strontium <strnty...@gmail.com> wrote: > Hi, > > I've been playing with the Flyswatter, OpenOCD and my Beagle Board. > > And I would like to see the serial output from the beagle, routhed > through the B port of the flyswatter, but for some reason, it seems > OpenOCD via libftdi (v0.13) is blocking up the whole FT22232 Device, > regardless that only port A is selected. Indeed I have seen the behavior. If you do reconnect to the serial it works again. I suspect it is something related to the usage of libusb as the serial driver is provided by the kernel driver. I can't remember if urjtag has the same behavior.
> If I have a terminal connected to port B, it stops working as soon as I > start OpenOCD. > > One possibility would be allow the data to be routed to the telnet > session. A "target" command, which could work like this. Read above , this is not necessary and openocd has nothing to do with the serial. Greetings _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
