This component is responsible for configuring the communication protocol used for data transfer between the bootloader host and bootloader client.
This component configures which verification method is used for user application verification.
These components are used to enable the I/O operations of the bootloader firmware.
This component allows the user to configure where the memory partition for the application begins. This also means that the memory partition of the bootloader client will end at this address.
This section demonstrates how to configure a bootloader for 8-bit PIC devices using UART, SPI, or I2C for communication.
This section demonstrates how to configure a bootable application configuration for 8-bit PIC® devices.
This section demonstrates how to merge the bootloader and application projects into a single hex file for 8-bit PIC devices.
This section demonstrates how to enable interrupts in the application code for PIC® devices.
This section demonstrates how to configure a bootloader for 8-bit AVR devices using UART, SPI, or I2C for communication.
This section demonstrates how to configure a bootable application configuration for 8-bit AVR devices.
This section demonstrates how to merge the bootloader and application projects into a single hex file for 8-bit AVR® devices.
This section demonstrates how to enable interrupts in the bootloader and application code for AVR® devices.
This section discusses various methods to verify the application provided to the users by the 8-Bit MDFU Client library.
The bootloader will check for a non-void value at a predefined location within the Reset Vector of the end application.
The bootloader will verify program status through a predefined byte value, also known as a State Flag or Status Byte.
The bootloader will verify program status by calculating and comparing a 16-bit checksum on the program data bytes.
The bootloader will verify program status by calculating and comparing a 16-bit or 32-bit CRC on the program data bytes.
This section communicates the most important assumptions of use for the 8-Bit MDFU Client and ecosystem.