This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2634: RPRC format will be deprecated from SDK 11.0.

Part Number: AM2634


Tool/software:

In SDK10.0 release notes: RPRC format will be deprecated from SDK 11.0.

Does this mean that with the SDK11.0 launch, the SDK will no longer include the original RPRC format parsing API functions, right? So I want to know, if my current app is in RPRC format, and if I later update to SDK11.0, the new app can only be in mcelf format. Since the bootloader cannot be updated, OTA cannot upgrade the new format app, right?,

  • Hi 

    Thank for your query allow me to get back on it by end of this week.

  • Hi,

    Do you have some new information about this question?

  • So I want to know, if my current app is in RPRC format, and if I later update to SDK11.0, the new app can only be in mcelf format.

    Yes this is correct we will no longer support RPRC format after SDK 11.0. 

  • Since the bootloader cannot be updated, OTA cannot upgrade the new format app, right?,

    There is a provision for redundant boot in AM263x using which it should be possible to update the boot loader as well.

    This info is also also mentioned in TRM, please read the following section of TRM: 5.4.1.1.1

    With this while you are doing and OTA send both SBL and you application image and flash it t 0xF_0000 location.

  • Since the bootloader cannot be updated, OTA cannot upgrade the new format app, right?,

    I do have another question, is you device already in production? Then in that case its also an option to say on SDK 10.0

  • yes,our device already has been producted based SDK9.0.0, it means that SBL and bootloader can not support to new format

    If the new SDK can not support RPRC format, and this project use new SDK, the past bootloader only support RPRC format and the new bootloader maybe support ELF format, it means we need to provide two application of RPRC and ELF format to OEM due to the past bootloader can not support ELF and bootloader cannot be updated.

    So we need to confirm whether RPRC fromat API will be deleted from SDK11.0. If it will be deleted, our project will have compatibility issues if we change the SDK version

  • yes,our device already has been producted based SDK9.0.0, it means that SBL and bootloader can not support to new format

    Ok got it, one more question how frequently do you update the SDK version?

    If the new SDK can not support RPRC format, and this project use new SDK, the past bootloader only support RPRC format and the new bootloader maybe support ELF format, it means we need to provide two application of RPRC and ELF format to OEM due to the past bootloader can not support ELF and bootloader cannot be updated.

    So we need to confirm whether RPRC fromat API will be deleted from SDK11.0. If it will be deleted, our project will have compatibility issues if we change the SDK version

    Yes RPRC APIs will be removed from SDK 11.0 onwards. You can still update the bootloader using the method I mentined above, do you see any challenge with that.

  • Hi, 

    I wanted to update that the redundant boot support is limited due to the errata: https://www.ti.com/lit/er/sprz488e/sprz488e.pdf

    So this will not be a feasible solution in your system as I had initially proposed.