Introduction

The ColdFire 5441x platforms were created before NetBurner 3.x, but they can be easily upgraded. The primary difference is in the device configuration. For reverse compatibility with prior tool sets, all 5441x devices are shipped with a factory application built with the 2.x release so they work with the IPSetup and AutoUpdate utilities. Once you download an application created in NetBurner 3.x, the device will then have the advantages of the 3.x features.

The upgrade procedure consists of building a 3.x application with the _APP.s19 S-record file format output and programming it into the device. Thereafter, you can use either .bin or APP.s19 3.x application files.

Note

The NetBurner example command line makefiles will create both .bin and .s19 files. If using NBEclipse, the _APP.s19 file output must be enabled.

Attention

Once a device is running a 3.x application, you will no longer use the 2.x utilities IPSetup and AutoUpdate. Instead, you will use the methods described in the Device Discovery and Configuration section of this manual. Although IPSetup can still be used to get the device IP address, it cannot manage settings.

5441x Product Models Numbers

• MOD54415
• MOD54417
• NANO54415
• SB800EX
  

Set Option For S19 Output Format in NBEclipse

Right-click on the project, then: C/C++ Build -> Settings -> NB CompCode -> General -> Build Oputput -> Build Binary and change from Binary to Srec.

Procedure Using Alternate Boot Monitor

As of April 2021, the Alternate Boot Monitor has the ability to process a 3.x application .bin file. Older revisions must use the _APP.s19 file. Alternate Boot Monitor revisions must be the revision shown below or later to process .bin files:

• Connect to the debug/console port of the device with a serial terminal such as MTTTY
• Reset or power cycle the device (or use the recovery jumper)
• Press the 'A' key to abort when prompted (or use the recovery jumper)
• Use the AutoUpdate utility to download your 3.x application image

Procedure to Revert Back to 2.x

If you wish to revert back to 2.x, there are two methods to abort the boot sequence and enter the Alternate Boot Monitor:

1. Using the serial port interface
2. Using the hardware reset jumper

Serial Port Procedure

• Connect to the RS-232 debug/console port of the device with a serial terminal such as MTTTY
• Reset or power cycle the device
• Press the 'A' key to abort when prompted to abort to the Alternate Boot Monitor
• Use the AutoUpdate utility to download your 2.x application image

Hardware Reset Jumper Procedure

• Insert the hardware reset jumper
• Reset or power cycle the device to abort to the Alternate Boot Monitor
• Use the AutoUpdate utility to download your 2.x application image

Note on IPSetup utility and 3.x Devices

The windows IPSetup utility will still identify the IP address of a 3.x device. However, it cannot configure the device. The IPSetup device window designates these devices with a prefix of NEWCONFIG.