Part Number: F29H85X-SOM-EVM
With the flash-based SBL, only CPU1 and CPU3 images are loaded. As CPU2 may be integrated with the CPU1 or CPU3 application, can its application also be included in the .bin file?
Regards,
Shashank
Part Number: F29H85X-SOM-EVM
With the flash-based SBL, only CPU1 and CPU3 images are loaded. As CPU2 may be integrated with the CPU1 or CPU3 application, can its application also be included in the .bin file?
Regards,
Shashank
Another doubt: In the flash-based SBL, the image is loaded into flash using FRI1 – RP0 (0x1000 0000), from where the application is accessed. why the received image isn't loaded via FOTA using FRI3 – RP0 (0x1060 0000)?
Regards,
Shashank
Hello,
Yes, the CPU2 application can be bundled with the CPU1 application. CPU2 has no flash access, so CPU1 is responsible for copying CPU2's code into RAM and then taking it out of reset.
In the flash-based SBL, the image is loaded into flash using FRI1 – RP0 (0x1000 0000), from where the application is accessed. why the received image isn't loaded via FOTA using FRI3 – RP0 (0x1060 0000)?
Are you using BANKMODE 1 or 3? The SBL will download the application to the inactive region, then update BANKMGMT to perform the swap. When programming in FOTA mode you still use the 0x1000_0000 address range.
Best,
Alex
Hi Alex,
The FOTA example is available in f2985x_1_02_01_00. The device is in HS-FS mode, and flash operations for the incoming image in Bank Mode 1 are performed via FRI1-RP0 (0x1000 0000). Should these operations instead be performed using the FOTA region (FRI3-RP0 – 0x1060 0000)?
Regards,
Shashank
Hi Shashank,
Yes, when updating using FOTA mode data should be programmed to the 0x1060_0000 address range. In the F29 Flash API, this is done by using Fapi_getUserConfiguration with FOTA_Image as the FOTAStatus parameter. When in FOTA mode, the API will take in active region addresses but program to the inactive region. For example, passing address 0x1000_0000 in FOTA mode will program data to address 0x1060_0000.
Best,
Alex