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.

MCSHM & OMAPL138 SW development

Other Parts Discussed in Thread: OMAPL138, AM3517, TI-CGT, SYSBIOS

Hello,

I asked some time in this forum about "Migration from c6745 to c6748/omapl138" got good answer(s) and have followed that guided path.

We're putting together out RT- code from c6745 and our Linux- code from am3517 into a OMAPL138. 

We've started with MCSDK as advised in this forum and successfully installed and used tools listed below (from syslink products.mak)  and also run example codes with LodicPD eXperimenter kit. The time we tested syslink and examples we did not have CCS in linux but ti-cgt....

I  installed CCS to linux too but found it too complicated to me to import any syslink examples to CCS in and while trying that it became to my mind that what is the value added using CCS. 

So I would appreciate if some expert could recommend me "best practice" to develop sysbios & Linux code in a Linux host. 

Best Regards,

Risto

######## For OMAPL1XX device ########
LINUXKERNEL = $(DEPOT)/ti/mcsdk_1_01_00_02/board-support/linux-3.3-psp03.22.00.06.sdk
CGT_ARM_INSTALL_DIR = $(DEPOT)/arago-2011.09/armv5te
CGT_ARM_PREFIX = $(CGT_ARM_INSTALL_DIR)/bin/arm-arago-linux-gnueabi-
IPC_INSTALL_DIR = $(DEPOT)/ti/ipc_1_25_03_15
BIOS_INSTALL_DIR = $(DEPOT)/ti/bios_6_34_03_19
XDC_INSTALL_DIR = $(DEPOT)/ti/xdctools_3_24_05_48

# If LOADER=ELF then below elf tools path is required else set C64P path
ifeq ("$(LOADER)","ELF")
CGT_C674_ELF_INSTALL_DIR= $(DEPOT)/ti/ti-cgt-c6000_8.0.2
else
CGT_C674_INSTALL_DIR = $(DEPOT)/ti/ti-cgt-c6000_8.0.2
endif