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.

  • Resolved

[FAQ] TLV320AIC CODECs: How to transfer a completed design from Pure Path Studio (PPS) into the TLV320AIC3254 device?

Mastermind 39175 points

Replies: 1

Views: 375

Once we've completed a process flow using PPS, how do we transfer the design into the TLV320AIC3254 device?

Regards,
Collin Wells
Precision ADC Applications

  • By default, PPS-GDE generates the application as a CFG file. This file format is 
    described in the document titled "AIC Script Language" and can be found in the 
    PPS-GDE download folder (http://pps.ext.ti.com). The folder contents are visible 
    only to users whose access to PPS-GDE has been approved. One option is for the 
    user to write their own utility to convert this CFG file to whatever format they
    need to integrate the processflow into their microcontroller code.

    PPS-GDE can also optionally generate its output as a C header file. This 
    functionality can be enabled by checking
    Options->Build->Generate Generate Device Driver Interface

    Build your code and look for a file named base_main_Rate<FS>_pps_driver.h
    where <FS> is the sample rate for which you are generating your code (for example,
    base_main_Rate44_pps_driver.h for 44.1 kHz). You need to download the contents 
    of the array named REG_Section_program[]. Each entry in this array is a pair
    of numbers:
        {offset, value}

    Normally the <offset> lies between 0 and 127. In these cases, simply write <value>
    to the register at <offset> using I2C or SPI. Note that the register page is opened
    implicitly (by writing to register at offset 0) as part of the download sequence 
    in this array. While this means that the driver
    need not track the open page, it also means you cannot change the order in which
    the array is downloaded. (In the AIC3262 family of devices, the book is also
    opened implicitly by writing to register at 127 and the driver need not track the 
    currently open book during download.)

    There are two commands that are signalled by an <offset> greater than 127. 
    Unlike the other pairs, these are not literals writes to the device, rather they 
    signal that the driver should take a specific action at that point in the array. 
    The associated <value> becomes a parameter to the command as described below.

        offset == 254 ==> Delay by <value> milliseconds
        offset == 255 ==> Switch to downloading from a different array
                                                      <value>==0 usually means download miniDSP_A_reg_values[]
                                                      <value>==1 usually means download miniDSP_D_reg_values[]

     

    Regards,
    Collin Wells
    Precision ADC Applications

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.