• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 28 subscribers
  • Views 429 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.

Original question:

TAS2557: Microcontroller implementation

TAS2557: TAS2557 system integration: Header file generation / Overview of files generated

Andreas Paulin
Prodigy 235 points
Part Number: TAS2557
Other Parts Discussed in Thread: , TAS2563, TAS2562

Hello, TI team,

we have almost finished sound adjustments with the TAS2557EVM for our amplifier project now and

will start system integration now.
The job is to transfer all the configuration data, coefficients plus the encrypted DSP code via I2C to the TAS2557. That is understood.
1. I cannot find header files amongst the generated data. Is the header generation still nonfunctional?
2. If so, is there an external tool available to generate a proper header file?
3. PPC3 is generating a vast amount of files. Is there any documentation, what all these files are used for?
4. Where do i find the mentioned 'encrypted DSP code' and how to transfer it to the TAS2557?

Kind regards

Andreas Paulin

  • 0
    Prodigy 235 points

    One more crucial question:
    How much memory space do i have to calculate in the MCU for all the TAS2557 configuration data?
    Approximately?

  • 0 in reply to Andreas Paulin
    TI__Guru** 104555 points

    Hi Andreas,

    Have you already got through this AppNote?: https://www.ti.com/lit/an/sboa239/sboa239.pdf

    The software support for TAS2557 has binary and cfg files. Our newer devices like TAS2563 and TAS2562 already have header file support as well.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • 0 in reply to Ivan Salazar
    Prodigy 235 points

    Hello, Ivan,

    thank yo for the fast reply. No, i haven't known that appnote before. I think it will
    shed some more light upon the MCU integration job. I will read through it and get back later, if there
    are more detailed questions about it.

    Best regards

    Andreas Paulin

  • 0 in reply to Andreas Paulin
    Prodigy 235 points

    No, not all is clear - One more crucial question:

    We are using the TAS2557 in a standalone amplifier, no android, no powerful core CPU.
    So i need to select a small MCU to just load all the DSP program and the configuration data into the TAS2557.
    This MCU will contain all the needed data in it's Flash ROM.

    How much memory space do i have to calculate in the MCU for all the TAS2557 configuration data?
    Approximately?

    Best regards

    Andreas Paulin

  • 0 in reply to Andreas Paulin
    TI__Guru** 104555 points

    Hi Andreas,

    A tuning mode configuration results in a binary file of ~18kB. Additionally you need to include mute and unmute sequences (3 or 4 I2C commands each).
    You can generate a specific bin file by configuring your required settings in PPC3 and export the config files.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • 0 in reply to Ivan Salazar
    Prodigy 235 points

    Hi, Ivan,

    thank you for your prompt answer. I have read the sboa239.pdf and it explains the dumping procedure quite detailed.
    I can find the binary (afaik for android API) and the cfg files.
    I'd  prefer to concentrate on interpreting the cfg files according to the script specs in the PPC3-Manual, Appendix B (Microcontroller Code Implementation).
    That would mean to write some additional script-extractor software which turns script lines like this:
    w 98 7f 64
    w 98 46 02
    w 98 00 01
    w 98 08 a5
    > 5b
    > 51
    > 49
    ....
    into binary data i just send out to the I2C on address 0x98 eg. like this:

    0x7f, 0x64, 0x46, 0x02, 0x00, 0x01, 0x08, 0xa5, 0x5b, 0x51, 0x49...
    Ivan, can you point me to some PC software snippet which does the job? I cannot believe that hundreds of developers
    out there implementing a TAS2557 are doing the job by hand..

    Kind regards

    Andreas Paulin

  • 0 in reply to Andreas Paulin
    Prodigy 235 points

    this post is obsolete now.

    Andreas Paulin

  • 0 in reply to Andreas Paulin
    TI__Guru** 104555 points

    Hi Andreas,

    You can start a new thread related to this one if you consider questions are not directly related to the original post.
    Regarding the script format changes, as mentioned the most recent released devices support header file export already. For older devices a parser can be used to change the format from cfg file.

    Best regards,
    -Ivan Salazar
    Applications Engineer - Low Power Audio & Actuators

  • 0 in reply to Ivan Salazar
    Prodigy 235 points

    Hi, Ivan,

    thank you very much for your support and your tips. It helped a lot.
    I have written a little cfg-to-hdr parser and we will commence system integration next year.
    I'll get back to you if there should arise new questions.

    I wish you a merry christmas and all the best for 2020. Advance happy new year!

    Kind regards

    Andreas Paulin