Last modified August 22, 2014
Cross Reference: If you have not already, you might want to read the introductory page explaining the firmware (TinyCLR) and the loader (TinyBooter). It gives a basic procedure for determining whether or not you need to update. It also contains tips and trouble shooting advice.
This document describes updating TinyBooter for specific processors.
To make sure that this document is for your processor see the generic Loader (TinyBooter) documentation.
There are three ways to update the processors supported by this page:
Using FEZ Config
You can only use FEZ Config if its version number is greater than 0.1.3 (013). Otherwise, you must use the Manual Procedure Below
For all System on Modules, use the Manual Procedure Below
If your device/processor is not listed, you are on the wrong web page. Go to the general Loader page, and follow the links for your device.
The processor update steps for the following devices are identical, with two exceptions: (1) which is the way the device is put in loader mode. This is done via switches, jumpers, or buttons; and (2) selecting the file on your development system that contains the Loader (TinyBooter).
If you do not see any COM ports in the list and you can not get anything to happen in the serial area then skip to step 5 below
For FEZ Spider put the board switches in Loader configuration and press reset (while board is powered up) or power cycle the device.
For FEZ Spider II put the board switches in Loader configuration and press reset (while board is powered up) or power cycle the device.
G120 has a few Special Pins for accessing the installation mode. The pins have internal pull-ups so leave them unconnected for 'High' or connect to 'GND' for 'Low'.
|LDR0 (P2.10)||LDR1 (P0.22)||Boot Access|
For G120 connect LDR0 and LDR1 to GND (that's P2.10 and P0.22) and reset (while device is powered) or power cycle the device.
Pin 59 P1_30 AD4/COM4 OE must NOT be grounded on power-up for GHI Bootloader to function correctly.
Similar to the G120, pins are connected to ground to make them LOW:
EMX: Ground pins 7, 3, and 53 then reset (while device is powered) or power cycle the device.
Reference: see the EMX Manual
For FEZ Cobra II press and while holding LDR0 and LDR1 buttons, press the reset button (while board is powered) or power cycle the device.
Windows may install a new driver file: GHI_BootLoader_Interface.inf
GHI Boot loader commands are case sensitive. Be sure you type the command letters in the same case as shown in this document.
Installing the new loader is simple but it requires a terminal program that supports XMODEM file transfer (which TeraTerm does). XMODEM has a few settings, GHI boot loader requires 1K transfers with 16Bit CRC error checking.
XMODEM transfer is initiated using the X command. After the X command is entered, the device will start sending back the “C” character to TeraTerm. This “C” is an indicator telling you the device is waiting for data.
Entering X command...
Once you see the “C” character appearing on the terminal window, you can perform the XMODEM transfer from the menu File > Transfer > XMODEM > Send...
A dialog box will appear. You will need to navigate to the proper folder (via Look in:). The directory and file names are dependent on your device and SDK release:
For all the directory names below, your version number may vary. For example you may have v4.2 in place of vX.X
For NETMF 4.3 based SDKs (GHI's "NETMF and Gadgeteer Package 2014 R2" and newer SDKs) a subdirectory heirarchy is used ...\Firmwares\EMX or ..\Firmwares\G120; in this case, the TinyBooter file is named loader.ghi
For NETMF 4.2 based SDKs (GHI's "NETMF and Gadgeteer Package 2014 R1" and previous):
Legacy directory (4.1 SDK) for EMX:
C:\Program Files (x86)\GHI Electronics\GHI NETMF v4.1 SDK\EMX\Firmware\TinyBooter
Before clicking on "Open" make sure the 1K button is selected (see above). Then click "Open." Updating the loader takes a few seconds. Once installation has finished and the file is valid, the new loader is executed automatically and you will not see “BL” again. If you do see the "BL" again after this process, it means that the update process failed. You might need to double check that the downloaded file is not corrupted.
At this point you have a clean Flash memory with only the loader (TinyBooter). Proceed to firmware (TinyCLR) installation instructions or return to the page that directed you here (back button in the browser).