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.

CCS/EVMK2G: Converting the audioAnalogLoopbackTest project into a CCS project

Part Number: EVMK2G
Other Parts Discussed in Thread: AUDK2G, TIDEP-0088

Tool/software: Code Composer Studio

Hi,

What should I do to convert the audioAnalogLoopbackTest project into a CCS project?

Thank you and best regards,

Adam

  • Hi Adam,

    Download Processor SDK RTOS and execute the following commands:
    ykovachev@lin-0373:~/ti/pdk_k2g_1_0_10/packages$ source pdksetupenv.sh
    ykovachev@lin-0373:~/ti/pdk_k2g_1_0_10/packages$ ./pdkProjectCreate.sh K2G all little mcasp all dsp

    This will create all audio examples available. There is a loopback example.

    Best Regards,
    Yordan
  • Hi Yordan,

    thanks for the answer. One correction - the arguments should be: K2G all little mcasp all dsp. However, this creates MCASP_DeviceLoopback_evmK2G_c66ExampleProject and not the audioAnalogLoopbackTest project.

    Best regards,

    Adam
  • Adam,

    Currently, we are not providing CCS project for the audioAnalogLoopback example that is part of audK2G. The steps to build and run the example are provided here :
    processors.wiki.ti.com/.../Processor_SDK_RTOS_AUDK2G_AddOn

    If you are having any issues please let us know. If you still need a CCS project, you will need to read the makefile and create a CCS project by including the required source files, setting up the compiler and linker settings and using the appropriate libraries for the example to build.

    Regards,
    Rahul
  • Rahul,

    I think you might have a different project in mind. The 2.2.4.2 section named audioAnalogLoopbackTest in the tiducr7a.pdf, which is the main documento for TIDEP-0088 reference design specifically states that "The cmb project is part of the Processor SDK RTOS package and may be used to debug the CMB board". The source code directly names this project a "unit test" for CMB HW and drivers. It has no relation to the AUDK2G daugher board that you mention.

    Best regards,

    Adam

  • Adam,

    Both the multichannel audio loopack examples based on CMB and the aud2K2g boards, have the same name "audioAnalogLoopbackTest"and both of them are provided in the PDK package under the path pdk_k2g_1_0_10\packages\ti\addon

    As indicated in the Processor SDK RTOS Examples documentation the base unit test for this is built using makefile and not CCS project in the latest baseline:
    software-dl.ti.com/.../index_examples_demos.html

    If you see the TI Design was originally created using pdk_k2g_1_0_4 and the instructions may have been generated based on the software available at that time. I have checked with the developer and can confirm that the CCS projects for these examples are not in the SDK package as they are meant to be built using makefiles. Users can convert them into CCS projects if required by looking at the build log but this is not the default build environment.

    Regards,
    Rahul
  • Rahul,

    thank you very much. For the past 15+ years I have done all my development for TI DSPs in CCS under Windows and it is there where I feel comfortable (editing, building and debug over JTAG). Using makefiles is new to me and makes me feel that it will be all very manual process command-line based. Please correct me if I am wrong and there is an easy way to do it too. I have one more question: what is your motivation when you decide which way you will develop your example projects: makefile-based or CCS-based.

    Thanks and regards,

    Adam
  • Adam,

    I understand where you are coming from as I started as a developer with DSP and MCU where the primary build environment is CCS and can vouch for the ease of use and intuitive nature of the build process when using the IDE environment.

    Having said that let me try and provide the motivation for generating examples and drivers using makefiles is multifold from a Processor SDK RTOS point of view. The SDK supports multiple SOC architectures like ARM cores (Cortex A/R/M) , C66x architectures, PRU and EVE with a wide range of compilers associated with these cores. While CCS support for these cores is available, maintaining eclipse based CCS projects for all examples that ports across different user environments and Host setup has been a challenge. Also, the development teams use Yocto/bitbake OpenEmbedded environment for doing nightly test/regression builds which don`t provide an path to build and test every CCS project based builds. The makefile approach solves both these problems effectively as makefile based builds can be build in both Windows and Linux and supports building using all different compilers based on user defined build environment and allows for automation of build and test environment which is critical for maintenance of this software. In addition, folks migrating from other non-TI architecture to TI don`t need to get familiar with TI specific IDE and can just rely on command line make approach which is widely used in the development community.

    If you are still interested in knowing how to generate a CCS Project for a unit test that builds using makefile, we can support this effort in E2E. For example, we have generated instructions to create SBL(bootloader) using CCS project as you can check from link below:

    processors.wiki.ti.com/.../Creating_a_CCS_Project_for_SBL_on_AM572x_GP_EVM


    Regards,
    Rahul
  • Dear Raul,

    thank you very much for your extensive answer. I am not very much afraid of command-line builds, after all, you always look at the console output to see what happened. And the opportunity of automating processes is very appealing to me, especially for testing. What I am afraid most of is having to sacrifice the comfort and productivity of using the IDE. In the first place for editing (syntax code highlighting, finding the corresponding header files, functions definitions, quickly see what files are in the project and what is the current project configuration. Second: integration of IDE with code generation tools, using the proper compilers, having error or warning reports point back directly to my code, what RTOS components are in use, what memory segments are cached, etc. and for project debugging, the possibility of placing breakpoints, watching variables, even plotting them, etc. Could you please explain me your workflow and set of tools you use for the makefile based projects? I have chosen the audioAnalogLoopbackTest as my starting point for the implementation of my algorithm, if this might serve you as an an example, but just about any project will be fine. I would be very much helpful for giving me a direct list of tools that you use and some practical advice on how you use them.Thank you very much for your help,

    Best regards,

    Adam