TPS65987D: About creating a revised full flash image

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987

Tool/software:

Our system uses TPS65987D. I wanted to make some changes to a previously created project, and tried to load the project file using the GUI tool and generate a binary file, but the "project firmware" file did not exist. Please refresh the General Settings tab and try again. ” Firmware version: 0000.00.00
I get a message that the allocated application configuration size is 0x0 (0 bytes), but it's an error.
Does this mean that in addition to the project file, we also ne ed to load the Low region file that was generated earlier?

  • Hi Yamamotoju,

    If you try making a new project with the part you are using 987DH/DK, that field should be populated.

    Select the specific part you are using.

    Confirm the version that is used, and then select the "Change File" button. It should take you to the file location of the "Firmware Base Image" for the GUI tool. You can find the file path to the "Firmware Base Image" that you should be using for the part.

    Once you have found this, re-open your previously created product, and navigate to and load the "Firmware Base Image" you found.

    In the images, I selected the option for TPS65987DH. Make sure you select the correct part in the first step, otherwise the binary file generated may not work.

    Thanks and Regards,

    Chris

  • Thank you for understanding [Firmware Base Image].
    I would like to continue to check the "TPS65987_88_F707_10_10.bin" loaded with [Firmware Base Image] and the menu "②.low-region (full header)" and "③low-region (minimal header)" when generating the binary file. ” can be considered files with the same content?
    There is a description of (I2C/PBMx) in ③, but is it necessary to use ② and ③ differently?

  • Hi Yamamotoju,

    I would like to continue to check the "TPS65987_88_F707_10_10.bin" loaded with [Firmware Base Image] and the menu "②.low-region (full header)" and "③low-region (minimal header)" when generating the binary file. ” can be considered files with the same content?

    No, I don't think what you are saying here is correct.

    Above is an image of how the (1)Full Flash is formatted and looks. It contains two regions (0 and 1) which are duplicates and are primarily used for redundancy and for safe flash updates.

    The "Low Region"(2)(3) options basically take half of the Full flash by only having one region. The difference between the two is mainly formatting related to sizing, but they are essentially the same. You should always be using the minimal header.

    If you look at a single region, you'll notice it is split into two parts, a ID, Header and Configuration section, and a Patch code section. The "Base Firmware Image" is primarily used to update the patch section, while the settings you configure in the GUI is primarily used to update the Configuration section.

    So, the base firmware image is a part of 2 and 3, but is not "the same content"

    There is a description of (I2C/PBMx) in ③, but is it necessary to use ② and ③ differently?

    2 and 3 are basically the same, you should always be using 2.

    Thanks and Regards,

    Chris