This tutorial shows how to create an MSBuild-based project for an embedded bootloader that will be stored in a separate region of the FLASH memory and can be linked independently from the main project:
SmartFusion cSoC: Basic Bootloader and Field Upgrade eNVM Through IAP Interface 4 In release mode, while updating the eNVM content, the programming code (IAP Programmer) should not reside on the eNVM as it cannot be reprogrammed and accessed simultaneously. I've done this before with PIC24 parts where I created 2 projects, one for the bootloader and one for the application, each with a custom linker script that forced the linker to keep them within their specific areas of flash. The bootloader set the config fuses and was burned in by the programming cable. The application was installed via a uSD.
This is a simplified version of the GNU Make-based bootloader tutorial. We will focus on configuring MSBuild to link the outputs from 2 projects together and will leave out details about interrupt handling and system calls that are described in the GNU Make-based tutorial.
You can find the project shown in this tutorial in our Github repository here: https://github.com/sysprogs/tutorials/tree/master/visualgdb/ARM/BootloaderDemo
To learn about handling interrupts in bootloader-based setups and using syscalls from the application to the bootloader, follow the second part of the GNU Make-based bootloader tutorial. Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |