CCS/TMS320C6654: Basic and functional project example

Hi,

I found some UPP example codes: 

• https://e2e.ti.com/support/processors/f/791/t/797546
• https://e2e.ti.com/support/processors/f/791/t/202118

UPP interface is not widely used and support is very limited, and if you can consider interfaces like PCIE or EMIF instead of uPP.

Regards, Eric

Hi Eric,

Thank you for the uPP code examples.  The board is already designed so we are locked into the uPP design for now.

Could you please point me to a working example project for the 6654 processor?

E.g., the C2000 examples load very nicely:

But there are no projects to import in the C6000 folder:

I would not even know where to start with the C6000-series processor.

Thanks,

Tomas

Tomas,

The C665x PDK doesn't contain any CCS project. The CCS projects have to be created by a batch script for each driver, but there is no UPP driver. So the script will not create a UPP example for you.

The CSL has the UPP register definition under packages\ti\csl\src\ip\upp\V0, no any API functions or test code. 

Please refer to the previous 2 E2E threads I mentioned, there are some UPP test code attached.

Regards, Eric

Eric,

I see.  I will study the files you mentioned.

But for now, is there a basic working example project, such as "blink LED" for the selected processor? Just something to get calibrated on when coming from the well supported C2000 series.

Also, could you please expand on CCS projects being generated by a batch script for each driver?  This is very different from the C2000 series where there are existing project files.

Thank you,

Tomas

Dear Eric,

I tried using that command for my processor and it failed.  Please see below.  In your script above, you use C6657, which is supported by the bat file.

The bat file supports these SOCs - does any correspond to C6654?

@REM * Description: (first option is default)

@REM * soc - AM335x / AM437x / AM571x / AM572x / AM574x / K2E / K2G / K2K / K2H / K2L /
@REM * C6678 / C6657 / DRA72x / DRA75x / DRA78x / OMAPL137 / OMAPL138 / C6748 / am65xx

C6654 and C6657 are very different devices - with regards to speed and memory.  Also, C6654 is single-core while C6657 is dual-core.

Thank you,

Tomas

Hi,

Please use C6657 for C6654. The difference is 2 vs 1 C66x core. All the driver examples can be created with C6657, there is no C6654.

Regards, Eric  

Dear Eric,

I have tried running the command in my command shell and it fails without giving any details about the failure.  I have tried both administrator and normal mode to run "cmd".  

Also, I did check the target folder.  No files or folders were created by the script.

Thank you, Tomas

Hi,

Please read through the user guide, especially section 1.1.8: 

• Where you installed CCS?
• Did CCS discovered all the package installed?
• In the pdkprojectcreate, is "CCS_INSTALL_PATH" correct?

Regards, Eric

Dear Eric,

Great, thanks.

The issue was the CCS folder location.  I had to change the bat file as follows:

if not defined CCS_INSTALL_PATH (
REM set CCS_INSTALL_PATH=C:/ti/ccs930/ccs
set CCS_INSTALL_PATH=C:/ti/ccs900/ccs
)

Then I built a GPIO toggle project using the "pdkProjectCreate.bat C6657 all big gpio all dsp" command.  The project was created.  We use big endian in our project - processor pin T25 is tied low.

I am able to load the project in CCS.  However, the project does not compile.  Please see the error below.

Just to verify, I also used the little endian setting, even though that one is not supported by the board.  It compiles just fine, which suggests that all software packages are installed correctly.  The project created with "big" endian flag seems to call a non-existing library.

I checked the website you pointed me to (http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_overview.html#download-and-install-software) but there is notion of anything relevant to this issue. 

Thank you, Tomas

Hi,

All the C665X drivers and applications are built and tested with little endian, then packaged and released. In theory, big endian should be possible, but we never try that.

Regards, Eric