Hi!
I have been struggling to make my Spider ver1.00 work with my win10 laptop and usb3 ports.
Since my spider is a couple of years old, I needed to upgrade it before use. But that was not possible to do with my win10 pc and FEZ Config.
After a lot of struggling I managed to update the spider with an old win7 pc and FEZ Config. So far so good.
But when I try to use the spider with my win10 again, I get an error (10) in the device manager.
Since my computer only have usb3 ports, I connected my spider to a Silex (SX-3000GB, Silex Technology) USB device server. And voilĂ , it is listed without error under comports in the device manager. And itâs listed as EMX under the Universal Serial Bus devices.
But, I canât still upload the hex from vs2012, vs2013 and/or vs2015 to my spider⌠Itâs not listed in visual studio when I select usb.
You could try checking the SetupAPIDev.txt file found in the Windows\Inf folder. Error 10 can be caused by a number of errors that the driver could not handle with a more specific error code.
Look near the end of file, there are time stamps to help find when the Spiderâs USB cable was connected.
If that doesnât provide you with some clue as to the problem, then post that portion of the log file to this form, we may be able to help with this extra detail of the issue.
Not sure if this is of any help but my Windows 10 will connect/deploy/debug using Visual Studio 2012 and 2013 Pro.
I have tried a Spider and Raptor using USB 2, USB 3 and USB 3 connected through a USB 2 Hub.
Both boards work event though windows 10 tells me that it may not work.
In fact I have been using a USB 3 port that was using the WinUSB driver. The Winusb driver was installed because( I assume) that was because I was using winusb on Windows 8.1 before the Windows 10 update.
With winusb the device manager showed it was using Universal Serial Bus Devices.
As a test I removed the driver WINUSB from my system (Not easy to do) and then booted my pc with the Spider attached to a USB 3 port.
At first no driver was installed but after another couple of tries Windows 10 installed the Debuggable .Net Micro Framework Device.
With the new driver my Spider and Raptor still connect/deploy/debug using Visual Studio 2012 and 2013 Pro on a USB 2 or USB 3 port.
Check if you are using the
GHI .NET Micro Framework USB Debugging Interface
What version of the GHI Electronics SDK do you have installed?
Was Windows 7 previously on this system before the upgrade to Windows 10?
The SetupApiDev.txt log shows that the INBOX usbser.sys driver failed to start as reported in Device Manger, didnât see any other details. Since this is the INBOX driver, it is very unlikely to be the problem. However there may be missing entries in the registry or USB Descriptors in the Spider USB client software.
The post from willgeorge shows his system is using the WinUSB.SYS driver, so at some point in the SDK release cycle there was a switch to WinUSB.SYS. I didnât realize the CDC mode was supported.
I donât have access to a Windows 10 system currently, but am curious to see what it is using.
Starting with Windows 8 it is possible to define USB Descriptors in the client to load the INBOX WinUSB.SYS driver with out an INF file which means there is also no need to digitally sign the INF as done previously.
@ PHITEK - Hi, Iâm using the GHI Electronics NETMF SDK 2015 R1 Pre-Release 4.
The computer was delivered with win8, and I have just recently upgraded it to win10.
I have also tried connecting the spider to an older computer, the computer was running win7 on delivery but has been upgraded to win8.1 and now win10. The FEZ Config tool on that computer recognizes the spider.
@ albertvi - That last screen shot, doesnât show a problem with the EMX device, I would have thought there would be a yellow triangle on the EMX node.
Itâs like you have re-installed the GHI Electronics SDK, because the SetupApiDev log clearly shows the usbser.sys driver was loaded.
I donât have a spider board, so I not sure where the problem is.
Your image shows it is using winusb just as I had before changing to the Debuggable .Net Micro Framework Device driver. My PC was working with winusb. And now it is using the Debuggable .Net Micro Framework Device.
I should mention that I am using:
Using Loader (TinyBooter)
4.3.7.7
Using Firmware (TinyCLR)
4.3.7.10
Using Visual Studio 2013 Pro
*
GHI Electronics NETMF SDK 2015 R1 Pre-Release 4
NETMF and Gadgeteer Package 2014 R5
netmf-v4.3.2-SDK-QFE2-RTM
*
Using FEZ Spider
Nothing special about my PC.
Older HP 64 bit that originally had Windows 8, updated to Windows 8 Pro then Windows 10.
Winusb was being used when the PC was running Windows 8 and I have always been using the USB 3 port.
I have had zero problems using GHI Electronics NETMF SDK 2015 R1 Pre-Release 4
(At least for what I do). I would not update to this version at this time because you would need to update your Spider firmware.
If it were me I would perform all the steps stated in:
EVEN IF YOU HAVE DONE SO BEFORE.
Do âŚUninstall any currently installed NETMF SDKs.
REBOOT your PC and then install everything listed
Step 2
Download Microsoft .NET Micro Framework 4.3 (QFE2) and unzip the file. Open the fileâs folder and⌠Install MicroFrameworkSDK.MSI Install netmfvs2013.vsix
Step 3 and Step 4
I have no other suggestions at this time except asking if FEXConfig.exe can find your Spider.
Your picture that shows the âEMXâ device in device manager is operating correctly, in normal mode. At that point, you should be able to check the firmware version and loader version using Fez Config, and update them as needed.
So please change to SERIAL instead of USB in the dropdown, and then back to USB. Does that then populate a device name in the device list to the right ? (Often I see this not being detected straight away and a USB refresh will see it on the second scan)
@ Brett - No that donât change anything. Just for fun, I hooked up an Netduino Plus2 and installed the Netduino SDK v4.3.2.1. And as you can see from the picture that worked. It also worked in vs2012.
Hi!
Itâs now possible to use my spider with my old win10 pc. But my new win10 pc is still not recognizing the spider in vs or with Fez Config.
There is a little difference when I look at the EMX in the regedit. The ConfigFlags holds the value 0x00000020 at the working pc, but 0x00000000 at the faulty one. Do any of you have some info regarding those settings?
Nothing useful to help solve your problem but I thought you may like to know what I found in my Windows 10 registry.
See images:
I was using winusb with success on Windows 10 so the info here should be valid. Data relates to EMX.
ConfigFlags 0x00000000 and 0x00000020 were both valid working USB Ports.
To me it appears that the ConfigFlags changes between what Port and Hub is in use. (No expert on this statement)
Install MicroFrameworkSDK.MSI