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.

TPS65986: App Config Data Table too large error.

Part Number: TPS65986

We are completing FW features, and ran into an issue.  When I try to generate the .bin files, the config tool says: "The size of the app config data table generated by this project (0x406 bytes) is larger than the allocated region supported by firmware image (0x400 bytes).  Save operation has been aborted."

 

I worked around this problem by removing 2 register writes for 2 app configs (minor features for LED state).  But, concerned if we have to make any other changes, we may go over this limit again.

 

Can you provide details on what this limit is?  Is there anyway to change it in the config tool?  We are trying to change the behavior of the TPS65986 based on some HW settings, so we have 4 different data config sets.

  • Hi Eric S,

    The maximum size for the app config supported by the TPS65986 is 64kB. If too many different app configs are added to the same image, it can exceed 64kB like you are seeing. We cannot change this in the config tool since the 64kB limit is a HW memory limitation of the TPS65986. The following image shows how the SPI-Flash is organized to store the TPS65986 app config:

    If this answers your question, PLEASE select This resolved my issue


    Thank you,
    Eric

  • Eric, I understand that the App Code limit is 64kB, but this "App Config Data Table" referenced by the tool, and generated from their customized project appears to be limited to 0x400 Bytes, which is 1024 Bytes.... only a very small portion of the 64kB Application Code space. I presume most of the Application Code space is our FW load, I think the question is whether they can change the allocation of memory for their specific customized use to allow the "App Config Data Table" to be larger than 1024 Bytes, to allow their multiple data config sets?
  • Hi Eric S.,

    The actual limitation here is in the RAM memory buffer allocated by the firmware.  These devices have program and run-time data stored in 64K of shared program/data RAM.  The 1K buffer for app config data is set by the linker at build-time of the firmware.  Theoretically this can be changed by rebuilding the firmware, but it would require removing something else from the firmware.  There is no perfect number that will meet every customer's needs, but we have generally found that the 1K of app config space is sufficient for most applications.

    One thing that you may try is reducing the size of the billboard strings on the general settings tab.  These are stored in the app config table and are 1 byte/character, so you can buy a few more bytes by just reducing the size of these strings. 

    There is nothing that can be done in the tool to increase the available app config size, because is this determined at compile-time of the firmware.

    Regards,

    Steve