• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 82 subscribers
  • Views 2333 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/TMS320F28379D: New Project Basic example does not compile

Lenio Cacula
Genius 16820 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: SYSBIOS,

Tool/software: TI-RTOS

Issue:

When creating a new RTOS project in CCS for F28379D, the code does not compile and generates the following errors: (Project/New CCS Project/SYS/BIOS/TI Target Examples/ Typical):

Description Resource Path Location Type
declaration is incompatible with "xdc_Ptr ti_sysbios_BIOS_RtsGateProxy_Proxy__delegate__S(void)" (declared at line 244 of "C:/TI/bios_6_46_01_38/packages/ti/sysbios/package/BIOS_RtsGateProxy.h") .xdchelp /RTOS_blinky_CPU1 line 19906 C/C++ Problem
gmake: *** No rule to make target 'build-1317351329', needed by 'configPkg/compiler.opt'. RTOS_blinky_CPU1     C/C++ Problem
gmake: Target 'all' not remade because of errors. RTOS_blinky_CPU1     C/C++ Problem
gmake[1]: *** [build-1317351329-inproc] Error 1 RTOS_blinky_CPU1     C/C++ Problem
 warning: a value of type "const __T1_ti_sysbios_knl_Idle_coreList *" cannot be used to initialize an entity of type "xdc_UInt *" .xdchelp /RTOS_blinky_CPU1 line 6578 C/C++ Problem
 warning: a value of type "const __T1_ti_sysbios_knl_Idle_funcList *" cannot be used to initialize an entity of type "ti_sysbios_knl_Idle_FuncPtr *" .xdchelp /RTOS_blinky_CPU1 line 6567 C/C++ Problem
 warning: a value of type "xdc_Ptr (*)(xdc_Ptr, xdc_SizeT, xdc_Ptr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" cannot be used to initialize an entity of type "xdc_Ptr (*)(xdc_CPtr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" .xdchelp /RTOS_blinky_CPU1 line 853 C/C++ Problem
 warning: a value of type "xdc_Ptr (*)(xdc_Ptr, xdc_SizeT, xdc_Ptr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" cannot be used to initialize an entity of type "xdc_Ptr (*)(xdc_CPtr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" .xdchelp /RTOS_blinky_CPU1 line 881 C/C++ Problem
 warning: a value of type "xdc_Ptr (*)(xdc_Ptr, xdc_SizeT, xdc_Ptr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" cannot be used to initialize an entity of type "xdc_Ptr (*)(xdc_CPtr, const xdc_UChar *, xdc_SizeT, xdc_runtime_Error_Block *)" .xdchelp /RTOS_blinky_CPU1 line 910 C/C++ Problem
a value of type "const xdc_runtime_Types_Base *" cannot be assigned to an entity of type "xdc_runtime_Types_Base *" .ccsproject /RTOS_blinky_CPU1 line 142, external location: C:\TI\bios_6_46_01_38\packages\ti\sysbios\interfaces\ITimestamp.h C/C++ Problem
a value of type "const xdc_runtime_Types_Base *" cannot be assigned to an entity of type "xdc_runtime_Types_Base *" .ccsproject /RTOS_blinky_CPU1 line 162, external location: C:\TI\bios_6_46_01_38\packages\ti\sysbios\interfaces\ITimestamp.h C/C++ Problem

Versions:

CCS: 7.1.0.00016 

Compiler: TI v16.9.3.LTS

SYS/BIOS: 6.46.1.38

XDC Tool version: 3.50.1.12_core

Hardware: F28379D control card on dock station (XDS100v2)

Platform: ti.platforms.tms320x28:TMS320F28379D

Target: ti.targets.C28_float

Thank you!

  • 0
    TI__Mastermind 37985 points
    Lenio,
    these versions of XDCtools and SYS/BIOS are incompatible. CCS 7.1 also comes with XDCtools 3.32 installed, so please switch to that version for your project.
  • 0 in reply to Sasha Slijepcevic
    TI__Genius 16820 points

    Thanks, Sasha.

    1. The previous errors are gone, but I have new ones as the generated program does not fit in the available memory space. I tried all available linker command files without success.

    2. Is there a way to fix the default version of XDC? The option to create a Typical example should compile out-of-box, without previous knowledge of compatibility issues. By the way, do we have the compatibility information documented anywhere? Can you point me to a link? I am sure I can dig my way out of the errors I am seeing now, but the same idea should apply to the default linker command file with a plug-and-play setup. Is this an issue for the C2000 team?

    Thank you!

  • 0 in reply to Lenio Cacula
    TI__Mastermind 37985 points
    1. I would have to see the linker errors to tell you more. Please post the complete console output.

    2. I think there should be an error talking about incompatibility after these errors that you posted. In the next version of XDCtools, the incompatibility error message is going to show up earlier in the build, and is more informative.
    We also fixed the release notes for 3.50.02 to talk more about the incompatibility. The release notes for 3.50.01 do not have that information.

    As for the default version of XDCtools for examples, I'll have to ask someone else. I know that at the time SYS/BIOS 6.46 was released we didn't have XDCtools 3.50, so the example settings would probably specify "a release newer or equal to 3.32" or "the latest XDCtools available".
  • 0 in reply to Sasha Slijepcevic
    TI__Genius 16820 points

    Hi Sasha,

    here is the console log:

    Fullscreen Console_RTOS_F28379D.txt Download 
    **** Build of configuration Debug for project RTOS_blinky_CPU1 ****

