OMAP 4430 DRIVER

0 views

Skip to first unread message

Lutero Chaloux

unread,

Jun 28, 2024, 5:24:42 PM6/28/24

to profbawtidim

Plugging in Glass via USB allows me to browse files and such. But even with debug mode ON I can't get it to show up with the adb devices command. Also my Windows system said it couldn't find an OMAP4430 device driver (which is the Glass SoC I believe).

Add this magical snippet to both the [Google.NTamd64] and [Google.NTx86] section, which includes the correct PID and VID for Google Glass (Updated May 2014 after helping a student at Boston AnDevCon):

OMAP 4430 DRIVER

Download File ⇔ https://www.google.com/url?hl=en&q=https://urloso.com/2yLAUu&source=gmail&ust=1719696278782000&usg=AOvVaw0MhgmUOG10dgc82fiDzcMR

[Update August 2013 - In windows you can find the values for the above by going into Device Manager, right clicking your device > Properties > Details Tab > Change Dropdown to Hardware Ids. Once you have them make sure they match what you put into your inf file, for a developer I helped recently we had to comment out the top two lines above and just use the last two lines]

3 - Go into Device Manager and find the yellow warning icon for Glass, right click it and select Update Driver Software, choose select from computer and enter in the path in step #1 (just the parent folder of android_winusb.inf). My computer gave an anti-virus warning that I dismissed, and shortly after I was able to use Droid AT Screen to mirror my Glass display onto my windows PC, which is great for presentations.

The solution I found was to uninstall the Android Composite ADB Interface under Android Device within the Windows Device Manager. DO NOT CHECK the box that says delete the device driver software or you'll need to reload that again also. Then I removed the USB cable from the computer. Reconnected again and all was well. You might need a reboot before reconnecting the cable but I didn't.

One clue to this was that when you connect via USB normally you get the popup asking what you want to do, import pictures, open windows explorer etc. I was not getting this which was my clue to something being wrong.

One interesting piece was that I did have this working previously on the exact same computer. Initially I thought this was down to something related to the XE12 update, rather than a magical mystery of Windows 7 Pro 64but USB drivers.

So when I am connecting the USB cable from Board(Development) to Host(Desktop) then it is showing the device details and all but when we are checking it into device manager its showing that driver is not installed for that.

I don't have much information about what configuration your device-host are using, or if you are using Android or one of the OSes mentioned in omapedia.org, it is not specified in your post, but, you could try next link information, it has some links to some drivers to try.

in one of the other possible cases where you were developing a WinCE board and it is not a standard device configuration you will need to create your own driver to support your device, try to check what values are stored in OMAP USB configuration for vendor and product IDs, I am not so sure but USN RNDIS should provide some functions to set these values when initializing the device and this must match with the values used in the drivers you design to be used by host PC, in case they are not for a standard device.