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.

EVMK2G Audio Processing Reference Design



Hi,

I'm bumbling my way through setting up my EVMK2G eval module, the SDK, PDK, CCS, etc, etc, and have hit a snag.

Basically, I'm trying to follow the Audio Processing Reference Design guide found here:

However, it seems that the document is referencing pdk 1.0.1 instead of 1.0.3 (makes sense since the latter was released just this October).

I've got all the references and workspace variables in order, but it seems that the project can't find 'i2c_soc.c'.  Indeed this file is not included with PDK 1.0.3.  Before I go messing around with the source/linker, is there a straight forward solution to this that I can take?  I don't know what this file is used for, so I don't know what would happen if I remove it from the source, etc.

  • Justyn,

    The file I2C_soc.c resides under pdk_k2g_1_0_3\packages\ti\drv\i2c\soc\k2g.

    The Audio reference design is scheduled to be integrated in the Processor SDK RTOS 3.2 that will release before the end of the year so you will not need to figure integrating it in the latest version of the the SDK.

    In the mean time, you can create the McASP LLD driver example  by running the following script from pdk_1_0_3\packages.

    pdkProjectCreate.bat K2G all little mcasp dsp

    This will create a CCS Project by the name MCASP_Audio_evmK2G_c66ExampleProject under myExampleProjects directory. Import the project in CCS. this project demonstrates

    McASP loop back from Line in to Line out. Build and test it.

    Replace audioSample_main.c with audioEq_main.c and audioSamplie_io.c with audioEq_filtering.c. You may still need to fix some header path. I will try to replicate this and give you the updated files that you need.

    Regards,

    Rahul

  • Justyn,

    To simplify using the TI Design with the latest Processor SDK RTOS, I have created the following package.

    Audio_Equalization.zip

    Please unzip this package in the following directory pdk_k2g_1_0_4\packages\ti\drv\mcasp\example\evmK2G

    Now you can create a CCS project similar to any driver example in the PDK. You can setup the PDK environment setup and invoke the PdkProjectscript using :

    pdkProjectCreate.bat K2G all little mcasp dsp

    this should create a project called MCASP_AudioEQ_evmK2G_c66ExampleProject in the myExampleProjects directory as I had indicated in the earlier post. you can then import the project in CCS and build and run it.

    Regards,
    Rahul

  • Once I got all the licensing and set up done correctly, the loopback worked perfectly.

    Thanks so much for taking time to answer my simple questions.
  • No problem. Glad to know that you have this working.

    Regards,
    Rahul
  • Actually, I take that back...

    Because I'm completely new to the TI SDK, when I generated the example projects as per your instructions, I didn't notice that there was already a loopback example that comes with the SDK. I was following the above mentioned PDF which recommends downloading the filter example from the github repo.

    So when I built the examples, and got through the CCS licensing issue (turns out there was none), I was using the provided AIC31_Stereo_Loopback example instead of the EQ example, which is all I really needed. I have my own libraries I need to drop into the loopback, so I don't really need all the filter stuff in the github code, or your attached .zip, basically the EQ loopback stuff.

    The audio EQ example you gave me errors out when I run it on the DSP with the following:

    EDMA driver initialization PASS.
    mcaspCreateChan for McASP2 Tx Failed

    When the program gets to BIOS_start().

    As I mentioned above, my development doesn't depend on the EQ code, only the loopback code that I didn't initially realized was already an example program. I'm just pointing this out so that I don't leave this thread as "solved" as I naively thought above.
    This probably won't matter soon when the new SDK comes out, I'm guessing.
    Thank you again for your help; I'm asking easy questions, but my development schedule is ridiculous so I need all the help with a new platform I can get.

    Keep being awesome.