"C:\\TI\\ccsv7\\utils\\bin\\gmake" -k -j 4 all -O 
gmake[1]: Entering directory 'C:/Users/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1/Debug'
'Building file: ../app.cfg'
'Invoking: XDCtools'
"C:/TI/xdctools_3_32_00_06_core/xs" --xdcpath="C:/TI/bios_6_46_01_38/packages;C:/TI/ccsv7/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.C28_float -p ti.platforms.tms320x28:TMS320F28379D -r release -c "C:/TI/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS" --compileOptions "-g --optimize_with_debug" "../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/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1/src/sysbios/sysbios.a28FP ...
gmake[1]: Entering directory `C:/Users/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1/src/sysbios'
cl28FP C:/TI/bios_6_46_01_38/packages/ti/sysbios/BIOS.c ...
asm28FP C:/TI/bios_6_46_01_38/packages/ti/sysbios/family/c28/Hwi_asm.s28 ...
asm28FP C:/TI/bios_6_46_01_38/packages/ti/sysbios/family/c28/Hwi_disp_asm.s28 ...
asm28FP C:/TI/bios_6_46_01_38/packages/ti/sysbios/family/c28/IntrinsicsSupport_asm.s28 ...
asm28FP C:/TI/bios_6_46_01_38/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 ...
gmake[1]: Leaving directory `C:/Users/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1/src/sysbios'
Build of libraries done.
cl28FP package/cfg/app_p28FP.c ...
'Finished building: ../app.cfg'
' '
gmake[1]: Leaving directory 'C:/Users/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1/Debug'
        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/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla1 --float_support=fpu32 --tmu_support=tmu0 --vcu_support=vcu2 --include_path="C:/Users/a0274085/Workspace_root/F28379D_LP_v2/RTOS_blinky_CPU1" --include_path="C:/TI/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS/include" -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="main.d" --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: RTOS_blinky_CPU1.out'
'Invoking: C2000 Linker'
"C:/TI/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla1 --float_support=fpu32 --tmu_support=tmu0 --vcu_support=vcu2 -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"RTOS_blinky_CPU1.map" --stack_size=0x200 --warn_sections -i"C:/TI/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS/lib" -i"C:/TI/ccsv7/tools/compiler/ti-cgt-c2000_16.9.3.LTS/include" --reread_libs --diag_wrap=off --display_error_number --xml_link_info="RTOS_blinky_CPU1_linkInfo.xml" --rom_model -o "RTOS_blinky_CPU1.out" "./main.obj" "../2837x_RAM_lnk_cpu1.cmd" -l"configPkg/linker.cmd" -llibc.a -llibc.a 
<Linking>
warning #10247-D: creating output section ".binit" without a SECTIONS specification
warning #10247-D: creating output section ".cio" without a SECTIONS specification
"../2837x_RAM_lnk_cpu1.cmd", line 68: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".econst" size 0x1d5c page 1.  Available memory ranges:
   RAMLS5       size: 0x800        unused: 0x800        max hole: 0x800     
"../2837x_RAM_lnk_cpu1.cmd", line 67: error #10099-D: program will not fit into available memory.  run placement with alignment/blocking fails for section ".ebss" size 0x10d5 page 1.  Available memory ranges:
   RAMLS5       size: 0x800        unused: 0x800        max hole: 0x800     
"../2837x_RAM_lnk_cpu1.cmd", line 61: error #10099-D: program will not fit into available memory.  placement with alignment/blocking fails for section ".cinit" size 0x42a page 0.  Available memory ranges:
   RAMM0        size: 0x2de        unused: 0x0          max hole: 0x0       
"configPkg/linker.cmd", line 73: warning #10097: memory range not found: D01SARAM on page 0
"configPkg/linker.cmd", line 72: error #10265: no valid memory range(NULL) available for placement of ".text:ti_catalog_c2800_initF2837x_flashfuncs"
"configPkg/linker.cmd", line 72: error #10099-D: program will not fit into available memory.  run placement with alignment/blocking fails for section ".text:ti_catalog_c2800_initF2837x_flashfuncs" size 0x27 page 0
"configPkg/linker.cmd", line 72: warning #10097: memory range not found: FLASHA on page 0
"configPkg/linker.cmd", line 72: error #10265: no valid memory range(NULL) available for placement of ".text:ti_catalog_c2800_initF2837x_flashfuncs"
"configPkg/linker.cmd", line 72: error #10099-D: program will not fit into available memory.  load placement with alignment/blocking fails for section ".text:ti_catalog_c2800_initF2837x_flashfuncs" size 0x27 page 0
error #10010: errors encountered during linking; "RTOS_blinky_CPU1.out" not built

>> Compilation failure
makefile:142: recipe for target 'RTOS_blinky_CPU1.out' failed
gmake[1]: *** [RTOS_blinky_CPU1.out] Error 1
makefile:138: recipe for target 'all' failed
gmake: *** [all] Error 2

**** Build Finished ****

  • 0 in reply to Lenio Cacula
    TI__Mastermind 37985 points
    Lenio,
    it seems that SYS/BIOS expects some FLASH available on the device. I can also see in SYS/BIOS Release Notes under Supported Devices that 28379D is not on the list. I was able to make a typical example work when I added F28377D.cmd from <SYS/BIOS installation>/packages/ti/platforms/tms320x28/include to the project.
    I am not really sure what all this together says about SYS/BIOS support for 28379D. Since it's not on the list of the supported devices I don't think there was any testing done for that device.
  • 0 in reply to Sasha Slijepcevic
    TI__Genius 16820 points
    Thanks, Sasha. That was my intent - just to alert the issue with the New Project option for this device. Thanks for the help!