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.

TAS2557: Generate Header-file with PurePath Console 3

Part Number: TAS2557

Hello!

I have the following setup: A TAS2557EVM with PurePath Console 3 and a TAS2557 device embedded in my own breadboard. The embedded TAS2557 device is using I2C and is hooked up with the I2C-probes on the EVM-board. My embedded TAS2557 is using 22050Hz, 16bit and is acting as a master on I2S.
I am able to generate configuration files when dumping the binary file, but I am not able to generate header files for my embedded program. Is there a way to setup my embedded TAS2557 using TAS2557EVM and PurePath Console 3, and also generate header files instead of .cfg-files, which I have to manually type as I2C commands in my embedded software. 

I would also like to use PurePath Console to tweak some parameters and listen to the changes on my embedded device. And when im satisfied with the result, empty the configurations and save as a header file, Is this possible?

Thank you in advance,
/Viktor

  • Hi Viktor,

    Unfortunately at this moment it is not possible to save the changes made over I2C command controller through the header/cfg files generator option.
    We'll take this as a suggestion as it would be a good additional tool for device configuration, however I couldn't assure that this is going to be implemented or when it could be available.

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

    Okay, that sounds good.
    Is it possible to generate a header-file from a .cfg-file in PPC3 or any other script tool supplied by TI?

    /Viktor

  • Viktor,

    Currently there is no tool available to generate a header file out of a cfg file.
    Header files contain additional content like checksum along the configuration. The only way to generate header files at this moment is through PPC3 end system integration panel.

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