![]() This value can be found in cHwMagic field here It is defined by Wirepas and can’t be modified. HW_MAGIC : This is an 8 bit number used to identify the type of micro-controller the stack is running on. What are STACK_AREA_ID, APP_AREA_ID, HW_MAGIC? Only Scratchpad and User areas can be in external flashĪs an example, the below table describes the default area list for Nordic Semiconductor nRF52832 memory map that was described in the previous chapter : The content of this header can be read using “MSAP Scratchpad Status” remote API command.īoolean, indicate if the area is in internal or external flash This means that once flashed, it is not possible to modify the area list defined in a device for the lifetime of the product.Įach area defined in the bootloader has the following information:īoolean, tells the bootloader to store a special header when updating this area. And they are stored inside the BLCONFIG when the device is flashed. They are defined and can be modified in the SDK. Up to 8 areas can be defined in the bootloader. Instead of having hardcoded addresses in its code to know the location of each component, the bootloader maintains a list of areas that contain this information. The bootloader uses the concept of area to manage its memory regions. It is possible to change those limits based on product needs keeping in mind to ensure a coherent flash memory map to ensure scratchpad storage and OTAP in the product. This limit is here more to act as a warning rather than being a hard limit as per the previous explanation related to the Application area partitioning. About application sizeīy default a maximum application size is set in the SDK linker script for the application size (40KB for 512kB SoCs and 256kb for 1MB SoCs). It is highly recommended to ensure that the available smallest scratchpad area still allows to store any scratchpad to ensure proper OTAP. Note: In case of an heterogenous network, the nodes having the smallest memory footprint are the limiting one for OTAP. Hence the size of the application shall remain aligned with the total available size of the application area and the targeted use cases. For obvious reasons, the scratchpad area shall be large enough to store an OTAP image. The bootloader maximizes the size left for the scratchpad based on the real size of the application (also to avoid a scratchpad to overwrite the application itself). Depending on the total available flash of the microcontroller (MCU) the available space for the application + scratchpad varies between 232kB (for 512kB MCUs) and 748kB (for 1MB MCUs). ![]() It means that the maximum size of the scratchpad a device can store will depend on the application size.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |