Introduction

The MP image is used for Wi-Fi & BT performance verification and Wi-Fi & BT parameters calibration in massive production. This chapter mainly illustrates how to build and use the MP image.

Refer to the MP document for more details about MP flow.

How to Build MP Image

The steps of building MP image are depcited below:

Navigate to work directory {SDK}\amebadplus_gcc_project.
Use command make menuconfig to modify the configurations.
1. Enable MP
2. Enable Wi-Fi, and configure KM4 as AP core and KM0 as NP core.
3. Enable BT.
4. Save and exit the menuconfig.
Use command make all to rebuild the projects of KM0 and KM4.

The MP image km0_km4_app_mp.bin will be generated in {SDK}\amebadplus_gcc_project and all the images releated to the MP image can be found in the paths below:

{SDK}\amebadplus_gcc_project\project_km4\asdk\image_mp
{SDK}\amebadplus_gcc_project\project_km0\asdk\image_mp

How to Combine Images

Before downloading images into the chip, the MP image needs to be combined with normal image. In massive production, the MP image is used to calibrate the parameters first. After calibration, you can use the command illustrated in How to Switch Image to switch to the normal image and boot from it. Since the chip boots from OTA1 by default when both OTA1 and OTA2 images are valid and with the same version number, the MP image should be located in the OTA1 field.

The steps of combining images are depcited below:

Check if both the normal image and MP image are valid.

Use the Ameba_1-10_MP_ImageTool_Linux to combine all the images, including km4_boot_all.bin, km0_km4_app_mp.bin and km0_km4_app.bin, which are located in {SDK}\amebadplus_gcc_project.

Set the highlight image offsets according to the Flash layout, which can be found in {SDK}\component\soc\amebadplus\usrcfg\ameba_flashcfg.c.

/*
* @brif        Flash layout is set according to Flash Layout in User Manual
*  In each entry, the first item is flash regoin type, the second item is start address, the second item is end address */
const FlashLayoutInfo_TypeDef Flash_Layout[] = {
   /*Region_Type,      [StartAddr,     EndAddr]                */
   {IMG_BOOT,          0x08000000, 0x08013FFF}, //Boot Manifest(4K) + KM4 Bootloader(76K)
   //Users should modify below according to their own memory
   {IMG_APP_OTA1, 0x08014000, 0x081F3FFF}, //Certificate(4K) + Manifest(4K) + KM4 Application OTA1 + Manifest(4K) + RDP IMG OTA1

   {IMG_BOOT_OTA2, 0x08200000, 0x08213FFF}, //Boot Manifest(4K) + KM4 Bootloader(76K) OTA
   {IMG_APP_OTA2, 0x08214000, 0x083F3FFF}, //Certificate(4K) + Manifest(4K) + KM4 Application OTA2 + Manifest(4K) + RDP IMG OTA2

   {FTL,                       0x08700000, 0x08702FFF}, //FTL for BT(>=12K), The start offset of flash pages which is allocated to FTL physical map.
   {VFS1,                      0x08703000, 0x08722FFF}, //VFS region 1 (128K)
   {USER,                      0xFFFFFFFF, 0xFFFFFFFF}, //reserve for user

   /* End */
   {0xFF,                      0xFFFFFFFF, 0xFFFFFFFF},
};

Set km0_km4_app_mp.bin in IMG_APP_OTA1 section
Set km0_km4_app.bin in IMG_APP_OTA2 section

Execute the command and save the combined image named Image_All.bin.

sudo ./Ameba_1-10_MP_ImageTool_Linux -combine km4_boot_all.bin 0x0000 km0_km4_app_mp.bin 0x14000 km0_km4_app.bin 0x214000

Download the Image_All.bin into the device after the combination is finished.

Note

The normal image km0_km4_app.bin is built with MP disabled. Check the normal image in {SDK}\amebadplus_gcc_project. All the images related to normal image can be found in paths below:

{SDK}\amebadplus_gcc_project\project_km4\asdk\image
{SDK}\amebadplus_gcc_project\project_km0\asdk\image

Boot Flow

Reset the device after downloading image is finished.

Check if the device boots from MP image successfully.

[MODULE_BOOT-LEVEL_INFO]: KM4 SRAM[20010000:1200]
[MODULE_BOOT-LEVEL_INFO]: KM4 PSRAM[0e045a20:20]
[MODULE_BOOT-LEVEL_INFO]: IMG2 BOOT from OTA 1
[MODULE_BOOT-LEVEL_INFO]: Start NonSecure @ 0xe000115 ...
[MODULE_BOOT-LEVEL_INFO]: VTOR: 20005000, VTOR_NS: 0
[MODULE_BOOT-LEVEL_INFO]: KM4 APP START
...
[MODULE_BOOT-LEVEL_INFO]: KM0 VTOR: Ox20000000
[MODULE_PMC-LEVEL_INFO]: AP wake event 410 80000008
[MODULE_PMC-LEVEL_INFO]: NP wake event 804 41008308
[MODULE_BOOT-LEVEL_INFO]: KM0 OS START
[CAL131K]: delta:22 target:2441 PPM: 9012 PPM_Limit:30000
[CAL4M]: delta:0 target:320 PPM: 0 PPM_Limit:30000
[MODULE_BOOT-LEVEL_INFO]: KM4 MAIN
Register flash disk driver to Fatfs.
Fatfs Register:disk driver 0
Flash drive path:0:/
Test flash drive (file: flash.txt)

flash mount OK
[MODULE_BOOT-LEVEL_INFO]: File system Init success
[MODULE_BOOT-LEVEL_INFO]: KM4 START SCHEDULER
interface 0 is initialized
interface 1 is initialized
interface 2 is initialized

Initializing WIFI ...
RTL8721F[Driver]: The driver is for MP Firmware Enable

Start the massive production flow if the device boots from MP image successfully.

How to Switch Image

When MP is finished, you need to switch the image from MP image to the normal image to verify the application.

Use command AT+OTACLEAR from serial terminal to clear the signature of MP image in order to assign the MP image invalid.

[16:41:35:731]AT+OTACLEAR
[16:41:35:731][SYS-A] [sys_clear_ota_signature] IMGID: 1, current OTA1 Address: 0x00014000, target OTA2 Address: 0x00214000
[16:41:35:731]
[16:41:35:731]+OTACLEAR:OK
[16:41:35:731]
[16:41:35:732][MEM] After do cmd, available heap 318976

Reset the device, then the device will boot from the normal image located in OTA2 field.

[MODULE_BOOT-LEVEL_INFO]: KM0 XIP IMG[0c000000:4c020]
[MODULE_BOOT-LEVEL_INFO]: KM0 SRAM[20040000:3960]
[MODULE_BOOT-LEVEL_INFO]: KM0 PSRAM[0c04f980:20]
[MODULE_BOOT-LEVEL_INFO]: KM0 B00T[20004d00:40]
[MODULE_BOOT-LEVEL_INFO]: KM4 XIP IMG[0e000000:43200]
[MODULE_BOOT-LEVEL_INFO]: KM4 SRAM[0e0443e0:20]
[MODULE_BOOT-LEVEL_INFO]: IMG2 BOOT from OTA 2
[MODULE_BOOT-LEVEL_INFO]: Start NonSecure @ 0xe000115 ...
[MODULE_BOOT-LEVEL_INFO]: VTOR: 20005000, VTOR_NS: 0
[MODULE_BOOT-LEVEL_INFO]: ...