NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
TMS320C6678L Build Configuration
Configuring the Stairstep Example Project to use Ethernet Transport on the TMS320C6678L[edit]
There are a number of additional steps and files that are required in order to use the Ethernet Transport on the C66X EVMs. The attached zip file contains the Stairstep example project ported to run on the EVM6678L: media:StairstepEthernet_6678.zip.
Note that this project is only intended to run on a single CPU of the 6678L. For a multicore example project that supports UIA and System Analyzer, please see Tutorial 4C
The attached zip file contains the following files:
- evmInit.c : provides initialization code for the evm
- netCtrlCallbackFns.c : provides callback functions required by the NDK
- platform_osal.c : implements O/S abstraction APIs required by the various Low Level Drivers (LLDs)
- resourcemgr.c : implements the common configuration of the resource manager for the application to use
- stairstep.c : the 'application code', including the main() function.
- stairstep_Ethernet.cfg : provides the configuration script that is needed to initialize the various low level drivers and configure BIOS and the NDK.
The following steps show how to configure a project's build options to use the LLDs and the various packages associated with the 6678L:
1. Install MCSDK 2.X. Be careful to read the MCSDK readme instructions before installing, especially if you are already using CCSv5.1 as there are some special steps required in order to avoid overwriting the version of System Analyzer that is installed with CCS.
NOTE: For MCSDK releases later than MCSDK 2.1.1.4, please use the platform_osal.c and resourcemgr.c files located in <MCSDK INSTALL DIR>\examples\ndk\helloWorld in your project instead of the ones that are in the StairstepEthernet_6678.zip file. (Special thanks to Fabian for his help).
2. Add any required build variables
- right click on the project in the CCS Project view, select Properties / Build / Build Variables
- check the "Show System Variables" checkbox
- If required, edit any incorrect paths or add any missing variables.
- verify that the following variables are defined and contain valid paths to the install folders for the various products
- TI_PDK_INSTALL_DIR
- NDK_INSTALL_DIR
- BIOS_CG_ROOT
- IPC_CG_ROOT
- COM_TI_UIA_INSTALL_DIR
- TI_MCSDK_INSTALL_DIR
3. Add the various packages to the project
- Right click on the project in the CCS Project view, select Properties / General / RTSC
- 3a) Add the MCSDK to the package path
- 3b) Add MCSDK/demos/hua to the package path
- 3c) In the "Platform:" field, select a platform file for your target device (custom.hpdspua.evmc6678l if you are using a 6678L evm)
- 3d) Add the UIA, NDK, Sys/BIOS and PDK packages you wish to use by setting the appropriate checkboxes in the list of RTSC packages
4. Modify the project include options:
- TIP: did you know that you can enter filter text in the Build Settings box to make it easier to locate a particular group of setting options?
5. Predefine the following symbols:
Note: If you later wish to switch to using JTAG to upload events from the target, you will need to set LoggingSetup.eventUploadMode = LoggingSetup.UploadMode_JTAGRUNMODE AND remove all lines associated with the ServiceMgr module from your .cfg file.
Links[edit]