Are there any known issues with the GHI Bootloader interface when using Windows 10 with the latest updates?
I am using Windows 10 Pro with all (known to me) updates.
I needed to update a older Spider to 4.3.8.1 but the loader does not start.
I have, in the past, used the Bootloader interface but that was before the several Windows 10 updates.
GHI Bootloader interface (COM6)
Removed in order listed.
Microsoft .NET Micro Framework 4.3 (QFE2)
Microsoft .NET Gadgeteer Core
GHI Electronics NETMF SDK 2016 R1
Reboot and install in order listed.
Microsoft .NET Micro Framework 4.3 (QFE2)
Microsoft .NET Gadgeteer Core
GHI Electronics NETMF SDK 2016 R1
Running Windows 10 Pro
All current updates are installed.
Error received in Device Manager:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
Events in order:
Device USB\VID_1B9F&PID_0104\6&ab382be&0&1 requires further installation.
Driver Management has concluded the process to add Service usbser
for Device Instance ID USB\VID_1B9F&PID_0104\6&AB382BE&0&1 with the following status: 0.
Driver Management concluded the process to install driver
ghi_bootloader_interface.inf_amd64_4c92248765c12d8c
\ghi_bootloader_interface.inf for Device Instance ID USB
\VID_1B9F&PID_0104\6&AB382BE&0&1 with the following status: 0x0.
@ willgeorge - It’s likely the same issue with the EMX bootloader being unable to run on Windows 8+. We haven’t been able to track it down yet and the only work around when it occurs is to use Windows 7, as @ Greg Norris suggested.
@ willgeorge - The issue only happens on some computers, so it’s like a combination of the PC hardware, the EMX, and Windows 8+. You can actually also try to update over serial on Windows 10.
@ willgeorge - To update using serial mode, you’ll want to move all four of the DIP switches, not just the first three. Then connect a USB to serial module to socket 9 (COM 1). You can use FEZ Config to deploy the loader and firmware or TeraTerm to deploy the loader.