Error building STK-MED for 6678

Richard Sampson

Other Parts Discussed in Thread: MIDAS

I have installed STK-MED 3.0, and I have installed all the needed components (with versions specified in the README). I have started to build the modules, and I am able to build all but the testscu and testdpu modules, both giving me the following errors:

Inside EDMA3 RM getLibs
    will link with ti.sdo.edma3.rm:lib/c6678-evm/66/debug/edma3_lld_rm.ae66
js: "C:\ti\xdctools_3_22_00_09\packages\ti\targets\elf\linkcmd.xdt#108(eval)", line 1: Error: Allocations for sections '.bss', '.rodata' and '.neardata' must be same.
gmake.exe: *** [package/cfg/bios6_pe66.xdl] Error 1
gmake.exe: *** Deleting file `package/cfg/bios6_pe66.xdl'
gmake.exe: *** [package/cfg/bios6_pe66.xdl] Deleting file `package/cfg/bios6_pe66.h'
gmake.exe: *** [package/cfg/bios6_pe66.xdl] Deleting file `package/cfg/bios6_pe66.c'
Warning: directory "C:/packages" on package path does not exist
Warning: directory "C:/ti/xdctools_3_22_00_09" on package path has a "packages" subdirectory - did you mean this instead?
js: "C:/ti/xdctools_3_22_00_09/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: *** [configPkg/compiler.opt] Error 1
gmake: Target `all' not remade because of errors.

I am compiling for EVM6678.

over 13 years ago

0 Uday over 13 years ago

TI__Expert 4920 points

Hi Richard,

Could you please verify the following: Go to Window->Preferences->CCS->RTSC->Products. Check if C:/ti (or equivalent TI_INSTALL_DIR, i.e. path to directory where you have installed all the software components) is listed under "Tool Discovery Path." If not, add it to your tool discovery path. This should populate "Discovered Tools." with the installed components. Now try doing a clean and then a build. If this doesn't resolve the issue, we'll need the following information to help debug:

1. Please take a screenshot of Window->Preferences->CCS->RTSC->Products

2. Please take a screenshot of Window -> Preferences -> CCS -> Code Generation Tools.

3. Go back to your workspace. Under the 'C/C++ Projects' subwindow, right click on 'sculib_c66,' "Build Configurations --> Clean All" and then "Build Configurations --> Build All." Copy-paste all text from the Console into a file and attach it to your post.

4. Now do the same for 'testscu_C6678,' i.e. under the 'C/C++ Projects' subwindow, right click on 'testscu_C6678,' "Build Configurations --> Clean All" and then "Build Configurations --> Build All." Copy-paste all text from the Console into a file and attach it to your post.

0 Richard Sampson over 13 years ago in reply to Uday

Prodigy 60 points

I had already added C:\ to my path as you can see. I also tried a clean build and it did not work for scutest.

Here are the builds for the sculib and for scutest. I have also added the builds for bpulib and bputest which works and I have successfully run the binaries for.

8535.sculib_build.txt

8446.scutest_build.txt

4718.bpulib_build.txt

2072.scutest_build.txt

0 Richard Sampson over 13 years ago in reply to Richard Sampson

Prodigy 60 points

Sorry I posted the wrong file for bputest last time and the image for the RTSC products didn't post , here is the correct build and the image:

5810.bputest_build.txt

0 Uday over 13 years ago in reply to Richard Sampson

TI__Expert 4920 points

Hi Richard,

I looked at your testscu build log. Looks like it's not picking up the right set of software components (including EDMA) in your build environment. Below is a comparison of the initial lines for our build console (outputs highlighted in yellow). You'll observe that in your case the second path for 'xdcpath' is just '/packages' whereas in the successful build log below it is 'C:/development/ti/edma3_lld_02_11_02_04/packages.' It cannot locate the EDMA install directory in your environment. Also looking at your screenshot, I don't see MCSDK. Is MCSDK installed? Is it installed in another location that's not included in the tool discovery path? The EDMA package that we need is part of this MCSDK package.

Another difference is that in your environment it is also picking up some additional software components which shouldn't be part of the build. Not sure why it's doing that; were any changes made to the default properties provided in STK-MED for the project? Please right click on testscu_C6678, and then select "Properties -> CCS Build -> RTSC (tab)." For both "Debug" and "Release" Configurations (drop-down menu at the top), verify that the only 4 components checked are "EDMA3 Low Level Driver 02.11.02" , "Framework Components 3.21.01.26", "SYS/BIOS 6.31.05.31" and "Other Repositories: ${PROJECT_ROOT}/../platformRepo." All other components should not be checked.

