Thread: [Libusb-win32-devel] (no subject)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

confirm 345291

Hi,

?

There appears to be two home pages for libUSB:

? http://libusb.sourceforge.net/index.html

? http://libusb-win32.sourceforge.net/

?

Are they describing the same product? Or are they describing
two different competing products?

Is there a difference between libusb and libusb-win32?

?

?

Faithfully,

Sean B. Durkin

(s.d...@gr...)

________________________________________________________________________
Check Out the new free AIM(R) Mail -- Unlimited storage and industry-leading spam and email virus protection.

Sean:
        As far as my knowledge goes, libusb is for Linux platform whereas
libusb-win32 is for Windows platform. Their APIs are compatible with each
other.

On 9/14/07, sea...@ne... <sea...@ne...> wrote:
>
> Hi,
>
> There appears to be two home pages for libUSB:
>   http://libusb.sourceforge.net/index.html
>   http://libusb-win32.sourceforge.net/
>
> Are they describing the same product? Or are they describing two different
> competing products?
> Is there a difference between libusb and libusb-win32?
>
>
> Faithfully,
> Sean B. Durkin
> (s.d...@gr...)
>  ------------------------------
> *Check Out the new free AIM(R) Mail*<http://o.aolcdn.com/cdn.webmail.aol.com/mailtour/aim/en-us/index.htm>-- Unlimited storage and industry-leading spam and email virus protection.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>

Hello,
Please unsubscribe me from this mailing list. 		 	   		  
On Sat, Jul 31, 2010 at 11:57 PM, tjado buining <tj...@ho...> wrote:
> Hello,
> Please unsubscribe me from this mailing list.
>

Hmm, you guys must have come across the following
link every time you receive a post. Please go here to
unsubscribe.
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
Xiaofan

Hi,

I'm trying to send Control messages to the ports of my Hub device Cypress CY7C65630 (PID=0x04B4 VID=6560) under XP (32-bit).  inf-wizard.exe recognizes my "Generic USB Hub" and creates and installs the driver.  The hub then re-enumerates in Device Manager as under a libusb-win32 Device.  So far so good.

I cannot, however, detect this device with its new driver using testlibusb-win.exe or testlibusb.exe.  The application I originally wrote in Linux cannot recognize any devices attached to my system either.

I tried running a filter driver, just as a backup, but that program cannot recognize my device with libusb driver, or the standard MS driver.

I've tried removing drivers, reinstalling, etc, a few times and am pretty much stumped at this point.  Any help is appreciated.

Thanks in advance.
On 11/17/2011 1:47 PM, steven guzior wrote:
> Hi,
>
> I'm trying to send Control messages to the ports of my Hub device 
> Cypress CY7C65630 (PID=0x04B4 VID=6560) under XP (32-bit).  
> inf-wizard.exe recognizes my "Generic USB Hub" and creates and 
> installs the driver.  The hub then re-enumerates in Device Manager as 
> under a libusb-win32 Device.  So far so good.
>
> I cannot, however, detect this device with its new driver using 
> testlibusb-win.exe or testlibusb.exe.  The application I originally 
> wrote in Linux cannot recognize any devices attached to my system either.
>
> I tried running a filter driver, just as a backup, but that program 
> cannot recognize my device with libusb driver, or the standard MS driver.
>
> I've tried removing drivers, reinstalling, etc, a few times and am 
> pretty much stumped at this point.  Any help is appreciated.
>

The driver does not support USB device hubs.  This was done 
intentionally some time ago a because most of the APIs are device 
specific and cause problems with device hubs.

You can re-enable this functionality by removing this hunk from 
libusb_driver.c:
     // Don't attach to usb device hubs
     if (strstr(compat_id, "class_09"))
     {
         USBDBG("skipping usb device hub (%s) %s\n",compat_id, id);
         return STATUS_SUCCESS;
     }

Regards,
Travis

