Dear Dialogue support,
Our client is seeking a solution to boot into production test mode by triggering a software switch in their firmware. Can you please check if the following proposal is feasible?
1. burn boot loader combined with production test function into OTP - need to integrate bootloader and production test together into a single binary
2. burn application firmware into flash (2 banks)
3. when booting, normally boot into application firmware if a special flag (boot_into_production) is not set in the SRAM
4.while running application firmware, writing into certain UUID triggers the boot_into_production flag is set in the SRAM and a reboot is initiated
5. bootloader check the boot_into_production flag is set and boot into production test image
Is it possible to implement above procedure? What's the main catch if there is a way?
Looks like the key issue is how to preserve the boot_into_production flag after the reboot? Is there a solution to it?
Thanks for your attention,
uta_lc
Hi uta_lc,
Be aware that integrating the secondary bootloader and the production test together into a single binary, this will be a little bit tricky. If you store the boot_into_production flag into the SRAM and when booting from otp, the firmware will be mirrored into the SRAM, so you will not be completely sure that the flag’s value will not be overwritten. I suppose that the safest way to do that is to store the value of the boot_into_production flag into the SPI flash.
Thanks, PM_Dialog