Another difference (highlighted in blue) is that it is picking up the wrong RTSC platform. As wiki readme points out, did you unzip 'plat6678.zip' at "scu_ires\test\ccsProj_C6678\platformRepo"? If so (or once that's done), please make sure that the "RTSC Platform" selected in "Properties -> CCS Build -> RTSC (tab)" for the project, for both Debug and Release configurations is selected to be 'plat6678.'

Ensure that once you have made the above changes you do a 'clean all' and then a 'build all'. Let me know how it goes.

Successful build:

**** Build of configuration Release for project testscu_C6678 ****
C:\ti\ccsv5\ccsv5\utils\gmake\gmake -k all 
'Building file: C:/development/tests/customerissues/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/bios6.cfg'
'Invoking: XDCtools'
"C:/development/ti/xdctools_3_22_00_09/xs" --xdcpath="C:/development/ti/bios_6_31_05_31/packages;
C:/development/ti/edma3_lld_02_11_02_04/packages;
C:/development/tests/customerissues/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/testscu/../platformRepo;
C:/development/ti/framework_components_3_21_01_26/fctools/packages;
C:/development/ti/framework_components_3_21_01_26/packages;" xdc.tools.configuro -o configPkg 
-t ti.targets.elf.C66 -p plat6678 -r release -c 
"C:/ti/ccsv5/ccsv5/tools/compiler/c6000" "C:/development/tests/customerissues/stk-med-03.00.00/miAlgos/scu_ires/test/
ccsProj_C6678/bios6.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring bios6.pe66 from package/cfg/bios6_pe66.cfg ...
useModule Settings: 6600
Setting to dskt2's functions 
Auto-registering resource manager for EDMA3CHAN
remark: the selected profile (release) does not generate optimized code.  'debug' and 'release' profiles should only 
be used for source-level debugging of BIOS code.  
While these profiles build faster, the code runs slower and requires extra stack space.  'whole_program' profile 
is recommended for optimized code.
Inside EDMA3 RM getLibs
    will link with ti.sdo.edma3.rm:lib/generic/66/release/edma3_lld_rm.ae66
cle66 package/cfg/bios6_pe66.c ...
'Finished building: C:/development/tests/customerissues/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/bios6.cfg'
......

......

Failed Build (your environment):

C:\ti\ccsv5\ccsv5\utils\gmake\gmake -k all 
'Building file: C:/ti/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/bios6.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_22_00_09/xs" --xdcpath="C:/ti/bios_6_31_05_31/packages;/packages;
C:/ti/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/testscu/../platformRepo;
C:/ti/framework_components_3_21_01_26/fctools/packages;C:/ti/framework_components_3_21_01_26/packages;
C:/ti/codec_engine_3_21_00_19/packages;
C:/ti/codec_engine_3_21_00_19/examples;C:/ti/codec_engine_3_21_00_19/cetools/packages;
C:/ti/ipc_1_22_05_27/packages;C:/ti/ccsv5/xdais_7_20_00_07/packages;
C:/ti/ccsv5/xdais_7_20_00_07/examples;C:/ti/dsplib_c66x_3_0_0_8/packages;" 
xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r 
release -c "C:/ti/ccsv5/ccsv5/tools/compiler/c6000" "C:/ti/stk-med-03.00.00/miAlgos/scu_ires/test/ccsProj_C6678/bios6.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring bios6.pe66 from package/cfg/bios6_pe66.cfg ...
useModule Settings: 6600
Setting to dskt2's functions 
Auto-registering resource manager for EDMA3CHAN
remark: the selected profile (release) does not generate optimized code.  'debug' and 'release' profiles 
should only be used for source-level debugging of BIOS code.  
While these profiles build faster, the code runs slower and requires extra stack space.  
'whole_program' profile is recommended for optimized code.
Inside EDMA3 RM getLibs
    will link with ti.sdo.edma3.rm:lib/c6678-evm/66/release/edma3_lld_rm.ae66
js: "C:\ti\xdctools_3_22_00_09\packages\ti\targets\elf\linkcmd.xdt#108(eval)", 
line 1: Error: Allocations for sections '.bss', '.rodata' and '.neardata' must be same.

gmake.exe: *** [package/cfg/bios6_pe66.xdl] Error 1
gmake.exe: *** Deleting file `package/cfg/bios6_pe66.xdl'
gmake.exe: *** [package/cfg/bios6_pe66.xdl] Deleting file `package/cfg/bios6_pe66.h'
gmake.exe: *** [package/cfg/bios6_pe66.xdl] Deleting file `package/cfg/bios6_pe66.c'
Warning: directory "C:/packages" on package path does not exist
js: "C:/ti/xdctools_3_22_00_09/packages/xdc/tools/Cmdr.xs", line 51: 
Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: *** [configPkg/compiler.opt] Error 1
gmake: Target `all' not remade because of errors.

0 Richard Sampson over 13 years ago in reply to Uday

Prodigy 60 points

EDMA and MCSDK were installed, but unchecking the stuff not needed and unpacking plat6678 worked. Also you referred to a wiki, but I am unaware of and have not found a wiki for the SDK so if you have a link, I would greatly appreciate it.

0 Uday over 13 years ago in reply to Richard Sampson

TI__Expert 4920 points

Great, glad it works.

Sorry, I meant the readme.txt, not wiki.

Btw, there are also medical imaging demos (ultrasound and OCT), system-level implementation examples that leverage the algorithms from this software toolkit. For 6678, you'll want to look at MIDAS Ultrasound v4.0 and for OCT, MIDAS OCT v1.0. The main landing page for MIDAS is here.

Good luck with your project.

Processors

Processors forum

Error building STK-MED for 6678