Table of Contents
Advertisement
The IVAS Device needs access to the following file structure to be served from the server:
DOWNLOAD FILE NAME
IvasUserConfig.txt
IvasBootloaderConfig.txt
IvasApplication.bin
IvasBootloader.bin
Table 10: IVAS Pythom scripts – example
6.4 Flash Programming
IVAS Device can be programmed by,
1. Flash Stage1Boot_HW_R1.bin in address 0x08000000
2. Flash MainBoot_HW_R1_signed.bin in address 0x08020000
6.5 Bootloader Execution Flow
Following steps describes Bootloader execution,
1. Bootloader will start execution from Stage-1 bootloader
2. Stage-1 bootloader will jump to Main bootloader
During Boot up, if external flash is corrupted; same will be erased
3. Main bootloader will POST startup info to the server
1. {"$(DEVICE_MAC_ID)":"{\"$(DEVICE_MAC_ID)\":\"0.2.1\"}"}
2. Here 0080E1000000 is IVAS device mac id and 0.2.1 is Bootloader version.
4. Application check
1. If valid application is available in IVAS, Main bootloader will jump to the application
2. If no valid application is available in IVAS, Main bootloader will remain
5. Update request from user
1. Main bootloader will request for update request from user with IvasUserConfig.txt
2. Download of IvasApplication.bin/IvasBootloader.bin/IvasBootloaderConfig.txt depends on IvasUserConfig.txt
file content,
3. If the flag is set true , corresponding file will be downloaded. If the flag is set false, corresponding file will not be
downloaded.
Note: Do not enable more than one flag of AppUpdate,BootUpdate and BootConfig. If more than one flag is
enabled NO download will be performed.
FILE CONTENTS
{
"Boot":
{
"AppUpdate" : true,
"BootUpdate" : true,
"BootConfig" : true
}
}
{ "http": { "ip" : "192.168.178.100", "port" : 8000 } }
DESCRIPTION
User update request
Bootloader Configuration
Application firmware
Bootloader firmware
18
Advertisement
Table of Contents
