Lup Yuen Lee 李立源 @lupyuen@qoto.org

#BL602 Bootloader uses XZ Compression when installing Application Firmware

https://lupyuen.github.io/articles/boot?9#install-application-firmware

#BL602 Bootloader will rollback the Application Firmware in XIP Flash Memory when there's a problem

https://lupyuen.github.io/articles/boot?8#inside-the-bootloader

#BL602 Bootloader loads our Application Firmware into XIP Flash Memory ... And starts the firmware

https://lupyuen.github.io/articles/boot?7#inside-the-bootloader

Inside the #BL602 Bootloader

https://lupyuen.github.io/articles/boot?4#inside-the-bootloader

What is the #BL602 Boot2 Bootloader? How is it used for Secure Firmware Updates?

https://lupyuen.github.io/articles/boot?3

Now writing about the #BL602 Bootloader ... Then heading back to Rust Wrappers for BL602 IoT SDK

https://lupyuen.github.io/articles/boot?1

Interesting...

🤔

Roast Korma Kampong Chicken ... No Karma Chameleon 😂

https://www.fairprice.com.sg/tips/healthy-living/do-you-know-your-chicken/

https://www.assufi.com/product/kurma-mix/

#BL602 IoT SDK defines the ROM Driver API Functions at 0x2101 0800 ... Located in the BL602 Boot ROM

https://github.com/lupyuen/bl_iot_sdk/blob/master/components/bl602/bl602_std/bl602_std/StdDriver/Inc/bl602_romdriver.h#L279

Remember the Table of #BL602 ROM API Functions? Here's an interesting project that wraps the BL602 ROM API with #RustLang

https://github.com/9names/bl602-rom-wrapper/blob/main/src/rom_lookup.rs

Some parts of #BL602 Bootloader are located in ITCM Cache Memory (instead of XIP Flash) ... Maybe that's why the Bootloader is able to overwrite itself in XIP Flash Memory 🤔

https://github.com/lupyuen/bl_iot_sdk/releases/download/v8.0.2/bl602_boot2.map

Linker Script for #BL602 Bootloader says that some System Functions will be placed in ITCM (0x2201 0000) ... Like Global Register (GLB), Power (PDS), XIP Flash and eFuse 🤔

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2_flash.ld#L67-L95

#BL602 Application Firmware also has a Table of ROM API Functions ... But it's located at 0x4200 C000 (DTCM) 🤔

https://github.com/lupyuen/bl_iot_sdk/releases/download/v8.0.1/sdk_app_blinky.map

#BL602 Bootloader has a Table of ROM API Functions at 0x2201 0000 (ITCM) ... How is this table used? 🤔

https://github.com/lupyuen/bl_iot_sdk/releases/download/v8.0.2/bl602_boot2.map

Matching the #BL602 Bootloader Code ... With the Partition Table that's flashed to BL602 🤔

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2.c#L226-L269

Where does #BL602 Bootloader get the AES Encryption Key? From the eFuse Hardware!

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_port.c#L184-L209

#BL602 Bootloader writes Application Firmware to XIP Flash Memory

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2.c#L226-L269

#BL602 Bootloader installs the Application Firmware

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2.c#L271-L313

How #BL602 Bootloader starts the Application Firmware

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2.c#L509-L571

#BL602 Bootloader installs the Application Firmware ... With eFuse Protection (optional)

https://github.com/lupyuen/bl_iot_sdk/blob/master/customer_app/bl602_boot2/bl602_boot2/blsp_boot2.c#L381-L507