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.

TLV320AIC3254EVM-K: Combining PurePath Files into a Single Script

Part Number: TLV320AIC3254EVM-K
Other Parts Discussed in Thread: TLV320AIC3254

I am working with the TLV320AIC3254 and am utilizing PurePath studios to generate the code. I have successfully generated the code using this tool which results in four files of the following types: .pfw; .cfg; .image; and .lst. I am unsure how to combine multiple generated code files into a single script file to flash the board. My intent is to have multiple audio inputs that are selected based on a manually selected mode (VAD/VOX, PTT, etc.). I installed Code Composer Studio, however this device was not listed in the resources. Please let me know if you have any suggestions on combining multiple PurePath files in order to configure the board.

  • Hello Anna,

    Are you asking how to load the miniDSP FW based on the PPS process flow you've created while using the EVM?  Or are you asking how to load this information in your end-system integration with a host processor?

  • Hi Collin,

    I am more concerned with the end-system integration. I am relatively new to developing systems such as these, so I am not too familiar with what host processor would be used. I am developing a mobile system, and I was hoping to implement toggle controls that would interact with the codec's interprocessor to trigger interrupts that are able to change microphone inputs, VOX/PTT operations, and volume control. I am also concerned that PurePath only allows one input and one output in a process flow, therefore I will have several process flows to generate code from.

    Please let me know your thoughts,

    Anna

  • Update on the project: I will only be copying one PurePath script to the codec. This being said, is it possible to have an external volume control interact with the codec instead of the digital control in the GDE?

    Thank you,

    Anna

  • Hi Anna,

    I'm not immediately sure, and will have to check with some other team members.  It may take two or three days.

  • Hi Anna,

    Code generation for device interfacing has to be enabled to generate the .c/.h files.

    You can set these options by going to Tools => Options and then from the Build Panel, select the ‘Generate Driver Code’ option as shown in the screenshot.

    Building with these options will generate two files - pps_driver.c and pps_driver.h - in the process flow folder (i.e. where the .pfw file resides).

    Please let us know if you have any further questions.

  • Thank you, that was very helpful! I did not see that option. Do you have a TI microprocessor that you recommend to assume the host processor role? Since the codec works with audio, the processor would need to be fast but I am desiring low power as well.

    Anna