• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 427 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR6843AOP: Firmware Update Failures using SBL

JOH MINWOO
Prodigy 90 points
Part Number: IWR6843AOP

Tool/software:

I am using the IWR6843AOP and attempting to implement FOTA via the SBL solution.

Although I successfully copied the firmware binary file using the SBL_transportDownloadFile() function's QSPIFlash_singleWrite(), the image loader is not functioning correctly.

Are there any specific modifications I need to make?

Best Regards,

Minwoo

  • 0
    TI__Mastermind 19780 points

    Hello.

    What specific issue/error are you encountering when loading the image?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points

    Thanks for reply.

    The process is no longer proceeding, although no specific error message has been generated. It seems there is an issue at the SBL_multicoreImageParser stage of the SBL_bufferMgmt function.

    Below are the differences identified when comparing my code with the reference code.

    before SBL_multicoreImageParser()

    after SBL_multicoreImageParser()

    Best Regards,

    Minwoo

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points

    + 

    Additional anomalies include the SBL_BUFFER_PARSER_RPRC_DWLD function running only once and not repeating further.

    When downloading a file with a size of 0x9b984 through the UART (XMODEM) of the SBL reference code, it becomes 0x9ba00. I am not sure where the extra 124 bytes came from.

  • 0 in reply to JOH MINWOO
    TI__Mastermind 19780 points

    Hello Joh.

    What specific code changes did you make to the SBL example, and what output are you getting on the terminal when running your custom example?  I would confirm that you have selected the 1k option when trying to send the binary via XMODEM on tera term.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 90 points
    Hi Santosh,

    I added SPI communication code to the SBL example and used UART only for debugging purposes. (I did not download the firmware file using XMODEM 1K,

    I just used XMODEM 1K to compare the firmware file size.)

    In the SBL_imageFlasher function, I wrote the entire firmware data to flash memory in 63-byte segments via SBL_transportDownloadFile SPI.

    There were no modifications made to the SBL_imageLoader function, but it seems there is an issue when loading the input buffer to RAM (such as the magic word value constantly changing).

    The buffer size modification details are as follows.

    Best Regards,

    Minwoo

  • 0 in reply to JOH MINWOO
    TI__Mastermind 19780 points

    Hello.

    Let me look into this and will provide an update by the end of the day Monday.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Mastermind 19780 points

    Hello.

    Apologies for the delayed response.  From looking at your changes, I would make sure that you keep the parameters from the first image the same as the original demo.  Those macros are primarily involved in setting up flash in a way that makes it clean for the SBL to write the new image into SFLASH.  In terms of the loading, I would also make sure that the load address is correct; are you loading the image in by interrupting the countdown or just trying to boot the factory image?  The original code assumes the backup image is in P4(0x00180000U), and the main image at 0x40000, so I would just make sure that you have updated the flashing code to account for the changes in SFLASH address.

    Sincerely,

    Santosh