Dear friends,
I have installed libusb drivers for my usb device (texas C5515 DSP
eZdsp usb stick).now I want to use a host application for some simple
bulk transfer. I think I can use the source codes in the
libusb/examples folder. However there is not any executable files,so
how can I run the examples?
Any help will be appreciated.. Thanks in advance.
Best Regards...

yusufs

On Mon, Apr 9, 2012 at 5:09 PM, Yusuf Sekman <ys...@gm...> wrote:
> Dear friends,
> I have installed libusb drivers for my usb device (texas C5515 DSP
> eZdsp usb stick).now I want to use a host application for some simple
> bulk transfer. I think I can use the source codes in the
> libusb/examples folder. However there is not any executable files,so
> how can I run the examples?
> Any help will be appreciated.. Thanks in advance.

You can build the examples. The examples are there for
you to adapt to your own boards and then build your own
binaries.

-- 
Xiaofan

Hi Xiaofan,
Thank you for your answer, I am trying on it. I have a question.
In the Wiki page, in build process section, there is an explanation as below:

"Starting from version 1.1.4.0, batch files in the DDK_MAKE directory
will be the main tools to build the driver, library, and distribution
packages.

Download the latest source code.
Edit make.cfg according to your particular setup (WDK directory,
locations of MinGW, Borland C++, Inno Setup, etc).
Use the provided batch files to the build the 32bit/64bit drivers,
library and test programs. Please refer to the output of "make.cmd"
for more build options.
To build the distribution archives and the installer run "make.cmd
dist". Please refer to the output of "make.cmd" for more build
options."

I did not understand where the DDK_MAKE directory and also make.cfg
file are. Are these steps for building examples and libraries?
Best Regards...
Yusufs

9 Nisan 2012 13:27 tarihinde Xiaofan Chen <xia...@gm...> yazdı:
> On Mon, Apr 9, 2012 at 5:09 PM, Yusuf Sekman <ys...@gm...> wrote:
>> Dear friends,
>> I have installed libusb drivers for my usb device (texas C5515 DSP
>> eZdsp usb stick).now I want to use a host application for some simple
>> bulk transfer. I think I can use the source codes in the
>> libusb/examples folder. However there is not any executable files,so
>> how can I run the examples?
>> Any help will be appreciated.. Thanks in advance.
>
> You can build the examples. The examples are there for
> you to adapt to your own boards and then build your own
> binaries.
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

2012/4/9 Yusuf Sekman <ys...@gm...>:
> Hi Xiaofan,
> Thank you for your answer, I am trying on it. I have a question.
> In the Wiki page, in build process section, there is an explanation as below:
>
> "Starting from version 1.1.4.0, batch files in the DDK_MAKE directory
> will be the main tools to build the driver, library, and distribution
> packages.
>
> Download the latest source code.
> Edit make.cfg according to your particular setup (WDK directory,
> locations of MinGW, Borland C++, Inno Setup, etc).
> Use the provided batch files to the build the 32bit/64bit drivers,
> library and test programs. Please refer to the output of "make.cmd"
> for more build options.
> To build the distribution archives and the installer run "make.cmd
> dist". Please refer to the output of "make.cmd" for more build
> options."
>
> I did not understand where the DDK_MAKE directory and also make.cfg
> file are. Are these steps for building examples and libraries?

They are mainly used by the project maintainer (Travis and I)
to build the release packages (include the driver, dll, and
libraries).

If you only need to build the examples, then you should not
need to use them.

-- 
Xiaofan

Hello,
Thanks for your quick replies..

@Ekkehard
I have tried your suggestion, but it didn't work. Actually, if the problem
would be like what you are saying, why it is working when receiving data
from the host.?
Thank you for your help..

@Xiaofan
The fifo size of my device is 64 bytes to 4K bytes. I set it to 64 bytes.
It was a misunderstanding of mine. I have tried sending 2 bytes , it also
did not work. I am  confused about what I am doing right while receiving
data and I am not doing it while sending data to PC.? Do you have any idea
about the firmware differences between sending and receiving data?

