CCS/TMS320F28069M: F28069 Launchpad RTSC Setup on CCSv10

Hi Andrew,

Can you get one of the out-of-box SYS/BIOS examples to build properly?

You probably need the ":TMS320F28069" added onto the platform name:

I don't have the sys/bios options. How do I get those choices?

I installed the SYS/BIOS and when I went to open the cfg file but I get the following error.

After installing the new SYS/BIOS and ensuring the CCS has 'discovered' it, then restarted CCS, I think you'll need to delete the old example project and re-import it.

Alan

I tried what u listed above and it didn't work. I also created multiple new projects scratch and it still didn't work. So I tried messing with the memory allocation as shown below. I navigated to the RTSC Tools window and tried changing the settings shown below. I tried changing the stack memory location but it caused more errors. Is there any thing else I can try?

Can you share the .cfg file here?

I notice you have 12110 set as the Clock Speed (MHz) in the 'Device Details'  view. I don't think this is the source of your main problem, but is 12,110 MHz correct (ie 12.11 GHz)?

Alan

7444.app.cfg

I don't see anything wrong there.

Can you confirm that if you import a c28x example from the SYS/BIOS product (in C:/ti/bios_6_83_00_18/packages/ti/sysbios/examples/c28), you are not able to build it?

If importing and building an example doesn't work, I am thinking something is messed up with the CCS or BIOS installation and I would recommend re-booting your PC and re-installing CCS and BIOS. Make sure you enable support for C28 devices when you install CCS.

Alan

I imported an example from that folder but its just a c file and not an entire project file so I don't have the option to build it.

I'll have to ask a local expert who will return on Monday.

From the symptoms, it does appear to me that something is wrong with the CCS installation though.

Alan

I reinstalled CCS and built the typical SYSBIOS v6 RTCS example. I get the following error messages.

I've asked a colleague of mine to assist on this.

Alan

Hi Andrew,
can you clean and rebuild and post the console output? The errors you are seeing indicate a two different linker command files specifying the memory layout. 

The platform tms320x28 was not supposed to be edited with the Platform Wizard. It assumes there is a linker command file in the project that will do that. But if you made the changes in the platform with the Platform Wizard you may still be able to build if you disable the linker command file in the project. But let's see what the console output contains and then we will figure out how to proceed.

**** Build of configuration Debug for project typical ****

"C:\\ti\\ccs1010\\ccs\\utils\\bin\\gmake" -k -j 8 all -O

Building file: "../app.cfg"
Invoking: XDCtools
"C:/ti/ccs1010/xdctools_3_61_02_27_core/xs" --xdcpath="C:/ti/bios_6_83_00_18/packages;" xdc.tools.configuro -o configPkg -t ti.targets.C28_float -p ti.platforms.tms320x28:TMS320F28069 -r release -c "C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS" --compileOptions "-g" "../app.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring app.x28FP from package/cfg/app_p28FP.cfg ...
generating custom ti.sysbios library makefile ...
Starting build of library sources ...
making C:/Users/butlea4/workspace_v10/typical/src/sysbios/sysbios.a28FP ...
cl28FP C:/ti/bios_6_83_00_18/packages/ti/sysbios/BIOS.c ...
asm28FP C:/ti/bios_6_83_00_18/packages/ti/sysbios/family/c28/Hwi_asm.s28 ...
asm28FP C:/ti/bios_6_83_00_18/packages/ti/sysbios/family/c28/Hwi_disp_asm.s28 ...
asm28FP C:/ti/bios_6_83_00_18/packages/ti/sysbios/family/c28/IntrinsicsSupport_asm.s28 ...
asm28FP C:/ti/bios_6_83_00_18/packages/ti/sysbios/family/c28/TaskSupport_asm.s28 ...
ar28FP BIOS.obj c28_Hwi_asm.obj c28_Hwi_disp_asm.obj c28_IntrinsicsSupport_asm.obj c28_TaskSupport_asm.obj ...
Build of libraries done.
cl28FP package/cfg/app_p28FP.c ...
Finished building: "../app.cfg"

