Went back into the FEZ Config and here’s the following when I click “Check device for update”:
[quote] Loader (TinyBooter) version information:
184.108.40.206 on this computer.
Loader (TinyBooter) Version: Not present on the device.
Firmware (TinyCLR) version information:
220.127.116.11 on this computer.
Firmware (TinyCLR) Version: Not present on the device.
The device is in Loader mode.
Click on ‘Reboot CLR’ under the Advanced menu to reboot the device.[/quote]
I tried the “Reboot CLR” and it gives me the exact same results as above.
I’ve repeated my steps several times. The Tiny booter doesn’t load onto the device? Any ideas?
@ Gismofx - Im uncertain if it could be the USB Drivers. Here are a couple of more suggestions to try:
Try to use another computer.
If that does not work, try to download the latest SDK (NETMF and Gadgeteer Package 2014 R1) from the Support->NETMF page and see if that would fix the issue. If this SDK has been install previously, try to uninstall it and re install the SDK and see if this will fix the issue.
Sorry, can you give us more info here? You’re saying that you had been using this Cerb40 before, and had updated the firmware and had been programming it. Then something happened and you could no longer do that. And then you started on this journey you’ve documented here.
Any hints what else happened ? Did you have a failed deployment or anything ?
Yes. It was working just fine up until this morning. I pulled out the Cerb from my box of stuff and went to deploy some code that I’ve deployed before from Visual Studio 2012. Upon deployment the debugger didn’t seem to attach to the device, but nothing looked unusual in the output dialog box. Unfortunately, I didn’t save the output text. I can’t really say what happened. I didn’t have anything hooked up backwards or anything at all. Just the board and the usb cable. So, I felt compelled to dig a little deeper and that’s where my post starts.
I used it no more than a week ago…Surprisingly, I do have another netmf device…netduino 2, but I was having some problems and was really eying the Cerb 40, so I thought I’d try it. I dig the form factor and features and the community seems really great…Some of my issues immediately went away with the Cerb 40, but I’m running into one particular problem, same as my Netduino, which I detailed in another post (still near the top of the forum).
So, I’m jumping between devices but looks like Cerb 40 would end up in my final project. Would love to get to the bottom of this.
I don’t think there’s actually a recognition that there’s anything systemic here. Might be worth you creating your own topic to help troubleshoot, but I have never seen a situation where after booting into STDFU mode, then correctly deploying the bootloader, has left the processor in a state where the CLR couldn’t then be loaded on. The developers guide has a number of steps that if you don’t follow can result in the bootloader not being applied which might be relevant to your situation https://www.ghielectronics.com/docs/46/fez-cerb-family-developers-guide
Click the Create from Map button
Select the Erase radio button
Once finished, click Load DFU File button
Select C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.3 SDK\Firmwares\Cerb Family\Loader.dfu (or relevant).
Click Download radio button
Reboot your board