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/PROCESSOR-SDK-OMAPL138: PROCESSOR-SDK-OMAPL138

Part Number: PROCESSOR-SDK-OMAPL138
Other Parts Discussed in Thread: OMAPL138, OMAP-L138, SYSBIOS, SYSCONFIG

Tool/software: Code Composer Studio

hi,

Using Examples by MyExampleProjectsat pdk_omapl138. Regards Example of MCASP_Audio.. example.

The program is inefficient and difficult to decipher. HWI takes 45% cpu and Task 36%.In superficiality the task is copying input buffer to output buffer without any algorithm which in this case gives less than 20% for signal processing.

Is there another example, a simpler one of audio sampling for the LCDKOMAPL138 that can help me?

Thanks,

Itzhak

  • Hi Itzhak,

    Unfortunately that is the only supported McASP example available for OMAP-L138 in Processor SDK RTOS. 

    Regards,
    Sahin

  • Hi sahin,

    Is there a way to program the devices/peripherals such as EDMA, MCASP, I2C, CODEC etc.. with the help of SYS/BIOS graphic configuration tool as it was with BSL and CSL at CCSv3?

    Thanks,

    Itzhak

  • Itzhak,

    I can describe the available programming options but we may need some more clarification on the programming model that you are describing to be sure that this meets your expectations. OMAPL138/C6748 still provides a register level and functional CSL layer for programming the Chip. The CSL is part of the Platform development kit (PDK) that is part of our Processor SDK RTOS offering for the device. The BSL package that you referred to for the package refer to the Board support library provided by the board manufacturer for functional testing. This package existed for Logic PD EVM but the LCDK platform is functionally tested with out driver examples in the current software package.

    SYSBIOS still provides a Graphical configuration tool that is referred to as XGCONF that is part of our CCS offering but this only allows you to configure the RTOS modules and features not the peripheral drivers. Refer SYSBIOS user guide for details.  If EDMA, MCASP, I2C and CODEC is being used in your usecase, I would recommend that you look at our MCASP LLD example for LCDK platform which has the I2C, CODEC and EDMA functionality integrated to demonstrate stereo audio loopback using the HW platform.  IF you want to look at bare-metal code for McASP for C674x then there is also a multichannel audio example in the board diagnostics for reference.

    If the expectations is to have a GUI based tool that does auto code generation for peripheral configuration using the CSL as in case of SYSconfig that is supported by Simplelink SDK then this functionality does not exist. Hope this helps 

    Regards,

    Rahul

  • hi,

    Where can I find MCASP LLD example for LCDK platform?

    Thanks,

    Itzhak

  • Itzhak,

    All supported McASP LLD examples are documented here:

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_device_drv.html#id192

    to create the examples, you need to setup the Processor SDK RTOS build environment and run the pdkProjectCreate script a described here:

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_overview.html#pdk-example-and-test-project-creation

    The audio example, sets up the AIC3106 audio codec and then loops the Line in input and loops it back through MCASP out to DAC/lineout 

    Hope this helps.

    Regards,

    Rahul 

  • Hi Rahul,

    That's exactly what I did, The DSP example of MCASP_Audio... at pdkpdk_omapl138..\MyExampleProjects is a non-real time implementation as of all HWI threads takes 40% at least of cpu load and the leave only ~20% for signal processing. Thata why asking all this. If there is a good tools to configure peripherals for specific real time implementation like was done at earlier versions (CCS3) or other tools. It seems to me to build every project using peripheral from scratch is not the right policy of TI especially by using XGCONF for static configuration.

    Regards,

    Itzhak

  • The implementation is consistent across all of our processors and is being used in several audio products so I not sure that there is a driver issue with McASP LLD. Can you please provide a little more detail on how you are meauring CPU load for HWI. for most TI RTOS applications we recommend users to leverage the CCS integrated system analyzer tool for checking the application and CPU loading when TI RTOS application is running. You need to add from UIA configuration into SYSBIOS configuration to enable the Task and HWI visualization.

    Please refer to the TI RTOS Tips and Tricks here for enabling the system analyzer visualization.

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_how_to_guides.html#logging-and-trace

    Appreciate the feedback on the GUI based tooling requirement and we are currently evaluting several internal (CCS SYSConfig, GUI composer) and third party configuration tool options to make this easier. Not all customers like the GUI based option as much and prefer to have the API approach as it allows for maximum flexibility and integration into their environment.

    Regards,

    Rahul