1.7.1.5 UDP Bootloader Protocol

The Unified host application running on Host-PC uses below communication protocol to interact with the Bootloader firmware. The Unified host application acts as a master and issues commands to the Bootloader firmware to perform specific operations.

Frame Format The communication protocol follows the frame format, as shown below

<SOH><CRCL><CRCH><EOT>

Where:

<...> Represents a byte

Represents an optional or variable number of bytes

• The frame format remains the same in both directions, that is, from the host application to the Bootloader, and from the Bootloader to the host application.

• The frame starts with a control character, Start of Header (SOH), and ends with another control character, End of Transmission (EOT)

• The integrity of the frame is protected by two bytes of Cyclic Redundancy Check (CRC)-16, represented by CRCL (low-byte) and CRCH (high-byte)

Control Characters

Some bytes in the Data field may imitate the control characters, SOH and EOT. The Data Link Escape (DLE) character is used to escape such bytes that could be interpreted as control characters. The Bootloader always accepts the byte following a <DLE> as data, and always sends a <DLE> before any of the control characters.

Commands The PC host application can issue the commands listed in below to the Bootloader. The first byte in the data field carries the command.

Read Bootloader Version Information

The Read Version command sequence is as shown in below table with corresponding response

• The Bootloader responds to the PC request for version information in two bytes as shown above

  • MAJOR_VER = Major version of the Bootloader

  • MINOR_VER = Minor version of the Bootloader

Erase Flash The Erase Flash command sequence is as shown in below table with corresponding response

• On receiving the erase Flash command from the PC host application, the Bootloader erases that entire application program space starting from the application start address configured

• The Bootloader Task routine returns only after entire application space is erased

Program Flash The Program Flash command sequence is as shown in below table with corresponding response

• HEX_RECORD is the Intel Hex record in hexadecimal format

• The PC host application sends one or multiple hex records in Intel Hex format along with the program Flash command

• The MPLAB XC32 C/C++ Compiler generates the image in the Intel Hex format. Each line in the Intel hexadecimal file represents a hexadecimal record

• Each hexadecimal record starts with a colon (:) and is in ASCII format. The PC host application discards the colon and converts the remaining data from ASCII to hexadecimal, and then sends the data to the Bootloader

• The Bootloader extracts the destination address and data from the hex record, and writes the data into program Flash