Riotboard not recognized in Device Manager

could you plz share a screenshot, so that we can look into the issue .

basically what happens it may show a yellow (for unrecognised device) or red (for devices disabled) in windows.

so which one is showing for you ??

What Windows Version are you using?

The Driver needed isn´t a driver as in you install or download files.

It´s a Service that just has an inf as configuration.

Anything from XP and upwards should have this integrated.

It´s recognized as "HID conform, from producer defined Device"

If your system can´t find it on its own try this:

Double Click on Unknown Device

Install Driver

Search On Computer

Select from List

Uncheck Show Only Compatible Hardware

Get in the list to Standard System Devices

Search for "HID conform, from producer defined Device" or similar.

Problem is when installing the Android Image you´ll need another driver that installs when it comes to that point.

It´s recognized as a Removable Device like a Flash Drive. So if that doesn´t work either MFGTool will stop when it tries to copy the files.

I use a windows XP and the board just works fine.

sometimes i get a yellow sign with some USB Dongles, but replugging them works good, if not then search internet for drivers and it fixes that.

Problem is when installing the Android Image you´ll need another driver that installs when it comes to that point.

mostly i have flashed linux using MFGTools , so may be android may have its own challenges while flashing.

can you plz  share at which stage of flashing we need what drivers so that we can recommend that to customers.

It´s recognized as a Removable Device like a Flash Drive. So if that doesn´t work either MFGTool will stop when it tries to copy the files.

If the MFGtool shows a HID Compliant device it proceeds with write most of the time.

in general most USB devices are recognised by windows.

can you try the steps Otto mentioned above and let us know if that solves the issue.

can you plz  share at which stage of flashing we need what drivers so that we can recommend that to customers.

As far as i can tell all drivers needed are integrated in Windows XP and onwards.

I´m using Windows 8.1 by the way.

MFGTool uses two stages.

In the first stage it uses bootstrap to put the bootloader on the board. U-Boot in this case.

That´s when when the HID Driver is needed.

On second stage it "Jumps to os". So I think it´s booting up u-boot. That´s when the Driver for the removable device is needed.

I had problems at this stage because the driver wasn´t installed fast enough. Windows 7/8 is sometimes a bit slow with this because it tries to search online for newer drivers.

And even when that´s deactivated it takes sometimes a bit long.

But on the second run the driver was already installed and it worked without problems.

in general most USB devices are recognised by windows

The Problem here is that Windows, the more and more devices are connected to it, get´s more and more unstable in recognizing the right driver to install.

That´s because Windows doesn´t remove drivers when a device is removed. It only deactivates it.

It makes sense from time to time to remove not used drivers. Just to prevent this problem.

But deactivated drivers aren´t shown in the Device Manager.

To see them you´d have to set an environment variable in Windows with the name "devmgr_show_nonpresent_devices" and the value 1.

Then when you activate "Show non present devices" in the devices Manager, realy all installed drivers are shown. Unused drivers are then half transparent shown.

And you´ll be shocked how many deactivated unused drivers you have.

Even for a device while it´s in use there are sometimes 5 or more drivers installed additionally but not used.

thanks otto for sharing your experience, ppl having similar problem will get some help from the detailed explanation.

And you´ll be shocked how many deactivated unused drivers you have.

Even for a device while it´s in use there are sometimes 5 or more drivers installed additionally but not used.

bcoz of the multiple drivers, when a new device is plugged may be all those corresponding to the PID/VID combo trying to bind the device and sometimes all of them fail. and the device becomes unrecognised.

as you mentioned on second run it mostly gets going,  in worst case may be the machine needs a restart to remove unused drivers.

DLL version:  2.2.3

Saturday,  June 07, 2014 13:12:00  Start new logging

ModuleID[2] LevelID[1]:  Parse ucl script failed, error code:  21

You have to rename the file ucl2.txt to ucl2.xml in the folder "Profiles\MX6DL Linux Update\OS Firmware".

This is also written in the description.

the step mentioned above will definitely fix the ucl parse error .

more info:

MFGTools will be able to point to the flash location correctly after renaming the file to ucl2.xml.

the "ucl2.xml" also contains the instructions on How-to to erase eMMC (NAND) and install firmware (linux/android).

the cfg.ini file specifies to which memory the MFGTool should flash firmware to.

the below line specifices the flash memory to be eMMC (NAND).

name = i.MX6SOLO-ubuntu-RIOT-eMMC