Home · |
Applets are binary programs that can be loaded through the sam-ba connection into some RAM region of the target before being executed. Applets extend the SAM-BA monitor to provide more features. The main usage of applets is to program the bootstrap into some Non-Volatile Memory (NVM).
Within the context of the sam-ba program, the board is the hardware design which embeds a SAM MPU device.
The bootstrap is the 2nd stage bootloader (or directly the user application), executed immediatly after the ROM code. It is a program linked to be executed from the base address of the internal SRAM0.
Within the context of the sam-ba program, the device represents the SAM MPU that drives the board. It is a Microchip SoC like SAMA5D2.
The host is the system running the sam-ba program. It is likely a Windows/Linux PC workstation.
Non-Volatile Memory are used to store the bootstrap needed by the boot sequence process. NVM are driven by internal controllers of the SAM MPU, such as QSPIx, SDMMCx, FLEXCOMx SPI, ...
The ROM code is the 1st stage boot-loader or firmware running on the target at power-on or reset. It is responsible for the basic initialization of the target and for loading then executing a bootstrap loaded from an external Non-Volatile Memory (NVM) into the internal SRAM0. If no such bootstrap is found, then the ROM code executes its SAM-BA monitor.
The SAM-BA monitor is a sub-process of the ROM code, waiting for connection of the sam-ba program from either the ROM code console port or from the USB device port of the target. Once connected, the SAM-BA monitor provides a interactive interface and a set of basic commands to read from / write into the target memories or its peripheral registers. Besides, the SAM-BA monitor can also download applets through the sam-ba connection before executing them.
The target is the SAM-based board to be programmed with the sam-ba program.
Copyright © 2018 Microchip Technology | SAM-BA Documentation |