Please add to this as you find new drivers and whatnot. These are the steps I took to get Windows 7 working on my Udoo... 1. I installed Ubuntu on the 32gb eMMC. It came in handy later when I needed to access the Windows installation on the 128gb M.2 ssd. 2. Go into BIOS and enable keyboard and mouse for Windows under Other Configuration. 3. I followed the steps here to make my bootable USB thumb drive. http://www.fit-pc.com/wiki/index.php/How_to_make_Windows_7_bootable_install_USB_stick 4. Download and use this utility to add usb 3 support to the thumb drive. https://downloadcenter.intel.com/downloads/eula/25476/Windows-7-USB-3-0-Creator-Utility?httpDown=https://downloadmirror.intel.com/25476/eng/Win7-USB3.0-Creator-V3-Win7Admin.zip 5. Plug your installation thumb drive into the Udoo. 6. Start it up, push Escape repeatedly, and choose to boot from the thumb drive. 7. Windows installation will start. If you get stuck, follow this video. 8. The tricky part was that once Windows installed, I lost my keyboard access after logging into Windows but still had my mouse (this may or may not happen to you), so I booted into Ubuntu, downloaded the following files and dropped them into my Windows desktop folder... a) USB 3 - https://downloadcenter.intel.com/do...Driver-for-Intel-7-Series-C216-Chipset-Family b) Wifi - https://downloadcenter.intel.com/do...-Wireless-Software-and-Drivers-for-Windows-7- c) Graphics - https://downloadcenter.intel.com/do...phics-Driver-for-Windows-15-40-?product=91830 d) Ethernet - http://www.realtek.com/downloads/do...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false e) Audio - http://www.realtek.com/downloads/do...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false 9. Shut down and boot back into Windows. 10. Load those drivers, and you're good to setup wifi and download Windows Updates. This isn't perfect. There are still some unknowns in my device manager, but I haven't found anything that affects my regular usage of Adobe Suite, Microsoft Office, and coding tools. There is a quirk that had me sweating though. Windows could not find a driver for my WD My Passport portable drive that houses all my backup files. Finally, I plugged a USB 2 hub into the Udoo and plugged the portable drive into that, and it works. Please, please, please, post anything else you find.
Perhaps someone with Windows 10 (or Linux) installed can identify the still unknown devices so the hunt for win7 drivers can go on....
Microsoft Windows users can look at their Registry to determine the manufacturer or model of a PCI device installed in their computer. To do this follow the steps below. Through the System Information 1. Open the Windows System Information (msinfo32) tool. 2. Click Components to expand the available components on the computer. 3. Click Problem Devices and locate the PnP ID for the device you want to identify VEN_5333&DEV_8901&SUBSYS_00000000&REV_16 4. As can be seen in the above example you have lots of useful information that can be used to identify the card. In this example, the VEN aka vendor is 5333. Doing a search for this vendor on the PCI database shows that this particular PCI device is a "S3 Graphics Co. product." You can find a link to the PCI database on our motherboard links. source: https://www.computerhope.com/issues/ch000632.htm
They are all Intel, but the device ID's are not listed in that site. I'm looking them up. Device 22C1 - Intel® Serial IO Driver for Intel - Windows 8.1 driver specific Actually, it seems none of them are supported by Windows 7. I just tried an installer for another that errored out because of the platform.
Found the same unknown devices on my board and the drivers appear Win 8 specific as you said. Does this mean there is no hope of getting a fully functional Win 7 board running? Intermez
That's what I'm thinking. That's also why I have an Ubuntu install on the 32gb eMMC. If I find anything I want to tinker with on the board that Win7 doesn't support, I'll boot into Ubuntu.
Just did the same as you, Ubuntu on eMMC and Win 7 on SSD. Is there a way to "dual boot" this so that I don't have to go into BIOS every startup to select the OS I want?
Yes - I have mine set up to triple boot Ubuntu (eMMC), Android (image file on SSD) and Windows 10 (SSD). You need to go into the Grub configuration settings and specify the boot options you want. In fact if Windows was set up first then I am surprised Ubuntu did not set up dual boot by default during the Ubuntu install. In Grub you can also change things like the timeout on the boot menu and the default OS (I have mine set to be last one booted rather than a specific OS).
On my UDOO Ultra I have installed at the moment both Ubuntu 17.0.4 and Windows 7 from DVD (not USB stick). The installation of Ubuntu went smoothly as expected, while W7 was a bit tricky, as suggested above. In my case: 1) I had to disable MMC and SD from BIOS during setup to avoid weird errors about unaccessible partitions and "cannot install on this hardware". 2) The BIOS (v.102) setting for keyboard and mouse works but is quite volatile, it often resets itself at boot and has to be reenabled every time. 3) Once in W7 I installed the required drivers (see above). Many devices were not found or not working: I2C (8086:22C1 and 22C6) UART (8086:228A and 228C) SMBUS (8086:2292) DMA controllers (8086:2286 and 22C0) SD (driver failed, code 10) MMC (not even seen) 4) Then I installed a chipset driver (k1chp06us17_7.exe) found on the Lenovo site: http://pcsupport.lenovo.com/it/en/p...-ones/700-series/700-25ish/downloads/ds104851 It installed the SMBUS driver but didn't enable the other devices, only changed their names. But this was an important hint, as they were now called "Intel Celeron/Pentium"; and that suggested me to try installing a package not specific for Braswell (which doesn't exist for Windows 7). 5) And so, after some search, I found a driver package on the Intel site (PROC_IO_Win7_32_64_1.1.9.0140.zip): https://downloadcenter.intel.com/download/26660/Intel-Processor-I-O-Controller-Driver-for-Windows-7- It is for Intel Atom but installs itself correctly on the UDOO and seems to fix all the device problems, except for one GPIO controller and I2C, which are still not working. But at least MMC, SD and the COM ports are there! (I don't know yet if the serial lines really work, I will test them later)
@ Lord Arach, thank you very much for providing the instruction and all the links. You have saved everyone a great deal of time. Just one minor point to share re. step 4: 4. Download and use this utility to add usb 3 support to the thumb drive. https://downloadcenter.intel.com/downloads/eula/25476/Windows-7-USB-3-0-Creator-Utility?httpDown=https://downloadmirror.intel.com/25476/eng/Win7-USB3.0-Creator-V3-Win7Admin.zip There are 2 versions of USB 3.0 creator, from this link: https://downloadcenter.intel.com/download/25476/NUCs-Windows-7-USB-3-0-Creator-Utility Win7-USB3.0-Creator-V3.zip - for Admin systems with Windows 8.1 or Windows 10 installed Win7-USB3.0-Creator-V3-Win7Admin.zip - for Admin systems with Windows 7 installed Due to my absent-mindedness, I tried to run Win7-USB3.0-Creator-V3-Win7Admin.zip in Win. 10 to update the ISO many times without success before realizing it's the wrong version all along! Also re. installation error: Setup was unable to create a new system partition. This can be avoided by the the following UEFI setting in Udoo: Boot Menu -> Boot Type (Legacy Boot Type), Legacy Submenu -> Boot Type Order (Hard Disk 1st, USB), Hard Disk Drive (Target drive on top of list if multiple drives). On bootup, manually enter Boot Manager to boot from USB stick. Thank you to all the contributors for device driver links!
Also I have to say that the USB-COM Intel driver for Curie works very poorly in my Windows 7. While the serial console works fine in the Arduino environment (the only one, I suppose, they have tested), in TeraTerm there are long pauses between written characters; MobaXTerm shows only a blank screen; directly accessing the COM port from C, C++, C# just fails with no character sent or received. All works fine under linux instead, so I suspect some issue with the Windows driver. Can anyone check if this happens also under Windows 10? Alberto
