Hi Stephan, On Mon, Aug 16, 2010 at 11:04:54PM +0200, Stephan wrote: > Hi Johan, > > since kernel version 2.6.31 i cannot flash my msba2 device. this device > communicates via ft232rl ftdi interface. every time i want to flash an > image via lpc2k_pgm flasher tool it stops flashing when sending first > read to device. in that way it is similar to the problem described here: > http://www.spinics.net/lists/linux-usb/msg34099.html > also the "usb_serial_generic_read_bulk_callback" output in kernel > log(below) points to the problem described above(link). The read_bulk_callbacks are part of normal operation of the driver and does not indicate an error in itself. > you can see that it stops flashing in the strace output below. the bug > occurs every time i want to flash the msba2 device and only with > ftdi_sio versions 1.5.0 and 1.6.0. ftdi version 1.4.3 works well. > my setup is following: > > msba2 board with ft232rl ftdi interface > debian squezze with 2.6.35.2 kernel > > i can not flash from kernel version 2.6.31. for example 2.6.30.10 works. I did a quick search for your hardware and it seems that your board is using the DTS/RTS lines to put the MCU in reset. The way modem control is handled has changed in the ftdi_sio driver and is likely to be the cause of your problems. > in the lpc2k_pgm flasher tool the read command in following method cause > the problem: > > int read_serial_port(unsigned char *buf, int bufsize) > { > int num; > > num = read(port_fd, buf, bufsize); > > return num; > } > > I've attached the kern.log files with working setup and with not working > setup: > > working = first_kern.log > not workin = second_kern.log What are the exact versions of the kernel that were used to produce these logs? It would be helpful if you could track down the first version for which your application stopped working, preferably using git bisect but a stable release number could also suffice. Thanks, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
