Thanks Tim.
Issue was with the USB device 's clock configuration, causing it to lose
synchronization, when it see's 0x.
Thanks,
Hari
--
View this message in context:
http://libusbx.1081486.n5.nabble.com/sending-data-containig-0x-results-in-crc-error-tp2283p2341.html
Sent from the l
hgs16 wrote:
> I am using libusbx-1.0.17-win to communicate with our usb device(based on
> stm32). It runs stm32 usb library adapted to behave as winusb device.
>
> When sending data which contains 0x (say 0x, which is of 4 bytes
> in length), usb monitor software says USBD_STATUS_CRC
Hi All,
I am using libusbx-1.0.17-win to communicate with our usb device(based on
stm32). It runs stm32 usb library adapted to behave as winusb device.
When sending data which contains 0x (say 0x, which is of 4 bytes
in length), usb monitor software says USBD_STATUS_CRC (0xc001).