Thanks for your help, those were very helpful.

Best of all...
Yusuf

Sorry, but I can not help further.
Reagrds
Ekkehard

--
View this message in context: http://libusb.6.n5.nabble.com/no-subject-tp5627034p5644151.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

Dear friends,

I am trying to send data to host via bulk transfer. Receiving data from
device works however, while running bulk.c example host software for
reading data from device, I see that error:

error reading:
libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
A device attached to the system is not functioning.

What could be the problem related to this message?
Thanks in advance.

Best,
Yusuf

On Wed, Apr 18, 2012 at 8:08 PM, Yusuf Sekman <ys...@gm...> wrote:
> Dear friends,
>
> I am trying to send data to host via bulk transfer. Receiving data from
> device works however, while running bulk.c example host software for reading
> data from device, I see that error:
>
> error reading:
> libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
> A device attached to the system is not functioning.
>
> What could be the problem related to this message?
> Thanks in advance.
Pretty sure it is a firmware bug. Please try the ZLP suggestion.

Other than that, I have say libusb-win32 mailing list is
probably not the best place to help you on debugging
your firmware. Probably you can go to TI E2E forum for
better help.
http://e2e.ti.com/support/default.aspx

-- 
Xiaofan

Hello Xiaofan,

I ran the bulk.c example using Visual Studio 2010. I managed to read
success: device 0925:1456opened
success: set_configuration #1
success: claim_interface #0 logs in the output console.

After those above, the code gets into usb_bulk_read function. And
gives error as I expect because there is not any bulk transfer routine
in my firmware right now.
However, while debugging the firmware code, I realize that EP1 TX or
RX interrupts never occur in my USB controller.
Does that constitutes a problem before adding proper bulk transfer
routine in my firmware? or is that a problem not to see any EP1 TX
interrupts in the USB device.

Thanks for all your help.
Sincerely...
Yusuf

On Wed, Apr 11, 2012 at 8:10 PM, Yusuf Sekman <ys...@gm...> wrote:
> Hello Xiaofan,
>
> I ran the bulk.c example using Visual Studio 2010. I managed to read
> success: device 0925:1456opened
> success: set_configuration #1
> success: claim_interface #0 logs in the output console.
>
> After those above, the code gets into usb_bulk_read function. And
> gives error as I expect because there is not any bulk transfer routine
> in my firmware right now.
> However, while debugging the firmware code, I realize that EP1 TX or
> RX interrupts never occur in my USB controller.
> Does that constitutes a problem before adding proper bulk transfer
> routine in my firmware? or is that a problem not to see any EP1 TX
> interrupts in the USB device.

I do not think this is a problem. You need to get your firmware
right first.

-- 
Xiaofan

Hello Xiaofan,

I have another question about bulk.c example. I am trying to run the
example with my firmware code loaded into TI C5515 DSP.
When the bulk.c program running, the console says :

 success: device 0925:1456opened
 success: set_configuration #1
 success: claim_interface #0
error reading:
libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
A device attached to the system is not functioning.

I simply know that, my firmware code is not working properly, as I
understand from the error. But my question is that at which stage of
the transfer, my firmware fails?
Additionally, I see the error when the device starts to run. For a
second run of bulk.c program, I see timeout error at reading stage.
Does this imply anything for my situation?

I appreciate for your helps. Regards.
Yusuf

11 Nisan 2012 16:18 tarihinde Xiaofan Chen <xia...@gm...> yazdı:
> On Wed, Apr 11, 2012 at 8:10 PM, Yusuf Sekman <ys...@gm...> wrote:
>> Hello Xiaofan,
>>
>> I ran the bulk.c example using Visual Studio 2010. I managed to read
>> success: device 0925:1456opened
>> success: set_configuration #1
>> success: claim_interface #0 logs in the output console.
>>
>> After those above, the code gets into usb_bulk_read function. And
>> gives error as I expect because there is not any bulk transfer routine
>> in my firmware right now.
>> However, while debugging the firmware code, I realize that EP1 TX or
>> RX interrupts never occur in my USB controller.
>> Does that constitutes a problem before adding proper bulk transfer
>> routine in my firmware? or is that a problem not to see any EP1 TX
>> interrupts in the USB device.
>
> I do not think this is a problem. You need to get your firmware
> right first.
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

