This is on Linux, Over recent days I have become suspicious of the Flyswatter hardware itself. It is like my flyswatter is underpowered, as the FT2232 on port B keeps disconnecting and re-connecting to the PC, I tried connecting it through a powered hub and it makes no difference.
Also, if I just plug in the flyswatter and leave my target un-powered led 1 blinks green, and goes dark. lsusb shows no flyswatter. If I then earth the usb terminal of my target (a beagle board) using the usb cable I use to power it. (all I have to do is touch the outer shell of the cable connector to the shell of the beagles usb connector) Led 1 comes on, but it isnt stable, It keeps connecting and reconnecting. It would look like, to me, there are some earthing issues with regard to the flyswatter. The weird thing is port A seems more stable than port B. But I do not know that conclusively at this stage. If I connect my target using a different USB->RS232 adapter I have no problems. So I was going to abandon using the 232 port of the flyswatter and hope it made it more reliable. If that doesn't work and Port A exhibits the same weirdness, then I am going to hunt around for a better interface. I am going to get a new USB cable to rule a bad cable out, but If that doesn't fix it I will put it down to the flyswatter acting up. Strontium. dmesg shows this over and over if the target is unplugged: [517117.448429] hub 1-2:1.0: Cannot enable port 1. Maybe the USB cable is bad? [517117.520417] usb 1-2.1: new full speed USB device using ehci_hcd and address 86 [517117.593930] usb 1-2.1: device descriptor read/64, error -71 [517117.768296] usb 1-2.1: device descriptor read/64, error -71 [517117.948432] usb 1-2.1: new full speed USB device using ehci_hcd and address 87 [517118.356050] usb 1-2.1: device not accepting address 87, error -71 [517118.428319] usb 1-2.1: new full speed USB device using ehci_hcd and address 88 [517118.840047] usb 1-2.1: device not accepting address 88, error -71 [517118.840335] hub 1-2:1.0: unable to enumerate USB device on port 1 [517118.912419] usb 1-2.4: reset high speed USB device using ehci_hcd and address 12 and this is what it shows if I simply earth my target through a USB cable back to my PC: [517180.304062] usb 1-2: reset high speed USB device using ehci_hcd and address 11 [517180.716396] usb 1-2.1: new full speed USB device using ehci_hcd and address 113 [517183.268323] usb 1-2.1: device descriptor read/64, error -71 [517183.444328] usb 1-2.1: device descriptor read/64, error -71 [517183.620328] usb 1-2.1: new full speed USB device using ehci_hcd and address 114 [517183.693214] usb 1-2.1: device descriptor read/64, error -71 [517186.708391] hub 1-2:1.0: Cannot enable port 1. Maybe the USB cable is bad? [517186.780398] usb 1-2.1: new full speed USB device using ehci_hcd and address 115 [517186.810548] usb 1-2.1: configuration #1 chosen from 1 choice [517186.810849] ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected [517186.810890] usb 1-2.1: Detected FT2232C [517186.810952] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 [517186.813473] ftdi_sio 1-2.1:1.1: FTDI USB Serial Device converter detected [517186.813510] usb 1-2.1: Detected FT2232C [517186.813585] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB1 [517186.904400] usb 1-2.4: reset high speed USB device using ehci_hcd and address 12 [517191.231107] hub 1-2:1.0: port 1 disabled by hub (EMI?), re-enabling... [517191.231477] usb 1-2.1: USB disconnect, address 115 [517191.231920] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [517191.231946] ftdi_sio 1-2.1:1.0: device disconnected [517191.233777] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1 [517191.233804] ftdi_sio 1-2.1:1.1: device disconnected [517191.432371] usb 1-2.1: new full speed USB device using ehci_hcd and address 116 [517191.530529] usb 1-2.1: configuration #1 chosen from 1 choice [517191.530825] ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected [517191.530865] usb 1-2.1: Detected FT2232C [517191.530929] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 [517191.567321] ftdi_sio 1-2.1:1.1: FTDI USB Serial Device converter detected [517191.567363] usb 1-2.1: Detected FT2232C [517191.567425] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB1 [517192.255128] hub 1-2:1.0: port 1 disabled by hub (EMI?), re-enabling... [517192.255499] usb 1-2.1: USB disconnect, address 116 [517192.255933] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [517192.255959] ftdi_sio 1-2.1:1.0: device disconnected [517192.257679] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1 [517192.257705] ftdi_sio 1-2.1:1.1: device disconnected [517192.456392] usb 1-2.1: new full speed USB device using ehci_hcd and address 117 [517192.554545] usb 1-2.1: configuration #1 chosen from 1 choice [517192.554846] ftdi_sio 1-2.1:1.0: FTDI USB Serial Device converter detected [517192.554979] usb 1-2.1: Detected FT2232C [517192.555044] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 [517192.570018] ftdi_sio 1-2.1:1.1: FTDI USB Serial Device converter detected [517192.570060] usb 1-2.1: Detected FT2232C [517192.570122] usb 1-2.1: FTDI USB Serial Device converter now attached to ttyUSB1 The alert: hub 1-2:1.0: port 1 disabled by hub (EMI?), re-enabling... happens all the time when port B fails. Magnus Lundin wrote: > Win, Linux or Mac ?? > > I have now for a few days tested this with a flyswatter+beagleboard > under Fedora 10. > The serial connection stays active when I start and also when I quit > openocd. > > Best regards, > Magnus > > > > Strontium 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. >> >> 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. >> >> > target [tty] [enable/disable] [rate] [bits] [parity] [stop] >> >> Enables the display of any data received from the target on a connected >> jtag interface (in this case the flyswatter) [tty] is for hypothetical >> devices which could have multiple serial ports on them, and would be >> 0,1,2, etc. [rate], etc is only valid for an enable. >> >> Data from the target would then be shown as: >> target 0: [data] >> >> > target_cmd [tty] [data] >> >> Data is sent verbatim, minus the first space after tty, over the serial >> line nominated through the jtag interface. >> >> Its for text work, it isn't intended to transfer files and such. I am >> thinking of interacting with boot loaders, seeing debug messages and the >> like. >> >> The commands are independent. The target tty could be disabled (its >> still set up, just not being displayed) which just means output from the >> target is suppressed, but target_cmd would still try and send data to >> the target. >> >> Or something like that. >> >> >> Strontium >> >> >> _______________________________________________ >> Openocd-development mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/openocd-development >> >> > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
