• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 63 subscribers
  • Views 650 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.

TPS25750: MCU memory requirement

Ben Genereaux
Intellectual 1040 points

Part Number: TPS25750

Hi team,

We have a customer trying to determine how much flash space needs to reserved in their MCU to configure the PD controller.

The technical reference manual discusses application binaries and patch bundles. Are both of these required to be loaded to the device on every boot up or is only the application customization required?  

How much flash space needs to be reserved in the MCU? The recommended size of EEPROM in the data sheet was 32KB.  Is it possible that the application binary will be much smaller than this and that is all we need?

Thanks,

Ben

  • 0
    TI__Mastermind 37635 points

    Hi Ben,

    Ben Genereaux said:
    The technical reference manual discusses application binaries and patch bundles. Are both of these required to be loaded to the device on every boot up or is only the application customization required? 

    A patch bundle contains the "App binary" and a patch binary. The App binary contains the configuration, while the patch binary modifies default app firmware contains things like bug fixes. Each time you boot, you need to provide both, so to answer your question, you need to load the patch bundle every time during boot.

    Ben Genereaux said:
    How much flash space needs to be reserved in the MCU? The recommended size of EEPROM in the data sheet was 32KB.  Is it possible that the application binary will be much smaller than this and that is all we need?

    If you are writing the patch bundle from an MCU over I2C, you only need the low region. This can limit the reserved size to 16KB. The full flash binary generated for the EEPROM from the GUI contains the low region and high region. The high region is a duplicate of the low region and can be used as a backup incase the low region fails boot.

    Thanks and Regards,

    Chris

  • 0 in reply to Christopher Lim1
    TI__Intellectual 1040 points

    So from what I understand here, we need to store more than just values for all configuration register/values on the MCU flash? Why does the EEPROM need the additional files for redundancy but the MCU does not?

  • 0 in reply to Ben Genereaux
    TI__Mastermind 37635 points

    Hi Ben,

    Ben Genereaux said:
    So from what I understand here, we need to store more than just values for all configuration register/values on the MCU flash?

    Yes, the "patch binary" must also be included, which is separate from the configuration values.

    Ben Genereaux said:
    Why does the EEPROM need the additional files for redundancy but the MCU does not?

    It is most likely due to it being easier to update the MCU if patch fails. These requirements come from how the boot sequence is defined.

    Boot can change depending on the device configuration.

    If the PD is booting from an EEPROM, it tries loading the low region, and if the low region fail verification and was corrupted, it will try loading the high region.

    If the PD is booting from an MCU over I2C, it will raise a "ready for patch" interrupt flag, that indicates to the MCU that it can load the patch bundle over I2C. If the patch fails verification, the MCU will need to handle the failure.

    Thanks and Regards,

    Chris