2012/4/12 Yusuf Sekman <ys...@gm...>:
> Hello Xiaofan,
>
> I have another question about bulk.c example. I am trying to run the
> example with my firmware code loaded into TI C5515 DSP.
> When the bulk.c program running, the console says :
>
>  success: device 0925:1456opened
>  success: set_configuration #1
>  success: claim_interface #0
> error reading:
> libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
> A device attached to the system is not functioning.
>
> I simply know that, my firmware code is not working properly, as I
> understand from the error. But my question is that at which stage of
> the transfer, my firmware fails?
> Additionally, I see the error when the device starts to run. For a
> second run of bulk.c program, I see timeout error at reading stage.
> Does this imply anything for my situation?
>
> I appreciate for your helps. Regards.

I think libusb-win32 may not be the best debug tool for
your firmware. Do you have access to a HW debugger for
your device? Do you have access to a USB HW analyzer?

If not, then probably you can make use of the debug
version of libusb-win32 and then use DebugView
to post the debug log. Please search the archive
on how to do that.

-- 
Xiaofan

Hello Xiaofan,
I've started to use USB Trace Software Tool for debugging. I can trace bulk
in our transactions and success of fail status for all.
By the way, I have tried to receive data from the host. As you remember, I
use bulk.c example and I could read data coming from PC to my device.
But still I am not able to send data to PC. Size of EP1 FIFO Register in
C5515 DSP is 2bytes, so the device sends 64 byte data as an array of 2 byte
data packets.
However in bulk.c program, the data is read by 1byte for each element of
data array(because tmp[] and *bytes variables are defined as char). Do you
think that the problem occurs because of this conflict.? And what do you
recommend to modify bulk.c file?

I would like to quote the data transaction routines that I wrote for device
firmware for your information:

//////////////////////////////
//EP1 interrupt service
 //////////////////////////////

   //EP1 sending a data package to host

   if (ep1_tx == 0x0002)
   {
           //usbOn=0;
//printf("EP1 TX Interrupt Received./n");

fifo_write_ep1(pBuffer16_ep1,halfpacketSize);
USB_PERI_TXCSR_EP1 |= 0x01; //Set TXPKTRDY (B0 of PERI_TXCSR)
// USB_PERI_TXCSR_EP1 |= 0x10; //SENDSTALL BIT

   }

   //EP1 receiving a data package from host
   if (ep1_rx == 0x0200)
   {
fifo_read_ep1(pBuffer16_ep1_read, halfpacketSize);
USB_PERI_TXCSR_EP1 &= 0xFE;
printBuffer (pBuffer16_ep1_read, halfpacketSize);
//usbOn = 0;
 }

