• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 646 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.

TLV320AIC3256 file format

Rishabh Jain
Intellectual 810 points
Other Parts Discussed in Thread: OMAP-L138, TLV320AIC3256

Hi All,


We are having our own OMAP-L138 processor based customized board in which we are integrating TLV320AIC3256 codec chip through i2c and we are still in the process of doing that.

One doubt I have i.e in TLV320AIC3256 chip we need to download software to run.

But when we build example through PurePath GDE, it generates image base_main_rate.cfg in this file format.

So in which format, file has to be transferred to TLV320AIC3256.

As by referring to the following link:-

https://gitorious.org/ti-codecs/pages/MkCFW6x

it says we need to convert it to *.bin file.

But in the documentation of PurePath tool, such kind of information is not mention.


So please guide us on this.

Regards

Rishabh Jain

  • 0
    TI__Mastermind 46195 points

    Hi Rishabh,

    In PurePath Studio GDE, go to Tools > Options > Build and click Generate Device Driver Interface and Generate Driver Code. This will generate header files when compiling.

    Regards,

    J-

  • 0 in reply to J-
    Intellectual 810 points

    Hi J-,

    Thanks for the reply.

    You are totally correct the way you mentioned above and I am also doing the same way.

    But the outcome of the above steps generates base_main_Rate8.cfg file name along with one folder in which various files are generated with extensions of *.asm, *.lst, *.image, *.debug.

    But my question remain same as asked before that when I run my board it detects AIC3256 device through I2C interface and while booting in kernel it search for some *.bin file to download in the AIC3256 code chip.

    So my question was that, in which format ( *.cfg or *.bin) AIC3256 chip needs to download file in it to run, as the output of the test examples compiled through PurePath does not generate *.bin file.

    Hope I made my self clear and please reply for any queries.

    Regards

    Rishabh Jain

  • 0 in reply to Rishabh Jain
    Prodigy 20 points

    Hi Rishabh,

    The firmware image (.bin)  for the AIC3256 ALSA codec driver can be built using the mkcfw tool.  Please refer to the page below for details:

    https://gitorious.org/ti-codecs/pages/MkCFW6x

    http://e2e.ti.com/support/data_converters/audio_converters/f/64/t/266169.aspx

    REgards,

    hari

  • 0 in reply to Harikrishna Rajagopala
    Intellectual 810 points

    Hi Hari,

    I agree with your point.

    But this thing firmare image (.bin) for AIC3256 ALSA codec driver has not been mentioned any where in the datasheet of AIC3256 or PurePath.

    Can you send me any link where such thing is written or any document?

    Regards

    Rishabh Jain

  • 0 in reply to Rishabh Jain
    Prodigy 20 points

    Hi Rishabh,

    There is no additional documentation other than those that are part of the mkcfw package itself.  The firmware binary file was designed specifically for  the Linux ALSA driver where there is a need to avoid recompiling the kernel each time you change the processflow.   Using the Linux firmware load mechanism allows you to quickly change your processflow, rebuild only the firmware binary, place it in your filesystem and have the OS pick it up and load it.  

    As such the format used  has nothing to do specifically with the AIC3256.  If you don't mind recompiling the kernel each time your process flow changes, you can generate the driver header files as described by J- and include them into the driver sources.  You can then use low-level i2c API or the regmap API to send those to the device.

    Regards,

    hari