I’ve been trying to get .Net Gadgeteer working on Windows 8 for a while and I have one remaining problem - I can’t get the firmware to update. What happens is that when I run the config tool, it gets most of the way there and then fails leaving me with an erased .Net Gadgeteer. I thought it might be related to the tinybooter version (mine is 4.1.6 - or something like that). I’ve been looking at this guide and I can’t get past one of the steps:
where is says “EMX: Press and Hold UP, Select and Down buttons then while holding them down press and release the Reset button.” … I have no idea what this means. I tried the page up/down keys and enter key but nothing happens. I can’t get any further without getting past this step.
Apologies for being thick, but can anyone help me get this sorted?
It’s a Fez Spider 1.0. I’ve tried with those settings … it get’s about three quarters through firmware2.hex and then fails displaying a message about an interrupt in deploying.
I wondered whether updating the tinybooter would help, but I got stuck at that point in the guide.
The EMX instructions (multiple buttons) are equivalent to the switches on the Spider kit.
The fact that you go through the update process but fail shows you’re using the right approach, but can you please let us know what the version information from your running (in normal mode) device says, from “Device Capabilities” option in mfdeploy.exe? That way we can validate that the firmware is or isn’t consistent. You can try the “legacy” firmware updater from the support page too, to help do all your updates easily.
The other way you can tell what mode a device is in is to look at your PC’s Device Manager; if in a bootloader mode, you’ll see a COM port, if running netmf normally you’ll see a debuggable .NET device.
Thanks for all the suggestions. I’ve tried the legacy updater and it can’t connect. It can ping the device but when I start the update it doesn’t complete.
Device capabilities in MFDeploy says ‘Not Supported’.
There is no firmware on the device as it was erased before the failed update. It’s running tinybooter 4.1.6.0.
It is never recognised in serial debug mode. I can ping it in usb debug mode and use fezconfig (the latest) to start the update process (which fails).
Actually I got it to work. With much plugging and unplugging of usb cables I got one of the legacy uploaders to update tinybooter, then I used the newer Fez Config to get the firmware up to the latest version.