I have recently updated the page. It still needs to have some work done but it now addresses the Hydra Updater. Thank you for the “head’s up”. 
I can’t seem to get MFDeploy to load this new firmware on my new Cerbuino. I installed the package, connected the USB cable, opened MFDeploy, successfully pinged, then selected the ER_CONFIG and ER_FLASH, then clicked Deploy. A dialog then popped up saying “connecting”, then “erasing”, then “Unable to deploy”. See screenshot. I tried it on Win7 32-bit and Win8 64-bit, but both did exactly the same thing. The version of .NET MFDeploy is from the 4.2QFE1 SDK.
So, then I loaded the TinyBooter DFU file from the Cerberus directory. That loaded fine, but after that the device was not recognized at all by windows, so there’s no chance of it working with MFDeploy. So, at that point, just to make it work again, I put it back into Bootloader mode and flashed the older Cerberus DFU file. Now it is recognized again as FEZ Cerberus in Windows. But, MFDeploy is still not loading the firmware.
Any ideas? Is there is DFU version of this firmware instead? Honestly, I have never liked MFDeploy…
Thanks,
-Valkyrie-MT
Please try
1.Put board in bootloader mode
2.Open STDFU
3.Erase {On Protocol tab select Erase, Click on ‘Create from Map’, Click on ‘Go’}
4.Click ‘Load DFU File’ and select TinyBooter_4_2_0_1.dfu
5.Select Download
6.Click 'Go’
7.Remove bootloader jumper and Reset the board
8.Open MDDeploy
9.Deploy ER_CONFIG and ER_FLASH
1 Like
@ aron
From the wiki:
Must this be verion 4.1 of MFDeploy?
After uninstalling MF4.1 and installing MF4.2, the tools folder under 4.1 doesn’t contain a MFDeploy. There is only one in the 4.2 folder…
@ Rajesh - Thanks. After flashing the bootloader exactly as you described, the Cerbuino was recognized properly by windows as a FEZ Cerberus device. Then, MFDeploy worked fine. The only thing I did differently was that I used the DfuSe Demonstration app to flash the dfu and did not erase first.
Thanks!
-Valkyrie-MT
Is the Ethernet ENC28 Module supported with this release? I don’t see the module in the design surface.
Thanks,
-Valkyrie-MT
No ethernet and no SD card support just yet.
Still have the BSOD if I reset the board while the project is deploying with VS2010. I guess this is not a recommended operation, but is this behavior normal?
Did you update the firmware after installing the package?
Yes I do!
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.0.1
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: May 21 2012
I see on the Cerbuino page that wifi support can be added with an XBee Wifi card. Can an XBee card be configured through the Cerbuino using XCTU or is a breakout board necessary? Is there any managed library for using the XBee Wifi?
Sorry for all the questions. Just exploring ways of getting a Cerb connected to a Network.
Thanks,
-Valkyrie-MT
AKAICT you’ll need a breakout board.
Not yet. It is planned to be included in http://xbee.codeplex.com (I am tasked with this piece)
Don’t be! They’re good ones.
If you you have the XBee module then you could probably figure out how to use it in combo with an Extender module & an FTDI cable without needing a separate breakout. If you’re talking about just a Cerbuino Bee by itself that doesn’t look likely at this time. But, perhaps you also have the XBee module. You can use this as a reference circuit.
Using MFDeploy 4.2 should be just fine but I do not use it as it seems to be very slow (perhaps a bug in MFDeploy?). I will remove the statement that is to be MFDeploy 4.1 and just imply that it needs to be any MFDeploy version 4.1 or greater.
I’ve updated my cerberus, but the cerbuino reisted a bit more. For anyone else doing this the instructions differ from the Cerberus in that LDR pads have to be shorted with a wire. The STDFU Tester program is a bit tempermental - it may take a few attempts.
I found there is a short window between removing the boot pin and pressing reset for it to come back on to be recognized by windows as a GHI usb device.
Patience and peristance.
If I order a cerberus today (may 27th) - will it come with tinybootloader already on it?
You could do it but it would require buying a serial-usb module:
http://www.ghielectronics.com/catalog/product/287
You would have to write a simple piece of code that would bridge the serial port of xbee and the serial port of the module inside the cerbuino. Alternatively you could communicate with your Cerbuino using CDC mode (if this is available in OSHW libraries) but then you would have to program the board thru serial… this would require a serial to usb converter as well.
The cost of Serial-To-USB module is almost the same as XBee Explorer USB so I don’t think it’s worth the trouble. The only advantage i see is that you could run the program on Cerbuino and simultaneously red the XBee module to see the settings (of course come kind of synchronization would have to be added).
I’ve noticed something strange going on with this latest build. I think the problem is possibly that the debug symbols are not quite in sync with the deployed assemblies. If I create a new blank Gadgeteer 4.2 project and put a break on the first line and try to step through the program, once I get to the closing brace of ProgramStarted() I’ll get an error saying the source file (Program.cs) has changed. Then after closing it, I’ll get the second error. Sometimes, I get the third error. Notice the circled path. That path does not exist on my machine. I believe that belongs to either GHI or Microsoft and for some reason VS is trying to use debug symbols for it instead of the actual symbols for my Program.cs. Anyone else seeing this?
Hello,
OneWire seem to be come up for a few poeple. Could I please get a code example of using OneWire on the OSHW (Cerbuino bee) the class native to 4.2 is different in more than a few ways from the GHI.Hardware implementation.
I’m troubleshooting my code, the parasitic power setup, the new firmware, the dallas semi ds18b20 and 4.2 microframework. So far I just can’t get a reading off the ds18b20, but new class doesn’t have reset() method -so I’m unclear on its usage.
Thanks.
Just got time at work to do the upgrade to 4.2 STABLE for my Cerberus.
Loaded the bootloader. Reset the board.
Now Windows 7 64bit thinks it’s a Fez Cerberus SideShow device.
MFDeploy will not recognise it.
Any idea what is going on?