USB CDC.

[fabim]

I and other friends of the forum, we are more than 1 years hoping to mikroe, launching the liby
"USB CDC" to mikropascal.
I wonder whether the mikroE has no intention to develop this liby /?

[BaCaRdi]

Are you speaking of a Communication Device Class library?

That would be nice to have come to think of it..

-Marc

I and other friends of the forum, we are more than 1 years hoping to mikroe, launching the liby
"USB CDC" to mikropascal.
I wonder whether the mikroE has no intention to develop this liby /?

[fabim]

Exactly.
unsuccessfully tried to carry the codes in "C" for Paschal but without any success

Fabim, Brasil

[BaCaRdi]

Really, so there is a USB CDC library in MikroC, but not in pascal. I didn't know this, very interesting. I am guessing this was a ME original lib as well, not a user comunity release.

-Marc

Exactly.
unsuccessfully tried to carry the codes in "C" for Paschal but without any success

Fabim, Brasil

[zristic]

There is no official CDC library for any mE compiler.

The reason for this is that writing a CDC library for PIC heavily depends on PC driver, i.e. windows driver. We, therefore, do not provide any of the two, because it is very difficult to write a universal one, as it is possible with HID.

However, the Internet is rich with explanations of how to make a CDC driver, all you have to do is to follow tutorials and implement them in your specific project.

[fabim]

Unfortunately ....
I am more than a year trying, without any success.

Fabim, Brasil

[fabim]

That exclusion, any possibility of providing this library? "CDC"

[BaCaRdi]

Ahh I see where you coming from, a method to the otherwise madness. :)

Man I miss good old USART!

-Marc

There is no official CDC library for any mE compiler.

The reason for this is that writing a CDC library for PIC heavily depends on PC driver, i.e. windows driver. We, therefore, do not provide any of the two, because it is very difficult to write a universal one, as it is possible with HID.

However, the Internet is rich with explanations of how to make a CDC driver, all you have to do is to follow tutorials and implement them in your specific project.

[Dany]

Hi all, I made an attempt to make a simple USB_CDC_Library.
See section "Units" on the website http://users.edpnet.be/rosseel01/DRO/PIC/index.htm.

Have fun!

[Tomy]

Thank You very much ! We wait for it very very long time

[XorXaX]

Hi all, I made an attempt to make a simple USB_CDC_Library.
See section "Units" on the website http://users.edpnet.be/rosseel01/DRO/PIC/index.htm.

Have fun!

Interesting Dany, does it work? If it does, I might attempt to translate it into mikroC.

[Dany]

Interesting Dany, does it work? If it does, I might attempt to translate it into mikroC.

Hi XorXaX,
Well yes, it works, but not with the PC communication programs i liked it to work like "HyperTerminal" or the Uart tool in the mikroElektronica's compiler's IDE. I do not know the reason for this.
Also I had to use a driver that is different from the one Microchip itself advises ("usbser.sys").
But, I am happy that I got something working.

Anyway, the code is "minimal" and more oversee-able than the Microchip C18 USB firmware (but also undoutably more error prone I think), so it should be possible to translate it in MicroC I think.

[XorXaX]

Thanks for the info, I will have a look at it when I get the time.

[vesko_hard]

Hi,

Thanks for CDC Libraly.

I compile demo project and edit VID and PID in driver ini-file.
Windows detect device and accept driver, but in device manager i see: "This device cannot start. (Code 10)".




USB_CDC_ProjectItems.ppas:

Code: Select all

UsbManufacturer : string[20] = 'Vesko_hard';
// Sets the name of the manufacturer of the USB device you are creating.

UsbProduct      : string[20] = 'CDC Dongle';
// Sets the name of the USB product you are creating.

UsbSerialNo     : string[20] = '1234';
// Sets the serial number of the product you are creating.

// -- ID numbers --
VENDOR_ID     : word = $1234;
// Identifies the vendor or manufacturer of the USB device created.
// This number is (normally) defined by the USB organisation.

PRODUCT_ID    : word = $1234;
// Identifies the product, defined by the manufacturer (You).

DEVICE_REL_NR : word = $0101;
// Identifies the device release number (in BCD!), defined by the manufacturer (You).

usbcom.inf:

Code: Select all

[usbcom_Mfg]
; DisplayName               Section           DeviceId
%usbcom_DeviceDesc%=usbcom_DDI, USB\VID_1234&PID_1234

[Dany]

I compile demo project and edit VID and PID in driver ini-file. Windows detect device and accept driver, but in device manager i see: "This device cannot start. (Code 10)".

Hi, your code changes seem to be Ok. I see that you already at serial port number 30. Is this indeed the case that there were already 29 com ports present? If not, there is something wrong with the windows comport enumeration process. I do not know if this is the cause of the problem you face however, it is possible. Did you try "troubleshoot"?
Anyway, the PC software "TestCDC.exe" is only capable of selecting comports upto number 5.