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.
Tool/software: Code Composer Studio
.cfg添加var MultiProc = xdc.useModule('ti.sdo.utils.MultiProc');报错
Description Resource Path Location Type
can't locate the package 'ti.sdo.utils' along the path: 'C:/ti/bios_6_33_04_39/packages;C:/ti/mcsdk_2_00_09_21/demos;C:/ti/pdk_C6678_1_0_0_21/packages;C:/ti/ndk_2_21_02_43/packages;C:/Users/zjm/workspace_v5_5/C6678_Test_DSP_Net_v20190320/platform;C:/ti/ccsv5/ccs_base;C:/ti/dsplib_c66x_3_1_0_0/packages;C:/ti/xdctools_3_23_02_47/packages;..;'. Ensure that the package path is set correctly. .xdchelp /C6678_Test_DSP_Net_v20190320 line 266 C/C++ Problem
Description Resource Path Location Type
unresolved symbol MultiProc_self, first referenced in ./main.obj C6678_Test_DSP_Net_v20190320 C/C++ Problem
Hi,
Looks you are using MCSDK package, which is already obsolete. You may consider migrating to Processor SDK RTOS for C6678. Please see https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/t/353777 if it helps, maybe IPC package is missing.
Regards, Eric
你好:
我设置了这个之后错误变成一个:
说明资源路径位置类型
不能沿着以下路径找到包“ ti.sdo.utils”:'C:/ ti / bios_6_33_04_39 / packages; C:/ ti / mcsdk_2_00_09_21 / demos; C:/ ti / pdk_C6678_1_0_0_21 / packages; C:/ ti / ndk_2_21_02_43 / packages; C:/ Users / zjm / workspace_v5_5 / C6678_Test_DSP_Net_v20190320 / platform; C:/ ti / ccsv5 / ccs_base; C:/ ti / dsplib_c66x_3_1_0_0 / packages; C:/ ti / xdctools_3。确保包路径设置正确。.xdchelp / C6678_Test_DSP_Net_v20190320行266 C / C ++问题
Hi,
As you registered IPC 1.24 and 3.23 under CCS, I thought you should have a way to select one of them to use. Then they should appear in the search path when you compile the code. Below is screenshot a typical SYSBIOS project, not the same as yours, but you can see the RTSC package needs to be selected.
When I built it, I have them in the search path:
"C:\\ti\\ccs930\\ccs\\utils\\bin\\gmake" -k -j 8 all -O
Building file: "C:/ti/pdk_k2hk_4_0_13/packages/ti/diag/serdes_diag/test/k2h/c66/bios/serdes_diag_example.cfg"
Invoking: XDCtools
"C:/ti/ccs_8_3_0/xdctools_3_51_01_18_core/xs" --xdcpath="C:/ti/bios_6_76_03_01/packages;C:/ti/pdk_k2hk_4_0_13/packages;C:/ti/edma3_lld_2_12_05_30E/packages;C:/ti/ipc_3_50_04_07/packages;C:/ti/ndk_3_61_01_01/packages;C:/ti/uia_2_30_01_02/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evmTCI6636K2H -r debug -c "C:/ti/ti-cgt-c6000_8.3.2" "C:/ti/pdk_k2hk_4_0_13/packages/ti/diag/serdes_diag/test/k2h/c66/bios/serdes_diag_example.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring serdes_diag_example.xe66 from package/cfg/serdes_diag_example_pe66.cfg ...
Linking with library ti.csl:./lib/k2h/c66/release/ti.csl.ae66;./lib/k2h/c66/release/ti.csl.intc.ae66
cle66 package/cfg/serdes_diag_example_pe66.c ...
Regards, Eric
Hi,
In your .cfg file, you have some IPC setting like this:
/****** IPC - Shared Memory Settings ********/
/* IPC packages */
var Ipc = xdc.useModule('ti.sdo.ipc.Ipc');
var Settings = xdc.module('ti.sdo.ipc.family.Settings');
var ListMP = xdc.useModule('ti.sdo.ipc.ListMP');
var GateMP = xdc.useModule('ti.sdo.ipc.GateMP');
var SharedRegion = xdc.useModule('ti.sdo.ipc.SharedRegion');
var HeapMemMP = xdc.useModule('ti.sdo.ipc.heaps.HeapMemMP');
var MultiProc = xdc.useModule('ti.sdo.utils.MultiProc');
I am not sure why the CCS project didn't search the registered IPC package. Maybe something messed up? Do you have a clean IPC example project proven working as a starting point?
Regards, Eric