Sorry. The problem was in a Copy&Paste error where i have defined the endpoint numbers as:
TI_EP_BULK_UART1_OUT = 0x01 TI_EP_BULK_UART1_OUT = 0x81 And they should be: TI_EP_BULK_UART1_OUT = 0x01 TI_EP_BULK_UART1_IN = 0x81 and the tryed to WRITE to an INPUT endpoint. Question: shouldnt this raise an exception on pyusb? Another question: Do you know some good USB sniffer. I used vusb-analyzer but it needs a lot more improvement. Thanks. Diego 2010/7/8 Diego Jacobi <jacobidi...@gmail.com>: > Hello people. > > I am working with a TUSB3410 chip which by default creates a virtual > serial port. > But i want to comunicate directly with it with pyusb instead of pyserial. > > I have a working basic 9600 bps configuration done but when i send > data with dev.write(1, data, 0, 1000) it fails with Timed out error. > > I can test it by opening the serial port with gtkterm. > > Then i dettach the driver, set some initialization control words and do this: > > print "SEND: Hello World!" > print dev.write(TI_EP_BULK_UART1_OUT, "Hello World!",0,1000) > > print "RECV: Hello World!" > print dev.write(TI_EP_BULK_UART1_IN, 30 ,0,1000) > > > Because i cant find directly information on how the serial data is > transmitted, and because "i think" that i have readed that this kind > of devices uses bulk endpoints to transfer the data, then i know that > thoose endpoints are Endpoint 1 IN and OUT. Endpoint 2 in is used to > transfer some "device interrupt" information which i dont need right > now. > > Any ideas?? > > > > > Below is the descriptor: > > > > > Bus 003 Device 064: ID 0451:3410 Texas Instruments, Inc. TUSB3410 > Microcontroller > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0451 Texas Instruments, Inc. > idProduct 0x3410 TUSB3410 Microcontroller > bcdDevice 0.01 > iManufacturer 1 > iProduct 2 > iSerial 3 > bNumConfigurations 2 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 2 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 2 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x01 EP 1 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 10 > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
