Hi,
We are using Open-Q 820(APQ8096) carrier board with the latest BSP 2.0 (Android MM). We had installed the Hexagon SDK 3.0 application and its USB driver which is available in the installation path of HexagoN SDK 3.0.
As a result, after installation if i connect OPEN-Q 820 board, it must recognized as
1 . Quacomm USB Composite Device XXXX under Universal Serial Bus controllers in device manager
2. Quacomm 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.0(Qualcomm\Hexagon_SDK\3.0\tools\debug\usb) and tried to replace the standard USB Composite Device to Qualcomm based Serial port but it didnt work as expected. The VID_05C6&PID_9039 doesnt seem to have match in the list of com port in Qualcomm.
In order to validate sensors in OPEN-Q 820 Device, it must be recognized as same as mentioned above.
I am running windows 7 (64 bit)PC with full USB access.
OPEN-Q 820 Device instance path is mentioned below
USB\VID_05C6&PID_9039&MI_01\6&2C36F609&0&0001
Can anyone support us in this regard.
Did you get any solution?
I have same problem.
BTW, before upgrading BSP 2.0, I could get 'Qualcomm USB Composite Device 901D' and mini-dm worked on same PC (Windows 10).
looks like usb drivers for BSP 2.0 are different , can you try installing usb drivers from USB folder in 8096_Open-Q_820_Android_BSP-M-2.0.zip (zip file that you got from intrinsyc). Please refer to the section 7.2.4 in the BSP programming guide
Can any one give an update on USB drive for Win7 64bit?
I choiced the driver folder from \8096_Open-Q_820_Android_BSP-M-2.0\usb_driver\i386 for
window device driver. which shows as "Android?" after update, looks like still not work.
Any suggestions?
thanks.
Hi all,
is there anyone who solved this problem?
I got into the same situation TT
Hi all,
is there anyone who solved this problem?
I got into the same situation TT
Hi all,
is there anyone who solved this problem?
I got into the same situation TT
I spoke with Intrinsyc support regarding this issue, suggestions I got from them are :
-> From device manager try updating drivers by pointing to USB folder in 8096_Open-Q_820_Android_BSP-M-2.0.zip
-> If you still see the issue try doing a factory reset from the settings menu, this should reset the product id on the dev kit.