When I do NOT add the USB Client DP on the design surface
A first chance exception of type ‘System.NotSupportedException’ occurred in Microsoft.SPOT.IO.dll
The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 4 must be specified for socket of type D
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 5 must be specified for socket of type D
Using mainboard GHI Electronics FEZCerberus version 1.1
Program Started
The thread ‘’ (0x3) has exited with code 0 (0x0).
When I add the USB CLient DP
A first chance exception of type ‘System.NotSupportedException’ occurred in Microsoft.SPOT.IO.dll
The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 4 must be specified for socket of type D
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 5 must be specified for socket of type D
Using mainboard GHI Electronics FEZCerberus version 1.1
A first chance exception of type ‘Gadgeteer.Socket.PinMissingException’ occurred in Gadgeteer.dll
An unhandled exception of type ‘Gadgeteer.Socket.PinMissingException’ occurred in Gadgeteer.dll
Additional information:
Pin 4 on socket 8 is not connected to a valid CPU pin.
There was a problem with the FEZCerberus driver. It didn’t assign the pins for that socket properly. This has been fixed and will be out in the next release. Is this something that you needed to work asap?
To determine the firmware version you are running, in MFDeploy, Select USB from the device dropdown. you should see FEZ Cerberus_Gadgeteer and Ping. It should say TinyCLR in response. If it does say TinyCLR in response, go to target and then click on device capabilities and a list of details should appear in the box at the bottom of MFDeploy. In this list of details there should be this line: SolutionReleaseInfo.solutionVersion: X.X.X.X The X.X.X.X will be the current version of your firmware. If you cannot ping the board successfully, you should follow the steps to update the board to the most recent firmware at the wiki page you linked to. Note anything that was on the board will be erased if you update the board.
OK i cant ping the cerberus (but shown under devices).
Then i followed the steps in the wiki with TinyBooter.
All OK i can ping the Cerberus (response “TinyBooter”).
If i want to upload the image files via MFDeploy the Error in the Screenshot is shown. I instaled the GHI SDK package today.
When im trying to deploy in visual studio theres a timeout.
After downloading firmware DFU firmware to cerberus, the green config led is on.
What is the directory of the of the Firmware file that you are trying to upload? Can you try again but separate the windows so I can see them? Also note that TinyBooter is not capable of having programs deployed to it as TinyBooter is only a booting program that cannot run or interface .NetMF programs. TinyBooter is sort of like a Windows Safe Mode with limited drivers loaded.
Those are the correct files. Try to deploy the images again, and if just deploying them gives same error, try the complete erase/reload instructions again. As for the device capabilities, TinyBooter cannot display them, however, when you get the firmware (image files) up and running, at the top of the menu bar, there is the menu “Target”. Click on that menu option and then click on device capabilities.
You should have the most up to date MFDeploy in the NetMF SDK program files located here: C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Tools. Just click on the MFDeploy icon and you should be able to deploy the image. But first one last time, erase then reload the TinyBooter to make sure the older version of MFDeploy did not corrupt any of the data.
i tested with pluged usb dp in designer. debugger stopped:
Pin 4 on socket 8 is not connected to a valid CPU pin.
i tested without pluged usb dp. i can print “Program Started”:
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 4 must be specified for socket of type D
Warning: socket 8 is not compliant with Gadgeteer : Cpu pin 5 must be specified for socket of type D
Using mainboard GHI Electronics FEZCerberus version 1.1
Program Started
