| 00:28.42 | *** join/#openjtag brolin (n=brolin@190.157.14.3) |
| 00:47.39 | *** join/#openjtag uwe_ (n=uwe_@dslb-084-056-024-012.pools.arcor-ip.net) |
| 01:05.41 | *** join/#openjtag rje`mac (n=rje`mac@c-67-185-128-239.hsd1.wa.comcast.net) |
| 09:16.26 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 11:15.37 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 12:34.17 | Strontium | anybody here know anything about the flyswatter? |
| 14:08.31 | *** join/#openjtag roxfan (n=dunno@242.42-244-81.adsl-dyn.isp.belgacom.be) |
| 14:35.34 | *** join/#openjtag dirk2 (n=dirk@p5B041EE6.dip0.t-ipconnect.de) |
| 14:55.26 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 14:58.57 | keesj | Strontium: what is your question? |
| 15:04.46 | *** join/#openjtag Strontium (n=Strontiu@115.134.178.127) |
| 15:04.58 | keesj | Strontium: what is your question? |
| 15:05.53 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 15:06.39 | Strontium | I wondered if it is normal to have problems using both OpenOCD and the on board serial port of the flyswatter (uisng /dev/ttyUSB1) at the same time. |
| 15:10.14 | keesj | "normal" is a little strange in this context. It is know that if you first connect to the board via serial and only after that start openocd the serial goes boom |
| 15:10.35 | keesj | but you can still "reconnect" afterwards , are you have more the the "normal" problem? |
| 15:10.55 | Strontium | yes, i cant reconnect after |
| 15:14.50 | keesj | Somebody (you?) mailed about this yesterday on the mailing list |
| 15:15.12 | Strontium | yep |
| 15:15.27 | keesj | I don't think this is normal behaviour(at least I think it should be possible to modify openocd to not do this) |
| 15:16.11 | Strontium | i have since hacked up a quick and dirty program to dump serial data from the port, using libftdi, but it doesnt work for port B, only port A. I get errors in dmesg if I try port B |
| 15:16.36 | Strontium | I think the error is something to do with libftdi and libusb interaction |
| 15:17.02 | Strontium | I think when you open the ft2232 with libftdi it just grabs the whole device. (both ports) |
| 15:17.23 | roxfan | have you tried the other ftd lib? |
| 15:18.06 | Strontium | well yes, and no. I didnt get much sense out of it, so didnt persevere. I should go back to it and do more experiments. |
| 15:18.35 | keesj | booth have the problem |
| 15:18.53 | keesj | I don't know if libusb even allows this |
| 15:20.00 | Strontium | I will keep experimenting. I am currently about to install the latest libftdi from source (rather than the one that ubuntu ships) |
| 15:20.20 | Strontium | That way I can put some tests into the library to try and work out what is going on |
| 15:23.41 | keesj | probably this: |
| 15:23.42 | keesj | src/ftdi.c: if (usb_detach_kernel_driver_np(ftdi->usb_dev, ftdi->interface) != 0 && errno != ENODATA) |
| 15:27.09 | Strontium | A quick check would indicate if interface is correct, then it should only detach the driver for ttyUSB0 |
| 15:27.14 | keesj | (this is libftdi-0.15) |
| 15:29.38 | Strontium | although looking at that code showed me my bug. I was calling set interface AFTER the open. It needs to be called before. |
| 15:31.13 | Strontium | OpenOCD does the same thing |
| 15:32.57 | Strontium | Although in OpenOCD's case, it should be not a problem, because interface A is the default |
| 15:33.02 | Strontium | still |
| 15:43.01 | Strontium | I will link up my test program which can simulate the openocd problem and trace it through GDB to find out which particular usb operation kills Interface B tomorrow. |
| 19:01.45 | *** join/#openjtag ChanServ (ChanServ@services.) |
| 19:01.45 | *** mode/#openjtag [+o ChanServ] by irc.freenode.net |
| 20:03.09 | *** join/#openjtag Strontium (n=Strontiu@115.134.178.127) |