• State TI Thinks Resolved
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 142 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

IWRL6432: RBL fallback scheme if image is corrupted

AndreTseng
Intellectual 2075 points
Part Number: IWRL6432

Hi champs,

        Customer have questions regarding to fallback scheme if RBL detect Image is corrupted.

    

1. What kind of scheme to check wither image is corrupted or not? CRC for each image embedded in each .RPRC? or just overall CRC appended at the end of multicore image .APPIMAGE? 

2. The image format in TRM 4.7 Boot Image Format is inconsistent with TOOLS_BOOT.html of the SDK. In TRM every image in RPRC file has its own CRC. Will RBL check every CRC (including the Meta Header, core Images) in the header is correct?     If yes, it means any bit flip on the meta header or on the image in RSRC format in the flash will load failure? Or just put CRC there, just do nothing?

3.What does RBL do when the loading failure? reloading on next METE partition or just load next appimage from META IMAGE2, META IMAGE3 ...? Any log information?

4. The table of register in the TRM 4.6.2.5.7 show the status which having load failure, Can HOST query these statuses via the UART used to update firmware?

Regards

Andre

  • 0
    TI__Expert 4580 points

    Hi,

    Thanks for your query. We will get back in a couple of days

    Regards

  • 0 in reply to Abhishek Karkisaval
    TI__Genius 12696 points

    Hello,

    1. The CRC of all images should be contained within the meta header of the .appimage as seen in the included diagram

    2. RBL should only check the CRC of the APPSS image according to the Integrity Verification description under 4.4 of the TRM.

    3. Might depend on what is the cause of the loading failure, but I will have to look into this further.

    4. I would assume so, but we also do not have example code of doing this.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 80 points

    Hi Pedrhom,

    About the question 3 and 4. there are the scenario that if I have some actions to do from the Host device when the RBL loads the secondary image(loading the first one failed), for instance, the action can be the recovery for the first image by reflashing.

    How do I know the first image is invalid? or how do I know which image is booted?

    Could you give some suggestions? 

    Thank you.

    Best Regards,

    Tony

  • 0 in reply to Tony Liu
    TI__Genius 12696 points

    Hello Tony,

    Please give me 24-48 hours to get back to you with additional information.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 80 points

    Hi Pedrhom,

    Is there an update on this issue?

    Best Regards

    Tony

  • 0 in reply to Tony Liu
    TI__Genius 12696 points

    Hello Tony,

    If METAIMAGE1 boot image fails, it does indeed continue through images 2 and 3 and so on.

    You can know which image got booted from the boot object.  UINT32 w_MetaimagesParserErrorStatus[8U]; added at the end of Boot object will give more information. Not sure what you meant by “just be reflashed for a successful run” because the boot failure is detected in functional mode and the flashing can be done only in the device management mode. Boot failure is detected in functional mode and the flashing can be done only in the device management/flashing mode.

    Best Regards,

    Pedrhom