I had a similar problem yesterday. I had uninstalled the old 4.2 stuff from February and installed the new 4.3 & 4.2 stuff, but upgrading my spider firmware via mfdeploy bricked it. I erased and re-installed tinybooter via teraterm. Then re-updated the firmware via mfdeploy. But could not change the usb name.
So… when I got home, I fired up a different computer that had the 4-30-2013 bits that I downloaded before they made it to the main support site - I guess these were semi pre-release? Anyway, that machine had a spider updater on it. I don’t know why or how. I didn’t see this app on the first computer. But anyway, the spider updater fixed my problem.
I’ve been finding it difficult to collect a consistent set of tools. The Current 4.3/4.2 release does not have the update program. The opening message of this thread points to the “old updater applications” and also to a preview of a new application. I did try the “old” version and that didn’t work for me - don’t quite remember how, but it was a failure with a popup message. I’ve just grabbed the preview of the new one - hopefully that is the version that worked for you. I’ve added a screen shot with its “About” window showing the version. From the announcement post it looks to be about 2 months old. I’ll have a go with that. Thanks for the information.
Used the new configuration tool to update my mainboard
Used the new configuration tool to change the USB name to Gadgeteer
Now it all works as it should. I should start from scratch on a new PC to verify the process, but most of the problem seems to have been in configuring the spider. I don’t have a clean spare to test, and anyway I have Gadgeteering to do now.
I tried using TeraTerm, but the USB option is grayed out, despite the GHI loader showing it as there. I tried to use that to update my Spider, but it hung on Firmware2 file, and the T35 is just white now.
Can you check what serial port is visible in Device Manager? Just checking that you do know you have to manually put it in loader mode for the serial port to appear - the GHI app forces this so you never have to do it… Then, once a serial port is available in Device Manager, opening Tera Term should see the port.
I was able to update my CerbBee ok. But I continue to have Win8 and USB3 issues. I may have to spend some money and get a USB hub. It’s a bit frustrating as it all should be plug-n-play and worked fine on my previous (now not working) laptop.
After several attempts at removing and reloading all SDKs, I cannot get past the following exception that gets thrown when Program.Mainboard is initialized:
[ul]I am using Visual Studio 2012 (with sp 2)
I have all of the correct SDKs (see image)
I have the simplest setup (main board with usb module) (see image)
I have updated the firmware of the Spyder using GHI_NETMF_Configuration_Toolv003.exe
I made sure my VS project is using .NET Micro Framework 4.2 [/ul]
namespace GadgeteerApp1 {
using Gadgeteer;
using GTM = Gadgeteer.Modules;
public partial class Program : Gadgeteer.Program {
private Gadgeteer.Modules.GHIElectronics.UsbClientDP usbClientDP;
public static void Main() {
// Important to initialize the Mainboard first
Program.Mainboard = new GHIElectronics.Gadgeteer.FEZSpider_II();
Program p = new Program();
p.InitializeModules();
p.ProgramStarted();
// Starts Dispatcher
p.Run();
}
private void InitializeModules() {
this.usbClientDP = new GTM.GHIElectronics.UsbClientDP(1);
}
}
}
I don’t know what to try next to get this very simple set up running. Can anyone shed some light on my problem?