1 file(s) copied.
making ../src/sysbios/sysbios.a28FP ...
gmake[1]: Nothing to be done for 'all'.
Building file: "../main.c"
Invoking: C2000 Compiler
"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 --include_path="C:/Users/butlea4/workspace_v10/typical" --include_path="C:/ti/bios_6_83_00_18/packages/ti/posix/ccs" --include_path="C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS/include" -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=coffabi --preproc_with_compile --preproc_dependency="main.d_raw" --cmd_file="configPkg/compiler.opt" "../main.c"
Finished building: "../main.c"

making ../src/sysbios/sysbios.a28FP ...
gmake[2]: Nothing to be done for 'all'.
Building target: "typical.out"
Invoking: C2000 Linker
"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=coffabi -z -m"typical.map" --stack_size=0x300 --warn_sections -i"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS/lib" -i"C:/ti/ccs1010/ccs/tools/compiler/ti-cgt-c2000_20.2.2.LTS/include" --reread_libs --diag_wrap=off --display_error_number --xml_link_info="typical_linkInfo.xml" --rom_model -o "typical.out" "./main.obj" "../TMS320F28069.cmd" -l"configPkg/linker.cmd" -llibc.a
<Linking>
"configPkg/linker.cmd", line 41: error #10263: PIEVECT memory range has already been specified
"configPkg/linker.cmd", line 41: error #10264: PIEVECT memory range overlaps existing memory range PIEVECT
"configPkg/linker.cmd", line 43: error #10264: BOOTROM memory range overlaps existing memory range FPUTABLES
"configPkg/linker.cmd", line 43: error #10264: BOOTROM memory range overlaps existing memory range IQTABLES
"configPkg/linker.cmd", line 43: error #10264: BOOTROM memory range overlaps existing memory range IQTABLES2
"configPkg/linker.cmd", line 43: error #10264: BOOTROM memory range overlaps existing memory range IQTABLES3
"configPkg/linker.cmd", line 43: error #10264: BOOTROM memory range overlaps existing memory range ROM
"configPkg/linker.cmd", line 46: error #10263: OTP memory range has already been specified
"configPkg/linker.cmd", line 46: error #10264: OTP memory range overlaps existing memory range OTP
"configPkg/linker.cmd", line 47: error #10263: BEGIN memory range has already been specified
"configPkg/linker.cmd", line 47: error #10264: BEGIN memory range overlaps existing memory range BEGIN
"configPkg/linker.cmd", line 49: error #10263: FLASH memory range has already been specified
"configPkg/linker.cmd", line 49: error #10264: FLASH memory range overlaps existing memory range FLASH
"configPkg/linker.cmd", line 50: error #10264: L03DPSARAM memory range overlaps existing memory range L03SARAM
error #10010: errors encountered during linking; "typical.out" not built

>> Compilation failure
makefile:141: recipe for target 'typical.out' failed
gmake[1]: *** [typical.out] Error 1
makefile:137: recipe for target 'all' failed
gmake: *** [all] Error 2

**** Build Finished ****

The linker command file TMS320F28069.cmd is defining a memory map, but configPkg/linker.cmd is defining another one based on the map you defined using the Platform Wizard, and these two memory maps are overlapping. I am assuming that the map in configPkg/linker.cmd is the one you want to have.

There are two ways to get there. A quick fix would be to delete the memory map from TMS320F28069.cmd, and rebuild. However, if you do that, the memory map that you created with the Platform Wizard will be used for all projects that use ti.platforms.tms320x28 and your current version of SYS/BIOS. Also, when you update SYS/BIOS, you will lose that version of ti.platforms.tms320x28. So, that quick fix may end up with a lot of work and issues later.

The second solution requires that you reinstall SYS/BIOS, but before you do that, edit TMS320F28069.cmd so that it contains the memory map that you want. Then, when you reinstall SYS/BIOS, you will go back to the initial version of ti.platforms.tms320x28 that doesn't define a memory map. But now, you have TMS320F28069.cmd that you can copy to other project, change it in an editor if needed and so on.

Which one is better depends on how many different projects you deal with, and how often you update SYS/BIOS.

I accidently changed configPkg/linker.cmd and I don't need to keep that file. So how do I delete configPkg/linker.cmd and use TMS320F28069.cmd?