Main Site Documentation

Firmware upgrade


#1

I updated the FEZ Domino using the file USBizi_CLR.GHI, at the end of file transfer I got a message that says bad firmware and now MFDeploy can’t see the device.
The previous firemware version was 4.0.3.0, the release notes from the GHI NETMF v4.1 SDK says it should be 4.1.3.0
Any help is appreciated


#2

Hold LDR, reset board and try to load again after you use E to erase all


#3

Hi Gus:

I erased all firmware and then reload the firmware from file, got the same message “bad firmware”, so I transferred the file again (without erasing) and this time it updated correctly and I can access the device through MFDeploy.

Cheers!


#4

What is the latest firmware for FEZ Panda ?


#5

This is the latest production:

SDK Version 1.0.11 October 15, 2010
[ulist]
USBizi (FEZ Mini, FEZ Domino, FEZ Rhino, FEZ Panda) V 4.1.3.0
EMX (FEZ Cobra) V 4.1.3.0, TinyBooter V 4.1.3.0
ChipworkX V 4.1.3.0 TinyBooter V 4.1.3.0
GHI NETMF Library V 4.1.3.0
[/ulist]

But there is also new beta:

SDK Version 1.0.12 February 21, 2011
[ulist]
USBizi (FEZ Mini, FEZ Domino, FEZ Rhino, FEZ Panda) V 4.1.4.0
EMX (FEZ Cobra) V 4.1.4.0, TinyBooter V 4.1.3.0
ChipworkX V 4.1.4.0 TinyBooter V 4.1.3.0
GHI NETMF Library V 4.1.4.0
[/ulist]


#6

easiest way is to check here always http://www.tinyclr.com/release-notes/


#7

I am currently having the same problem as well on the Domino.


#8

Okay, I fixed it.

I think the problem lies with Tera Term (I think).

What was happening is that, for some reason, it was reporting the firmware as a 0K file and not transferring it properly. The odd thing was, I created another file in that directory and then uninstalled/reinstalled the SDK and Tera Term was still reporting that both files were in the firmware directory.

A copy of the firmware to my desktop and then a transfer worked just fine.