View previous topic :: View next topic |
Author |
Message |
jaikumar
Joined: 15 Dec 2006 Posts: 109
|
WINUSB - solution for endpoint size problem |
Posted: Fri Apr 06, 2012 7:35 am |
|
|
Hi all,
I am trying to communicate using bulk transfer with winusb on PC side.
It installs fine and runs ok, Only when the bulk transfer endpoint is set to 64 bytes. If i set to 128 the driver giver error 10 could not start.
Is 64 bytes is the max that winusb can take or should we alter some other code in the ccs source.
IT WORKS FINE IN WINDOWS XP.
IT Creates problem in Windows xp if endpoint size set to 128 bytes.
Can any one please shed some light on this issue.
Regards,
Jai. |
|
![](templates/subSilver/images/spacer.gif) |
asmboy
Joined: 20 Nov 2007 Posts: 2128 Location: albany ny
|
|
Posted: Fri Apr 06, 2012 1:57 pm |
|
|
Have you tried using MCHPUSB.sys
on the Win-Doze / PC host ???
I think this is what Microchip suggests.
After one (MISERABLE) early attempt to at using the 18F integrated USB pics
I now shun all PIC direct USB functions - as being wasteful and kloogy, vastly preferring to use virtual com port hardware from FTDI , with the FT232R chip coming instantly to mind. |
|
![](templates/subSilver/images/spacer.gif) |
temtronic
Joined: 01 Jul 2010 Posts: 9170 Location: Greensville,Ontario
|
|
Posted: Fri Apr 06, 2012 3:27 pm |
|
|
yup, I gotta second what asmboy says! Offloading the USB function to an external device also frees up 1/3 of the code space of a 4550 that had the USB drivers in it....sigh...Useless Serial Bus....give me a REAL comport anyday !! |
|
![](templates/subSilver/images/spacer.gif) |
|