• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 570 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPS65982: The Regin0 and Regin1 of Flash FW to device setting

daniel
Genius 5095 points
Part Number: TPS65982

Hi team,

I have two questions about update FW by USB memory, please kindly help. Thanks

1. In orderto write SPI ROM by USB memory, it is necessary to set the regions as following?
    Region 0 : 0x2000
    Region 1 : 0x20000

With reference to TI document “TPS6598x FW Update From Embedded Controller Over I2C”.

[Process]

step1:check Regions address = {0x00002000, 0x00020000} (refer to TI document P12)

          const uint32_t rgnPntr1Val[2] = {0x2000, 0x20000};

step2:If step1 is OK, proceed FW writing process, if else issue error.

So to make sure FW update success, we need to ensure to set Regions as 0x2000 & 0x20000? Could we modify the address or even skip this checking process?

2. Does it relate to the low region file? Because we find the regions address may be changed to "Region0:0x2000 Region1:0x12000" in the early Application Customization Tool version.

Thanks

  • 0
    TI__Mastermind 36751 points
    Hi Daniel,

    There are two boot records that contain the pointers to the low and high region. They take up 0-0xFFF and 0x1000-0x1FFF. So the low and high region can’t go there. The other rules are that the low and high region have to start on a flash block boundary (be divisible by 0x1000) and can’t overlap.
    So typically the low region will always be at 0x2000. Then the earliest that the high region could be for a TPS65982 that has max image size of 64k (0x1_0000) is 0x2000 + 0x1_0000 + 0x1000 (boot header) = 0x1_3000.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Genius 5095 points

    Hi Eric,

    When we use old version tool to build .bin file, we can read low region 0x2000, hi region 0x20000, So we can use USB port to update the FW code.

    But when we use new version tool to build .bin file, we read low region 0x1200, hi region 0x20000, So we can not use USB port to update the FW code.

    Does it relate to the low region file? Because we find the low regions address may be changed to 0x1200 in the new version Application Customization Tool, and cause the FW update issue.

    Thanks

  • 0 in reply to daniel
    TI__Mastermind 36751 points
    Hi Daniel,

    Which version of the config tool are you using?

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Genius 5095 points
    Hi Eric,

    TPS6598x Application Customization Tool version 3.10

    Thanks
  • 0 in reply to daniel
    TI__Mastermind 36751 points

    Hi Daniel,

    Are you using the FLrr command to locate where the flash region starts?

    If you are reading back 0x1200 you can enter 0x1200 in the Utilities GUI when doing FW update over USB EP instead of 0x2000.

    Thank you,

    Eric