Qualcomm USB Driver not recognised for OpenQ 820 (Snapdragon 820) platform after installation - usb-drive

I am using Open-Q 820(APQ8096) carrier board. I have installed the Hexagon SDK 3.2 application and its USB driver which is available in the installation path of Hexagon SDK 3.2.
As a result, after installation if I connect OPEN-Q 820 board, it must recognized as
Qualcomm USB Composite Device XXXX under Universal Serial Bus controllers in device manager
Qualcomm HS-USB Diagnostics xxxx (comx) under Ports in device manager
But here there is no Qualcomm based usb recognised and instead only a standard USB Composite Device was getting listed below the Universal Serail Bus controllers section of the device manager.
To solve this we had followed the readme file which is present in the installation path of Hexagon SDK 3.2 (Qualcomm\Hexagon_SDK\3.2\tools\debug\usb) and tried to replace the standard USB Composite Device to Qualcomm based Serial port but it didn't work as expected. The VID_05C6&PID_9039 doesn't seem to have match in the list of com port in Qualcomm.
I am running windows 10 (64 bit) PC with full USB access.
OPEN-Q 820 Device instance path is mentioned below
USB\VID_0BDA&PID_57DE&REV_00147
USB\VID_0BDA&PID_57DE
Thank you

Related

Include my USB device driver in Windows Update?

How would an OEM go about getting their USB device driver added to Windows Update, so that it will be downloaded and installed automatically when the device is connected to the PC? In our case, if it matters, it will be a custom USB device class, and the driver will wrap WinUSB.
Is it possible to do this for Windows 7, Windows 8, and Windows 10? 32 and 64-bit.
What keywords (for searching) and concepts should I be aware of?
The question is misguided. The interface to WinUSB lives in userspace - not kernel space - so that DLL will be a library that lives in userspace; it won't be a driver.
The device will report via its device descriptors to Windows that it can use the WinUSB driver, so Windows won't look for its wrapper.

USB OTG on Project Tango

Does anyone know if the Project Tango tablet supports USB OTG? Or alternatively if the USB 3.0 port on the dock can act as an OTG hub? Online it only states that these ports are for charging so I am unsure if OTG functionality is also included. It would certainly increase the usefulness of the Tango's tracking capabilities if it was also able to interface with other devices.
Tango device supports "USB 3.0 host via dock connector". It means that it is possible to connect external device USB, but setup requires additional source of power.
Please refer official web site:
https://www.google.com/atap/project-tango/hardware/index.html
The Project Tango tablet support USB OTG, you could interface to other devices.
I'm checking the Tango tablet with an app named "USB OTG Checker". It says that the USB OTG API is loaded, and I can browse a USB memory drive attached to the dock's USB 3.0 port.
The USB OTG Checker says that the Tango tablet fails the check for USB OTG Signal, but I think this is because I'm not attaching a true external data source, like a USB Hard Drive.

RNDIS driver setup missing win 7 64 bit

Hi I have been trying to connect a few boards to my computer. These boards depend on RNDIS driver to get into concole. So if I connect a board for the first time my Win7 Laptop properly detects it as a RNDIS ethernet adapter or device. But when I plug in the boards second time it just comes up as a unknown device in USB section of device manager. From searching the web I assume that something is RNDIS to fail. So I try to install the driver manually using http://www.sharpduino.com/en/articles/article/19 where it suggest to manually install a driver under Network Adapters > Microsoft Corporation > RNDIS. But here is the problem the entire Microsoft corporation folder in the driver setup is missing. I am getting no help on the web on why this is so.
And this problem is not just on one board but on others as well. Boards used so far Intel Edison, Arietta G25.

Use of xHCI driver and USB_STORAGE driver

I'm currently learning driver programming and am at very nascent stage. I'm unable to get the difference of use of xHCI, EHCI, or OHCI drivers and usb_storage.
When I plug my USB device (pen drive) and observe dmesg output, it says that my device is using the ehci driver, but my device stops working when I rmmod usb_storage.
There are many drivers for different kind of USB devices let it be mouse, keyboard, camera, etc.
As of now, I assume that the xHCI driver is for USB host and the other driver is for the device we connect to our USB host. Am I correct? If not, what is the explanation?
*HCI are specifications of USB hosts:
xHCI - for USB 3.0
EHCI - for USB 2.0
OHCI and UHCI - for USB 1.x
usb_storage is a upper level driver working on the USB host side, and it is responsible for communication only with USB storage devices, not keyboard, mouse, etc.
The USB is maintained in form of a stack and *hci drivers are the lowest level in that stack. usb-storage and other drivers are located on a higher level of this stack.

Using Motorola Symbol barcode scanner in Simple COM Port Emulation on Mac OS X

I have a Motorola Symbol DS6708 barcode scanner. I need to scan QR codes that are in binary. So, the default HID Keyboard Emulation mode will not work for me. I want to put the device into a serial device mode. I can put it into Simple COM Port Emulation mode, and the device appears on the USB bus. However, it doesn't appear as a serial device, and there's nothing in /dev that relates to the device.
The documentation refers to a driver for COM mode for Windows, but I don't see any drivers for Mac. Any tips to get this working?
Check around and see if you can figure it who manufactures the USB->serial chip in the device. If it is Prolific, there are open source Prolific drivers available for the Mac. If the bridge is TI, then see if you can suss out the model of the chip, since there is example source for drivers (compilable) available thought the TI developer program/portal.

Resources