• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 436 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.

TAS5782M: Using the PPC3 to flash settings into the EEPROM independently from the TAS5782MEVM

Emad El-Shaham
Prodigy 20 points

Part Number: TAS5782M

Tool/software:

Hello,

We have designed a PCB around the TAS5782M, the I2C lines are common between the TAS5782M, a 512kb EEPROM, and an STM32.

Now using the PPC3, and after setting our customized parameters, we would like to upload the settings and flash it on the EEPROM, in order to have a standalone operation, so that the TAS5782M can selfboot from the EEPROM without using the motherboard again.

The second question is, how to get the hex file from the PPC3, and in what format, and how to flash this file on the EEPROM.

The third question is, Does the TAS5782M need to be configured to pull the data from the EEPROM by itself or does the STM32 need to orchestrate the data flow between them and how - a detailed answer is appreciated.

Best Regards.

  • 0
    TI__Genius 10305 points

    Hello Emad, 

    Here are my comments:

    • EEPROM takes .h format which is available in the end system configuration of the TAS5782M PPC3 app. Follow the steps of this end system integration choice. This step should provide a .h file that could be dumped to EEPROM. Below is an image of the file dump step to follow on ppc3 and an example of the .h file to expect. I have dumped my .h code to the PPC3 window, you can select to dump the .h file to a file on your pc :

     

    • For the device to receive the preset .h dump file generated and stored in the EEPROM, the IC needs to HW configured correctly, and both i2s and i2c lines should be operational to get the device properly initialized to receive preset configurations.
    • For the method of getting the EEPROM and MCU on your system to work, we don't support this but theoretically, the MCU that controls both the EEPROM and TAS5782M should be able to orchestrate the configuration dump from EEPROM to the IC. 

    Regards,

    Ore.

  • 0 in reply to Ore Ogundana
    Prodigy 20 points

    Hello Ore Ogundana,

    Thanks for the reply, but we still have more questions.

    First of all, regarding the EEPROM .h file.

    Ore Ogundana said:
    This step should provide a .h file that could be dumped to EEPROM.

    We can successfully create the .h file from the PPC3 but we are not sure if it should be encoded in a certain format or is it just a text file encoded in UTF-8.
    Additionally, can the TAS5782M read the .h file directly or it should be encoded or translated before being read by the TAS5782M. And does the I2C address of the EEPROM need to be configured to a certain address so the TAS5782M can find the EEPROM and read the data from it.

    Secondly, 

    Ore Ogundana said:
    the IC needs to HW configured correctly, and both i2s and i2c lines should be operational to get the device properly initialized to receive preset configurations.

    When you say the hardware needs to be configured correctly, does that mean a wiring configuration dedicated to EEPROM communication and configuration since the datasheet doesn't mention that, or do you mean the wiring of the TAS5782M I2C address since it is correctly configured at location 0x90 and we were able to successfully boot the board and the TAS5782M so the hardware should be correctly configured and the I2C lines are correctly wired and I2C devices are successfully detected at their addresses by an external MCU.

    Finally, since the MCU orchestration is not officially supported and documented, what is the TI approved way of getting the EEPROM and TAS5782M to communicate with each other.

    Best Regards.

  • 0 in reply to Emad El-Shaham
    TI__Genius 10305 points

    Hey Emad,

    To answer the first question:

    • Ultimately the eeprom and IC shouldn't share the same address number to avoid confusion in your setup. Section "9.3.9 I 2C Communication Port " of the DS says only I2C protocols are supported, find an example script format in the section "9.3.4.1" of the DS. It shows an example of the I2C protocol required by the device:

    To answer the second:

    • I mean the wiring for the audio TAS572M IC.

    Regarding the remaining EEPROM questions:

    • Unfortunately, TI-AUDIO doesn't support EEPROM application. It is up to the customer to decide how to setup their system with our part and use the guide provided by the DS.

    Regards,
    Ore.