12 Nisan 2012 18:04 tarihinde Xiaofan Chen <xia...@gm...> yazdı:
> 2012/4/12 Yusuf Sekman <ys...@gm...>:
>> Hello Xiaofan,
>>
>> I have another question about bulk.c example. I am trying to run the
>> example with my firmware code loaded into TI C5515 DSP.
>> When the bulk.c program running, the console says :
>>
>>  success: device 0925:1456opened
>>  success: set_configuration #1
>>  success: claim_interface #0
>> error reading:
>> libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
>> A device attached to the system is not functioning.
>>
>> I simply know that, my firmware code is not working properly, as I
>> understand from the error. But my question is that at which stage of
>> the transfer, my firmware fails?
>> Additionally, I see the error when the device starts to run. For a
>> second run of bulk.c program, I see timeout error at reading stage.
>> Does this imply anything for my situation?
>>
>> I appreciate for your helps. Regards.
>
> I think libusb-win32 may not be the best debug tool for
> your firmware. Do you have access to a HW debugger for
> your device? Do you have access to a USB HW analyzer?
>
> If not, then probably you can make use of the debug
> version of libusb-win32 and then use DebugView
> to post the debug log. Please search the archive
> on how to do that.
>
>
>
> --
> Xiaofan
>
>
------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Hello Xiaofan,
I've started to use USB Trace Software Tool for debugging. I can trace bulk
in our transactions and success of fail status for all.
By the way, I have tried to receive data from the host. As you remember, I
use bulk.c example and I could read data coming from PC to my device.
But still I am not able to send data to PC. Size of EP1 FIFO Register in
C5515 DSP is 2bytes, so the device sends 64 byte data as an array of 2 byte
data packets.
However in bulk.c program, the data is read by 1byte for each element of
data array(because tmp[] and *bytes variables are defined as char). Do you
think that the problem occurs because of this conflict.? And what do you
recommend to modify bulk.c file?

I would like to quote the data transaction routines that I wrote for device
firmware for your information:

 USB_FIFO0R1 and  USB_FIFO1R1  registers are called Transmit and Receive
FIFO Register 1 for Endpoint 0/1.
 USB_PERI_TXCSR_EP1 register is said to be modified when the data is loaded
to FIFO.

//////////////////////////////
//EP1 interrupt service
 //////////////////////////////

 //EP1 sending a data package to host

   if (ep1_tx == 0x0002)
          {
                 fifo_write_ep1(pBuffer16_ep1,halfpacketSize);
                 USB_PERI_TXCSR_EP1 |= 0x01; //Set TXPKTRDY (B0 of
PERI_TXCSR)
          }

 //EP1 receiving a data package from host

   if (ep1_rx == 0x0200)
   {
          fifo_read_ep1(pBuffer16_ep1_read, halfpacketSize);
          USB_PERI_TXCSR_EP1 &= 0xFE;
          printBuffer (pBuffer16_ep1_read, halfpacketSize);
   }

void fifo_write(Uint16 *buf, int size)
{
    int i;

    USBSCR |= 2; //enable byte access by CPU and LOW-byte is selected
    for (i=0; i<size; i++)
    {
        USB_FIFO0R1 = *buf;
        buf++;
    }
    USBSCR &= ~0x03; //enable word access by CPU
}

void fifo_write_ep1(Uint16 *buf, int size)
{
int i;

    USBSCR |= 2; //enable byte access by CPU and LOW-byte is selected
    for (i=0; i<size; i++)
    {
        USB_FIFO1R1 = *buf;
        buf++;
    }
    USBSCR &= ~0x03; //enable word access by CPU
}

void fifo_read_ep1(Uint16 *buf, int size)
{
int i;
 USBSCR |= 2; //enable byte access by CPU and LOW-byte is selected
    for (i=0; i<size; i++)
    {
        *buf = USB_FIFO1R1 ;
        buf++;
    }
    USBSCR &= ~0x03; //enable word access by CPU
}

I will appreciate for any interest in help me. Thanks in advance..
Best Regards.
Yusuf

13 Nisan 2012 16:36 tarihinde Yusuf Sekman <ys...@gm...> yazdı:

