I must admit this is all rather new to me and I am by no means a hardware guy, but rather a C# WIndows developer. I thought it would neat to code on the micro framework.
I just purchased and received a Spider Starter Kit. I am running on Win 8 x64 (desktop) with USB 2.0.
I installed MIrosoft Visual C# Express 2010
I installed Microsoft .NET Micro Framework 4.2 QFE2 SDK
I installed all components of the GHI NETMF v4.2 and .NET Gadgeteer Package (except legacy USB)
the switches are set to off, on, on, on (Loader)
When I plug in my spider when it instructs me to do so to update the firmware, first of all the screen is white. Nothing other than white has ever displayed on the screen. (Note: I am powering the spider with a power pack) Secondly, the update seems to go through except when it gets to the part where it says “rebooting”… see below…
Connecting to the device…
FEZ Spider found at Port#: COM5
GHI Bootloader Version: 1.02
Device will be updated automatically! DO NOT disconnect or turn off the device!
Updating TinyBooter. Please wait…
Welcome to the community. There is an SDK coming out tomorrow we highly recommend you use instead but for now, folow the bold note here to load the USB driver manually http://www.tinyclr.com/forum/topic?id=9388
I have already installed: C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\USB Drivers\GHI_NETMF_Interface\ghi_netmf_winusb.inf
as well as C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\USB Drivers\GHI_Bootloader_Interface\GHI_Bootloader_Interface.inf
The device is even showing up in device manager.
What SDK is this that is coming out tomorrow? Do you think it will resolve what I am experiencing?
First attempt… upon XMODEM send, it seems to get stuck on first packet for about 30 seconds… then the transfer window closes and now it seems to be going crazy with a ton of BLs, with the odd “Erase all memory”, “Bad firmware”, “1.02”… it seems like its being sent random characters or something… I will disconnect and try again.
In the past we’ve seen some people overwrite the firmware files with TeraTerm accidentally by using the wrong transfer direction; and you have to make sure you use the 1K option. By reinstalling the SDK you’ll get a nice fresh copy of the firmware files so you should be right to go then !