M1K not recognized in Windows 7

Our customers are using the M1K board and are unable to install the Pixel Pulse software on the Windows 7 OS. The device is not getting recognized or the USB drivers do not install on Windows 7 OS. The previous threads on this forum have not entirely addressed the exact solution of this problem.

Kindly let me know if we have a different USB driver to be installed on Windows 7. If not then were to download the USB driver and what are the steps involved to install the same. I have tried to install the latest version of Pixel Pulse software 

  • 0
    •  Analog Employees 
    on Sep 5, 2018 2:23 PM over 2 years ago


    The latest Pixelpulse release: github.com/.../v1.0.4 has an updated driver which should have priority and replace the wrong driver that Windows automatically assigns to the M1K board.
    The behaviour we experienced was the following: the M1K board in programming mode is plugged in and Windows automatically maps it to a wrong driver (usually shows up in the Device Manager as BOSSA COM PORT). The installation of Pixelpulse will also install the ADALM1000 WinUSB driver, but it does not have priority over the BOSSA driver. At this point, the right driver can be used if you follow the steps described here: wiki.analog.com/.../firmware-upgrade in the troubleshooting section.

    However, using the latest release, the wrong driver should be replaced by ADALM1000 WinUSB driver (or ADALM1000 SAM-BA WinUSB driver if the board is in programming mode) when Pixelpulse is installed.

    Please let me know if you encountered any issues after trying this version.


  • Hi Alexandra,

    I'm not sure if this problem is really solved. My situation:

    1. Installation of PixelPulse Version 1.0.4 (Sep. 5th) to a fresh Win7 installation. ADALM1000 not yet plugged in.

    2. Installation completes with positive message "Ready to use"

    3. ADALM1000 plugged in -> error message

    4. Check with Win7 device manager

     - ADALM shows up as "other device", not at USB nor COM

     - I tried to install the driver manually from the PixelPulse subdirectory

      -> Error message: "installation class not existant or invalid", installation error: E0000206

    5. If I uninstall everything and re-install with ADALM already plugged in, the same result.

    So, am I doing something wrong or is there still a problem with the Win7 setup ?

    Thanks for information & regards


  • 0
    •  Analog Employees 
    on Sep 7, 2018 8:09 AM over 2 years ago in reply to alphazed


    Could you post the content of the log file? C:\Windows\INF\setupapi.dev.log ?


  • My log file looks similar to this posting from June 2018:


    My version (only relevant "!!! message"):

        dvi:      {Installing Class}

         inf:           Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\m1k-winusb.inf_x86_neutral_b87c4281d7e5329c\m1k-winusb.inf' ([strings])
         dvi:           Installing device class: 'USBDevice' {88BAE032-5A81-49f0-BC3D-A4FF138216D6}.
    !!!  dvi:           Could not locate section [ClassInstall32].
    !!!  dvi:           Class: {88BAE032-5A81-49f0-BC3D-A4FF138216D6}. Install failed.
    !!!  dvi:           Error 0xe0000101: The required section was not found in the INF.

    ...rest omited...

    When I look at older postings, similar problems seem to exist since May 2017. And the comment from on May 16, 2017 5:29 AM was clearly articulated.

    So, looking forward to a quick and definitve solution, that also works for the ALICE software :-)


  • 0
    •  Analog Employees 
    on Sep 10, 2018 12:01 PM over 2 years ago in reply to alphazed

    Just so there isn't any confusion with regard to ALICE and the Windows installer. The ALICE Windows installer does not include the USB drivers. These must be installed before hand through either installing Libsmu with UBS driver option selected or installing Pixelpilse2 with UBS driver option selected .

    This also applies to running ALICE from source code, or any Python source code.