This repository provides bare metal embedded software example projects built with Microchip's SoftConsole IDE.
<repo>
|-- applications
| |- .
| |- .
|
|
|-- driver-examples
| |- CoreGPIO
| |- CoreUARTapb
| | .
| | .
| | .
| |- CoreSysServices-PF
| |- miv-i2c
| |- miv-watchdog
| | .
| | .
| | .
The applications directory contains applications that are ready for use with selected hardware platforms.
The driver-examples directory contains example projects demonstrating the Soft-IP device drivers. These examples serve as an easy starting point for the users to start exploring FPGA devices.
Each project provides a README.md explaining its functionality and usage instructions. All projects provide a set of ready to use build configurations and debug launch configurations. They are described in the following sections.
The build configurations configure the projects to build in a specific way. For example, Optimization level -Os, linking to a specific memory address etc.. Below is the list of the common build configurations provided by default with each bare metal driver example project. You may use these build configurations or create your own to suit your project.
| Configuration | Description |
|---|---|
| miv32imc-Debug | Targeted for the Mi-V soft processor configured with RV32I base ISA + M and C extension. Links to MIV_RV32 default reset vector address (0x80000000). Uses peripheral memory map as provided by MIV_ESS Not-optimized (-O0). |
| miv32imc-Release | Targeted for the Mi-V soft processor configured with RV32I base ISA + M and C extension. Links to MIV_RV32 default reset vector address (0x80000000). Uses peripheral memory map as provided by MIV_ESS Optimized (-Os). |
Note that some of the example projects provided in the miv-rv32-bare-metal-examples repository may contain additional or different build configs to suit the functionality. Refer the example projects for details.
A build configuration is a particular combination of SoftConsole project settings. The following sections describe the configurations provided by the default build configurations.
Some of the important project settings are explained in following sections.
The Debug configuration is intended for the early development and debug phase of the project. By convention, the *-Debug configurations use optimization level -O0 and generate maximum debug symbol information.
The Release configuration is intended for the final production release, where an executable stored in non-volatile memory runs after power-on-reset. On Microchip FPGAs, this could also be achieved by attaching the executable as memory client to a memory in Liber®o design flow. By convention, the *-Release configurations use higher optimization level (-Os) and do not generate debug symbol information. It also defines a NDEBUG macro which is used to exclude any debug code from the build.
Linker scripts: Each build configuration needs a linker script. The linker script describes the memory layout of the executable. Each build configuration selects an appropriate linker scripts via project settings.
There are several other settings that are required for a project. For complete project settings go to
\<project-name>->Properties->settings->Tool settings.
Apart from the SoftConsole project settings, each project needs a few more configurations. These configurations are categorized into hardware and software configurations.
The hardware configurations are located in the <project-root>/src/boards/<target-board> folder. The include files in the fpga_design_config folder define the hardware configurations such as clocks and base addresses. You must make sure that the configurations in this example project match the actual configurations of the Libero design that you are using to run the example project.
To choose a particular hardware configuration, include an appropriate <project-root>/src/boards/<target-board> folder path via the SoftConsole project settings.
Software configurations may be required for the correct functioning of the MIV_RV32 HAL, which are described in the README.md.
Apart from that the README.md in each example project describes the software configurations that are required for that project.
The following two pre-configured debug launchers are provided with each project.
| Configuration | Description |
|---|---|
| <project name> hw debug.launch | Intended to be used with *-Debug configurations. Resets soft processor. Downloads the executable and the symbols to the memory. Sets up PC to start location. |
| <project name> hw attach.launch | Intended to be used with *-Release configurations. Does not trigger reset. Downloads only the symbol information and attaches to processor. Typically used to check the current state of harts. If the project is linked to RAM memory such as LSRAM, you will be able to put breakpoints and step debug further. |
Both launchers are configured to use the currently active build configuration, hence the same launcher can be used with any of the build configurations. Make sure that an appropriate build configuration is set as active to avoid issues. Trying to use <*> attach.launch_ while a *-Debug build is active may not work.
You may change the existing debug launchers or create your own launcher to suit your project.
Please refer README.md in each project for details.
Libero® and PolarFire® are the property of Microchip Technology Inc. (MCHP).