> Hello Xiaofan,
> I've started to use USB Trace Software Tool for debugging. I can trace
> bulk in our transactions and success of fail status for all.
> By the way, I have tried to receive data from the host. As you remember, I
> use bulk.c example and I could read data coming from PC to my device.
> But still I am not able to send data to PC. Size of EP1 FIFO Register in
> C5515 DSP is 2bytes, so the device sends 64 byte data as an array of 2 byte
> data packets.
> However in bulk.c program, the data is read by 1byte for each element of
> data array(because tmp[] and *bytes variables are defined as char). Do you
> think that the problem occurs because of this conflict.? And what do you
> recommend to modify bulk.c file?
>
> I would like to quote the data transaction routines that I wrote for
> device firmware for your information:
>
> //////////////////////////////
> //EP1 interrupt service
>  //////////////////////////////
>
>    //EP1 sending a data package to host
>
>    if (ep1_tx == 0x0002)
>    {
>            //usbOn=0;
> //printf("EP1 TX Interrupt Received./n");
>
> fifo_write_ep1(pBuffer16_ep1,halfpacketSize);
> USB_PERI_TXCSR_EP1 |= 0x01; //Set TXPKTRDY (B0 of PERI_TXCSR)
> // USB_PERI_TXCSR_EP1 |= 0x10; //SENDSTALL BIT
>
>    }
>
>    //EP1 receiving a data package from host
>    if (ep1_rx == 0x0200)
>    {
> fifo_read_ep1(pBuffer16_ep1_read, halfpacketSize);
> USB_PERI_TXCSR_EP1 &= 0xFE;
> printBuffer (pBuffer16_ep1_read, halfpacketSize);
> //usbOn = 0;
>  }
>
>
> 12 Nisan 2012 18:04 tarihinde Xiaofan Chen <xia...@gm...> yazdı:
>
> > 2012/4/12 Yusuf Sekman <ys...@gm...>:
> >> Hello Xiaofan,
> >>
> >> I have another question about bulk.c example. I am trying to run the
> >> example with my firmware code loaded into TI C5515 DSP.
> >> When the bulk.c program running, the console says :
> >>
> >>  success: device 0925:1456opened
> >>  success: set_configuration #1
> >>  success: claim_interface #0
> >> error reading:
> >> libusb0-dll:err [_usb_reap_async] reaping request failed,win error:
> >> A device attached to the system is not functioning.
> >>
> >> I simply know that, my firmware code is not working properly, as I
> >> understand from the error. But my question is that at which stage of
> >> the transfer, my firmware fails?
> >> Additionally, I see the error when the device starts to run. For a
> >> second run of bulk.c program, I see timeout error at reading stage.
> >> Does this imply anything for my situation?
> >>
> >> I appreciate for your helps. Regards.
> >
> > I think libusb-win32 may not be the best debug tool for
> > your firmware. Do you have access to a HW debugger for
> > your device? Do you have access to a USB HW analyzer?
> >
> > If not, then probably you can make use of the debug
> > version of libusb-win32 and then use DebugView
> > to post the debug log. Please search the archive
> > on how to do that.
> >
> >
> >
> > --
> > Xiaofan
> >
> >
> ------------------------------------------------------------------------------
> > For Developers, A Lot Can Happen In A Second.
> > Boundary is the first to Know...and Tell You.
> > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> > http://p.sf.net/sfu/Boundary-d2dvs2
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

2012/4/13 Yusuf Sekman <ys...@gm...>:
> By the way, I have tried to receive data from the host. As you remember, I
> use bulk.c example and I could read data coming from PC to my device.
> But still I am not able to send data to PC. Size of EP1 FIFO Register in
> C5515 DSP is 2bytes, so the device sends 64 byte data as an array of 2 byte
> data packets.

Are you sure it is 2bytes? In that case, it is very small buffer.

> However in bulk.c program, the data is read by 1byte for each element of
> data array(because tmp[] and *bytes variables are defined as char).

Where do you get this? BUF_SIZE is 64 BYTES in bulk.c, corresponding
to the wMaxPacketSize of EP1 IN and EP1 OUT in our benchmark
firmware.

> Do you think that the problem occurs because of this conflict.?
> And what do you recommend to modify bulk.c file?
>

What is the output of testlibusb-win for your device?

-- 
Xiaofan

Here is the output of TestLibUsb :

DLL version: 1.2.6.0
Driver version: 1.2.6.0

bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0925-0x1456     0925/1456
- Manufacturer : KARDIOSIS
- Product      : YUSUF
bLength:             18
bDescriptorType:     01h
bcdUSB:              0200h
bDeviceClass:        00h
bDeviceSubClass:     00h
bDeviceProtocol:     00h
bMaxPacketSize0:     40h
idVendor:            0925h
idProduct:           1456h
bcdDevice:           0110h
iManufacturer:       1
iProduct:            2
iSerialNumber:       0
bNumConfigurations:  1
  wTotalLength:         34
  bNumInterfaces:       1
  bConfigurationValue:  1
  iConfiguration:       1
  bmAttributes:         a0h
  MaxPower:             40
    bInterfaceNumber:   0
    bAlternateSetting:  0
    bNumEndpoints:      2
    bInterfaceClass:    0
    bInterfaceSubClass: 0
    bInterfaceProtocol: 0
    iInterface:         0
      bEndpointAddress: 01h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 81h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0

Regards,
Yusuf

14 Nisan 2012 18:09 tarihinde Xiaofan Chen <xia...@gm...> yazdı:

> 2012/4/13 Yusuf Sekman <ys...@gm...>:
> > By the way, I have tried to receive data from the host. As you remember,
> I
> > use bulk.c example and I could read data coming from PC to my device.
> > But still I am not able to send data to PC. Size of EP1 FIFO Register in
> > C5515 DSP is 2bytes, so the device sends 64 byte data as an array of 2
> byte
> > data packets.
>
> Are you sure it is 2bytes? In that case, it is very small buffer.
>
> > However in bulk.c program, the data is read by 1byte for each element of
> > data array(because tmp[] and *bytes variables are defined as char).
>
> Where do you get this? BUF_SIZE is 64 BYTES in bulk.c, corresponding
> to the wMaxPacketSize of EP1 IN and EP1 OUT in our benchmark
> firmware.
>
> > Do you think that the problem occurs because of this conflict.?
> > And what do you recommend to modify bulk.c file?
> >
>
> What is the output of testlibusb-win for your device?
>
> --
> Xiaofan
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Good Morning,

Yusuf Sekman wrote
> 
> Here is the output of TestLibUsb :
> [snip]
>       bEndpointAddress: 01h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
>       bEndpointAddress: 81h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0
> [snip]
> 

If using as high speed descriptor the wMaxPacketSize for bulk must be 512
bytes. I had this also wrong declared (since my hardware has physicly only
64 bytes available ) and the device works nice on USB 2.0 ports but failed
on USB 3.0/2.0 ports. To get it working I declared as 512 in the descriptor
but send/receive only <= 64 bytes in my program.
Only in the lower speed modes 8, 16,  32 or 64 bytes are allowed.
Best regards
Ekkehard

--
View this message in context: http://libusb.6.n5.nabble.com/no-subject-tp5627034p5643040.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

2012/4/16 Yusuf Sekman <ys...@gm...>:
> Here is the output of TestLibUsb :
>
>       bEndpointAddress: 81h
>       bmAttributes:     02h
>       wMaxPacketSize:   64
>       bInterval:        0
>       bRefresh:         0
>       bSynchAddress:    0

Probably you have a firmware bug. For bulk transfer, you may
need to add a ZLP (zero length package) if the transfer length
is the multiple of the wMacPacketSize.

If that does not help, you may have other firmware bugs. Try change
wMaxPacketSize of EP1 IN (0x81) from  64 to 2 and send only 2 bytes
to the PC. This is because you mentioned that the buffer size of EP1 FIFO
Register in C5515 DSP is 2bytes and you may have bugs trying to send
64bytes. You still need to send a ZLP if the transfer size is multiple of the
wMaxPacketSize.

Reference:
http://www.microchip.com/forums/m325655-print.aspx

-- 
Xiaofan

Thread: [Libusb-win32-devel] (no subject)

libusb-win32 is a port of libusb-0.1 under Windows

libusb-win32-devel