TDA4VM: Is there any OTA upgrade solution for SBL?

Hi,

In the released SDK, SBL does not have feature to support OTA. If required, you would require to develop it. 

If you are using OSPI as primary boot media, then OSPI supports redundant boot address, you can use it in case booting from offset 0x0 fails. If i remember correctly, the redundant boot address is at 0x40000 offset. Please refer to TRM for more details. 

Regards,

Brijesh

Hi, Brijesh:

Yes, we would like to develop this feature.

Brijesh Jadav said:

In the released SDK, SBL does not have feature to support OTA. If required, you would require to develop it. 

Here is the OSPI boot parameter Table.

I have a few questions:

1. The boot parameter table is stored in MCU_MSRAM0, which means that these two tables must be filled in the code. When the SBL image is damaged, it cannot be started and therefore cannot fill this table anymore.What should be done in this situation?

2.  I saw in another post that it is necessary to use backup boot to start another SBL (Use different media), which should fill the boot parameter table. Is this solution feasible? Are there any simpler methods available? Is the method mentioned in the post not applicable if our current primary boot mode is ospi and we only have one ospi chip? https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1251330/faq-redundant-boot-from-emmc-boot-partitions-on-am62x?tisearch=e2e-sitesearch&keymatch=tda4%20redundant%20boot#

Brijesh Jadav said:

If you are using OSPI as primary boot media, then OSPI supports redundant boot address, you can use it in case booting from offset 0x0 fails. If i remember correctly, the redundant boot address is at 0x40000 offset. Please refer to TRM for more details. 

Hi Wang,

Tongxin Wang said:

1. The boot parameter table is stored in MCU_MSRAM0, which means that these two tables must be filled in the code. When the SBL image is damaged, it cannot be started and therefore cannot fill this table anymore.What should be done in this situation?

This boot parameter table is filled in MSRAM by ROM. So SBL does not need to fill this up. This is information provided from ROM.

Regards,

Brijesh

Well, I'm a bit confused: When the SBL image located at address 0x0 on the OSPi is damaged, how can we switch to the backup read address for booting? Could you please explain the process? Thank you very much.

This is done ROM, ROM verifies the image at offset 0x0 and if it is incorrect, it will try to boot from backup boot address. 

Well if the image is valid at the offset 0x0, it will boot from 0x0 offset. 

Please refer to TRM for more information on backup boot address.