Main Site Documentation

Lost comms between PC and G400


Sad story: I’m working on a .NET MF app before lunch and everything seems fine: I can make changes to the app, download the code to our custom board with a G400S, run and debug the code. After lunch, I can’t talk to the board at all. When I try to download the app, VS says there are deployment errors and I should check my hardware. FEZ Config gives me this:

The PC can see the G400 in the WIndows 7 devices applet. VS2013 can see the G400 in the Project Properties. I can ping the board with FEZ Config, I’ve erased the application with FEZ config and tried to “Reboot CLR” like FEZ config says to do. FEZ Config said both operations were successful. Of course, I’ve rebooted the PC and the G400 several times.

Seems like the G400 is stuck in some mode that doesn’t allow downloads but I’m not sure how to get it back where it needs to be.

I pulled a new board from stock and got similar (but not identical) results.

Of course it is the day before a Holiday so any suggestions will be doubly appreciated.

Thanks - Gene


just reflash netmf firmware onto the board. “Firmware updater”.


In VS, select project, right click >> project properties >> .net Micro Framework Tab.
Change Transport from USB to Serial, then change back to USB.
Retry running/debugging/starting the app via VS, i.e. click the ‘Start’ button.

This has worked for us MANY-MANY times.


Seems Lunch was the issue, I’d roll back lunch and try again



Well this just gets weirder and weirder. I know about switching the project transport from USB to Emulator and back. I’ve done that many times in the past also and tried it again for this issue many times with no luck. After several tries, I was able to reload the firmware with FEZ Config. Still no luck. So, I tried a different laptop. Guess what? It worked. Twice. And now I’m back to not being able to down load programs but with new symptoms.

When I hit the green arrow in VS, the output window says it successfully deployed the assemblies to the device and then says it is starting the device deployment but all it does is iterate until it fails with this error:

Error 1 Device not found or cannot be opened - USB:SN001

The weird thing is the Device is SN05 not SN001. SN001 is the board I was using before. And the project properties show a USB connection to SN05. I’ve built, cleaned and rebuilt many times but it seems to want to deploy to a device that is not connected?

As always, any help will be greatly appreciated.


I seem to have fixed the problem, at least for now, but there still is something important I clearly don’t understand. When I reflashed the .NET MF firmware with FEZ config, I left the “friendly name” set to the default “Gadgeteer”. Previously it was SN005. In spite of multiple rebuilds, cleans, project property transport changes, reboots of anything that could be rebooted; VS didn’t change whatever it needed to change so it could download my app to a G400 with a different friendly name.

If anyone knows what you have to do in VS when the hardware friendly name changes, I’d sure like to know.

Thanks - Gene


I’m not sure I can swear this is completely correct but when VS gives an error about can’t deploy to device name “XYZ” and device “ABC” is the one that is actually connected (see details above), the only thing that has worked for me is switching the transport in project properties to “emulator”, rebuilding and then switching the transport back to “USB”. Switching the transport without rebuilding, which does fix a lot of mysterious errors, didn’t work here.