An Application resource is the contents of a file identified its relative path from the Application classpath.
An Application resource is one of the following type:
- Raw Resource,
- Internationalized Message (Native Language Support).
The resource may be stored in RAM, flash, or external flash; and it is the responsibility of the Core Engine and/or the BSP to retrieve and load it.
There are two ways to store resources:
Internal resource: The resource is taken into consideration during the Application build. The SOAR step loads the resource and copies it into the same C library as the Application. Like the Application, the resource is linked into the CPU address space range (internal device memories, external parallel memories, etc.).
External resource: The resource is not taken into consideration during the Application build. It is the responsibility of the BSP project to manage external resources. The resource is often programmed outside the CPU address space range (storage media like SD card, serial NOR flash, EEPROM, etc.).
The BSP must implement the proper Low Level API (LLAPI) C functions:
LLEXT_RES_impl.h. See External Resources Loader for more information on the implementation.
All resources must be added in the project, usually in
All resources must be declared in the appropriate
*.list files depending on the type (raw, image, font, NLS) and the storage location (internal or external).
The following figure summarized how to declare resources:
For more details on how to use Application resources, refer to the following dedicated sections: