There are aways problem to updata the Firmware to my “FEZ Spider”.
After installing the latest “Microsoft .NET Micro Framework 4.1 SDK” and “GHI NETMF v4.1 and .NET Gadgeteer Package” I updata the “FEZ Spider”.
After “step 1” and “Step 2” in “FEZ Spider Mainboard Updater”, I have got always the Window “Cannot connect to the device! Follow steps 1 to 2”.(picture 1)
I have also checked the Hardware Manager, I find that USB driver got problem (picture 2), but I don’t know how to slove it. I have tried many times the USB drivers install and uninstall, but the “FEZ Spider” can’t be updated.
Hi, are you using a usb hub?
If so, try connecting directly to computer without usb hub.
I had problems, not in firmware upgrade, but sometimes after a certain period.
Sorry to hear you have a problem on your first post.
The best piece of information you can give us is the screen shot of your device manager like was shown above. If your problem is the same, with the driver showing there is a problem, then Gus’ early post about installing the driver manually will probably be the answer you need.
I tried different ways to install a usb driver for the modul under Win 7. But i wasn’t able to install. I tried the 4.2 package also.
At least i use an old Win Xp Computer, which failsas well with the updater application. But the bootloader interface drive was possible to install and the second attempt run successfully. With the updated firmware the modul works fine also with the Win 7 computer.
Now i see that the modul displays a boot screen and i get devices in Win 7. I assume that the loader on the module was corrupt.
That for your support.
H.H.
P.S. But how to solve such a problem only with Win7 ?
I tried installing the drivers several different ways, and included turning off the UAC to see if that would help any. In USB debug mode it seems to recognize it fine, however when switching the FEZ Spider to Loader the machine indicates that a suitable driver cannot be found, and labels it as “Unknown Device” and stops trying. I have also tried updating it manually to the drivers folder, but it didn’t like what it found in there either and said the “Unknown Device” driver was best suited for the device. Like the previous posters, if I attempt to use the updater without the device recognized, the updater software simply says it cannot find the device. I too am using Windows 7 x64.
While USB specifications say ports should provide 500mA, we rarely see a port that can actually provide 500mA. We always recommend the use of powered hubs or a power pack instead of relying on the USB power. Use a powered hub from a known brand, not a cheap hub. If your device has the option of using a power pack (for example the USB Client DP Module) then you can use a power pack instead. 9V 1A is typically recommended but check the bottom of the circuit board for printed voltage range. All power connectors on GHI products are 2.1mm with positive on the inside and negative on the outer ring.
Not using a powered hub or power pack can cause:
[ul]Unexplained behavior
Device does not function
Device functions intermittently
Device functions but network fails
Device functions but SD card fails
Device functions but firmware update fails[/ul]
(Generated by QuickReply)
OK, so here’s the deal. You haven’t got a driver loaded, you need to get that loaded before the updater will be able to see the device. Your problem description is great in that it clearly articluates where to focus.
Can you take some screenshots and post here? Please take a “before” one of the device manager, one of the directory structure you’ve pointed to when trying to identify the driver, one of any errors you get, and one of the device manager “after”.
I was kinda leaning toward driver being missing myself, but I had also planned on going over to BestBuy and picking up a powered USB hub as Gus had suggested later today to see if that was the problem. Given that in normal mode the driver was found, and I could use Visual Studio with it I wasn’t expecting much, but he’s got a lot more experience here and I figured even if it didn’t work I’d just have a hub around if I need it.
I took a couple screenshots for you as you’d requested, including some you didn’t in case the Windows version was the problem. The folders screenshot I tried using all the folders underneath the two I took a screenshot of with no luck. You can clearly see the Unknown device listed in the Loader.png in the USB section.
Thanks again for the help!
Edit: i wanted to add descriptions of which screenshots are where below:
The screenshot with the DIP switches on the mainboard set to Default.
The screenshot with the DIP switches on the mainboard set to Loader.
This is a screenshot of my Windows basic information, and computer model information.
This screenshot is the folders I had attempted to use when manually choosing a driver.
This is what the driver install dialog said when I tried to update the driver. (I am still an admin and the UAC is turned off on the machine right now)
This screenshot is the ‘before’ shot you requested of the device manager, the device is not connected right now.
While this maybe very unlikely i can confirm that it is unlikely but possible that USB3.0 is a problem since I do not remember our team saying anything about 3.0 testing.
Mmm, yep, I’ve got nothing at this point. Normally when a device is “just” missing the driver it will appear as a serial port device not as an “unknown” USB device. As we are seeing a few USB3 issues, is there any chance you have an older PC that you can try the update process on as well? I don’t know if moving the connection away from a USB3 port (if you can) would also be of benefit, but if you can try that it’d be great as well !
I just picked up a powered USB 2.0 hub from BestBuy, should be home in a while to test it. I may have a machine I can test with that only has 2.0 ports, not sure if it’ll work being my company laptop. My old computer’s mobo died on me. Will update when I get home.
Well, I got home with the USB 2.0 hub as Gus had suggested and initially it did not work. I’ve attached a screenshot of the device manager when this was happening. I moved the port which it was connected to closer to the power source on the hub and it did start working at that point. I also tried plugging the device directly into the laptop once it had been successfully installed on the machine, and it went back to not being able to find the drivers.
Now just to confirm that it wasn’t a power problem with what my laptop was supplying, I disconnected the power cable that was provided so the hub was only being powered through the USB port, disconnected it, and reconnected it. Even with only using USB power, the device was recognized and successfully assigned a COM port. Attached is a screenshot.
I’d imagine that it’s got something to do with USB 3.0 ports on my laptop. Hopefully this helps narrow down where the problem might be for anyone else that has the same issue as I did.
Edit: I just wanted to add a thank you to everyone that gave me suggestions what to look at and those that tried to help me fix it. I do appreciate not having a very expensive (albeit cool) looking paperweight on my desk.