Re: [Pyusb-users] Cleverboard part 3

2008-12-23 Thread Phil Hannent
Phil Hannent wrote: > Wander Lairson wrote: > >> By I remmember from USB Spec, endpoint 0x81 should be IN (MSB 1) and >> endpoint 0x2 should be OUT (MSB 0). I don't what are exactly the side >> effects of inverting them... Did you write the device firmware also? >> If not, probably you should sw

Re: [Pyusb-users] Cleverboard part 3

2008-12-23 Thread Phil Hannent
Wander Lairson wrote: > By I remmember from USB Spec, endpoint 0x81 should be IN (MSB 1) and > endpoint 0x2 should be OUT (MSB 0). I don't what are exactly the side > effects of inverting them... Did you write the device firmware also? > If not, probably you should swap the values of PLUG_BULK_IN_E

Re: [Pyusb-users] Cleverboard part 3

2008-12-22 Thread Wander Lairson
By I remmember from USB Spec, endpoint 0x81 should be IN (MSB 1) and endpoint 0x2 should be OUT (MSB 0). I don't what are exactly the side effects of inverting them... Did you write the device firmware also? If not, probably you should swap the values of PLUG_BULK_IN_EP and PLUG_BULK_OUT_EP. If so,

Re: [Pyusb-users] Cleverboard part 3

2008-12-22 Thread Phil Hannent
Wander Lairson wrote: > What are the constants PLUG_BULK_IN_EP and PLUG_BULK_OUT_EP? > They are: PLUG_BULK_IN_EP = 0x2 PLUG_BULK_OUT_EP = 0x81 The device enumerates to: Device: 006 Device class: 255 Device sub class: 0 Device protocol: 255 Max packet size: 8 idVendor: 2259 i

Re: [Pyusb-users] Cleverboard part 3

2008-12-22 Thread Wander Lairson
What are the constants PLUG_BULK_IN_EP and PLUG_BULK_OUT_EP? 2008/12/23 Phil Hannent : > Hello, > > Wander Lairson wrote: >> Well, I think you are doing things in the right way, may be the >> problem is a device protocol issue. Perhaps you are issuing the wrong >> command to get what you want... H

Re: [Pyusb-users] Cleverboard part 3

2008-12-22 Thread Phil Hannent
Hello, Wander Lairson wrote: > Well, I think you are doing things in the right way, may be the > problem is a device protocol issue. Perhaps you are issuing the wrong > command to get what you want... How do you get the storage capacity? > How many bytes are expected to return? Please, post the co

Re: [Pyusb-users] Cleverboard part 3

2008-12-22 Thread Wander Lairson
Well, I think you are doing things in the right way, may be the problem is a device protocol issue. Perhaps you are issuing the wrong command to get what you want... How do you get the storage capacity? How many bytes are expected to return? Please, post the code here (with comments). 2008/12/22 P

Re: [Pyusb-users] Cleverboard part 2

2008-12-19 Thread Phil Hannent
Phil Hannent wrote: > When I do: > read_bytes = > self.handle.interruptRead(PlugUSBDevice.PLUG_BULK_OUT_EP,sent_bytes); > > How can I split the read_bytes so that I can read each byte individually? > > if I print it I just get: > (33, 1, 32) > Ok, so I figured out that if I read while there was

Re: [Pyusb-users] Cleverboard

2008-12-18 Thread Wander Lairson
Read the the limit quantity of bytes. If there is less bytes, they will be returned... 2008/12/19 Santiago Palomino Sanchez-Manjavacas : > Hi, The thing is that you can always send 64 bytes as normal packet, and in > some cases, do not use all of them. > > Another approach es that the interrupt wi

Re: [Pyusb-users] Cleverboard

2008-12-18 Thread Santiago Palomino Sanchez-Manjavacas
Hi, The thing is that you can always send 64 bytes as normal packet, and in some cases, do not use all of them. Another approach es that the interrupt will trigger a bulk read of a variable size determined by what the interrupt packet says. But in that case, you will have several usb transactions,