1 MCC Melody Bootloader: 8-bit
2 User Interface
3 Unified Bootloader Host Application (UBHA)
4 Use Case Examples

This section explains how to configure various bootloaders using MPLAB® X IDE and MCC Melody.
5 Verification Schemes
This section discusses the various methods of application verification provided to the users by the bootloader module.
6 Bootload Communication Protocol: 8-bit
- 6.1 Read Version
  
  Enables the bootloader to read the version information from the configuration bits of the device.
- 6.2 Read Flash
  
  Enables the bootloader to interface with various memory drivers used by 8-bit PIC and 8-bit AVR chips.
- 6.3 Write Flash
  
  Enables the bootloader to write data to specified address locations.
- 6.4 Erase Flash
  
  Enables the bootloader to initiate erase commands to the memory driver.
- 6.5 Read EE Data
  
  Enables the bootloader to read bytes out from the EEPROM memory.
- 6.6 Write EE Data
  
  Enables the bootloader to write some number of bytes to the EEPROM memory.
- 6.7 Read Config
  
  Enables the bootloader to read the configuration words out of the chip’s memory.
- 6.8 Write Config
  
  Enables the bootloader to write to the configuration word range of memory.
- 6.9 Calculate Checksum
  
  Enables the bootloader to calculate and return a checksum value over a given range of memory addresses.
- 6.10 Reset Device
  
  Enables the bootloader to initiate the device’s software reset cycle
7 References
Microchip Information

6 Bootload Communication Protocol: 8-bit

Introduction

One of the most important features of any bootloader is going to be the bootloader’s command set. In order for the host application to use this command set, an agreed upon protocol is used by both the host and the bootloader applications to pass commands in a hex data string format between one another.

Response Codes

0x01 - Command Successful
0xFF - Command Unsupported
0xFE - Address Error
0xFD - Processing Error
0xFC - Buffer Overflow Error

Command Set

The online versions of the documents are provided as a courtesy. Verify all content and data in the device’s PDF documentation found on the device product page.