78M6618-PDU-1 データシートの表示（PDF） - Maxim Integrated

部品番号

コンポーネント説明

メーカー

78M6618-PDU-1

78M6618 PDU1 Firmware Quick Start Guide

Maxim Integrated 

78M6618 PDU1 Firmware Quick Start Guide

UG_6618_122

3.3 Rebuilding the Application

The application can be built with or without inclusion of the Boot Loader utility.

3.3.1 Without the Boot Loader

Building the application without the Boot Loader entails that software updates in the end product are

possible only by connecting the TFP2 or ADM-51 tools to the ICE interface port. However, 1 KB of flash

memory is freed when the Boot Loader is not included, which can be used by the application itself.

Select target PDU_NO_BOOT from the drop down list (encircled in the figure above) and press F7 to

build the project. A successful run produces two output files in the \Application\Obj folder. The *.abs file

is most suited to be used by the emulator for debugging. The *.hex file is an image file best suited for

the TFP2 programmer, and contains no debugging information. The *.hex file, as produced by the Keil

compiler, is not suitable for the TFP2 unless the CHKSUM utility is first used to process the file into the

proper format.

3.3.2 With the Boot Loader and CRC

The Boot Loader requires 1 KB of memory and insertion of CRC codes into the image file. Building an

application with the Boot Loader utility allows for subsequent firmware upgrades via the serial interface

(RS-232 or RS-485) connected to the host.

Select target PDU_BOOT from the drop-down list (encircled in the figure above) and press F7 to build the

project. A successful run produces two output files in the \Application\Obj folder. The *.abs file is most

suited to be used by the emulator for debugging. The *.hex file is an image file best suited for the TFP2

programmer, and contains no debugging information. See the Flash Programmer Model TFP2 User’s

Manual on how to use the CHKSUM utility.

It should be noted that the *.hex output file needs to be post-processed in order to calculate and insert

the CRC values. The Hex2CRCHex.exe application is included, in the tools folder of the SDK, to perform

the post-compiling CRC insertion into the hex file. The resulting hex file is renamed with ‘CRC’ added in

the name. For example: 6618_PDU_CRC.hex is generated by the Hex2CRCHex.exe tool using input file

6618_PDU.hex. The project settings are such that this tool is invoked by default, as shown here:

10

Rev.0

Share Link: