Syslink memory problem using DM8168

Hi Stephen,

If you are still having issues, can you provide some more details as to how you have modified your custom platform and added the new memory section names.
Do you have config.bld where you have defined new memory sections/map? Can you attach this and any other .cfg files that may be relevant?

Best,
Murat

I'm still having this problem.  I looked for a config.bld and found one in Debug/configPkg/ -- it looks like there's an error (I'll try to attach the file), but this was not apparent in the build:

**** Build of configuration Debug for project mbdsp ****

/opt/TI/ccsv5/utils/bin/gmake -k all
Building file: ../main.cfg
Invoking: XDCtools
"/opt/TI/xdctools_3_24_05_48/xs" --xdcpath="/opt/TI/bios_6_34_02_18/packages;/opt/TI/syslink_2_21_00_03/packages;/opt/TI/ipc_1_25_00_04/packages;/home/n5ac/microburst/smoothlake/trunk/packages;/opt/TI/ccsv5/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p flexradio.microburst_dsp -r release -c "/opt/TI/ccsv5/tools/compiler/c6000_7.4.1" --compileOptions "-g --optimize_with_debug" "../main.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring main.xe674 from package/cfg/main_pe674.cfg ...
cle674 package/cfg/main_pe674.c ...
Finished building: ../main.cfg
 
Building file: ../main.c
Invoking: C6000 Compiler
"/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6740 --abi=eabi -g --include_path="/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/include" --define=dm8168 --display_error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="main.pp" --cmd_file="./configPkg/compiler.opt"  "../main.c"
Finished building: ../main.c
 
Building file: ../server.c
Invoking: C6000 Compiler
"/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6740 --abi=eabi -g --include_path="/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/include" --define=dm8168 --display_error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="server.pp" --cmd_file="./configPkg/compiler.opt"  "../server.c"
Finished building: ../server.c
 
Building target: mbdsp.xe674
Invoking: C6000 Linker
"/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6740 --abi=eabi -g --define=dm8168 --display_error_number --diag_warning=225 -z --stack_size=0x800 -m"mbdsp.map" --heap_size=0x800 -i"/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/lib" -i"/home/n5ac/microburst/smoothlake/trunk/packages" -i"/opt/TI/c674x-dsplib/lib" -i"/opt/TI/ccsv5/tools/compiler/c6000_7.4.1/include" --reread_libs --define=DSP_CORE=1 --warn_sections --display_error_number --retain=_Ipc_ResetVector --rom_model --dynamic=exe -o "mbdsp.xe674" -l"./configPkg/linker.cmd"  "./server.obj" "./main.obj" -ldsplib674x_elf.lib -l"libc.a"
<Linking>
Finished building target: mbdsp.xe674
 
/opt/TI/ccsv5/utils/bin/gmake --no-print-directory post-build
cp mbdsp.xe674 /nfsroots/microburst/home/root/
 

**** Build Finished ****

Any file I attempt to attach get a "file type not allowed".  I've tried renaming to ._bld, etc. with no luck.

Steve

This file is small enough, I'll just add it here directly (config.bld):

/* THIS IS A GENERATED FILE -- DO NOT EDIT */
/* configuro was passed the target's name explicitly */
try {
    var target = xdc.module('ti.targets.elf.C674');
}
catch (e) {
    throw new Error("Can't find the target named '" + 'ti.targets.elf.C674'
                    + "' along the path '" + environment["xdc.path"]
                    + "': please check the spelling of the target's name and that it exists along this path.");
}
if (!(target instanceof xdc.module("xdc.bld.ITarget").Module)) {
    throw new Error("The module named 'ti.targets.elf.C674' exists but it's not a target: please check the spelling of the target's name");
}
    
target.ccOpts.prefix = "-g --optimize_with_debug " + target.ccOpts.prefix;
Build.targets = [target];
/* configuro was passed the target's rootDir explicitly */
Build.targets[0].rootDir = '/opt/TI/ccsv5/tools/compiler/c6000_7.4.1';

And here's the linker.cmd that shows the memory ("--" substituted for some paths):

/*
 * Do not modify this file; it is automatically generated from the template
 * linkcmd.xdt in the ti.targets.elf package and will be overwritten.
 */

/*
 * put '"'s around paths because, without this, the linker
 * considers '-' as minus operator, not a file name character.
 */


-l"/home/--/--/--/trunk/mbdsp/Debug/configPkg/package/cfg/main_pe674.oe674"
-l"/opt/TI/syslink_2_21_00_03/packages/ti/syslink/ipc/rtos/lib/release/ti.syslink.ipc.rtos.ae674"
-l"/opt/TI/ipc_1_25_00_04/packages/ti/sdo/ipc/lib/ipc/nonInstrumented/ipc.ae674"
-l"/opt/TI/syslink_2_21_00_03/packages/ti/syslink/utils/rtos/bios6/lib/release/ti.syslink.utils.rtos.bios6.ae674"
-l"/opt/TI/bios_6_34_02_18/packages/ti/sysbios/lib/sysbios/nonInstrumented/sysbios.ae674"
-l"/opt/TI/xdctools_3_24_05_48/packages/ti/targets/rts6000/lib/ti.targets.rts6000.ae674"
-l"/opt/TI/xdctools_3_24_05_48/packages/ti/targets/rts6000/lib/boot.ae674"

--retain="*(xdc.meta)"


--args 0x64
-heap  0x0
-stack 0x1000

MEMORY
{
    OCMC_0 (RWX) : org = 0x40300000, len = 0x40000
    OCMC_1 (RWX) : org = 0x40400000, len = 0x40000
    DDR3_DATA (RWX) : org = 0x9f000000, len = 0x200000
    DDR3_CODE (RWX) : org = 0x9f200000, len = 0xc00000
    SR_0 (RWX) : org = 0x9fe00000, len = 0x100000
    SR_1 (RWX) : org = 0x9ff00000, len = 0x100000
}

/*
 * Linker command file contributions from all loaded packages:
 */

/* Content from xdc.services.global (null): */

/* Content from xdc (null): */

/* Content from xdc.corevers (null): */

/* Content from xdc.shelf (null): */

/* Content from xdc.services.spec (null): */

/* Content from xdc.services.intern.xsr (null): */

/* Content from xdc.services.intern.gen (null): */

/* Content from xdc.services.intern.cmd (null): */

/* Content from xdc.bld (null): */

/* Content from ti.targets (null): */

/* Content from ti.targets.elf (null): */

/* Content from xdc.rov (null): */

/* Content from xdc.runtime (null): */

/* Content from ti.targets.rts6000 (null): */

/* Content from ti.sysbios.interfaces (null): */

/* Content from ti.sysbios.family (null): */

/* Content from ti.sysbios.hal (null): */

/* Content from ti.sysbios (null): */

/* Content from ti.sysbios.knl (null): */

/* Content from ti.sysbios.gates (null): */

/* Content from ti.sysbios.family.c64p (null): */

/* Content from xdc.services.getset (null): */

/* Content from xdc.runtime.knl (null): */

/* Content from ti.sdo.ipc.family (null): */

/* Content from ti.sdo.utils (null): */

/* Content from ti.sdo.ipc.interfaces (null): */

/* Content from ti.sysbios.syncs (null): */

/* Content from ti.sysbios.heaps (null): */

/* Content from ti.sysbios.xdcruntime (null): */

/* Content from ti.sysbios.family.c62 (null): */

/* Content from ti.sysbios.timers.dmtimer (null): */

/* Content from ti.sysbios.family.c64p.ti81xx (null): */

/* Content from ti.syslink.utils.rtos.bios6 (null): */

/* Content from ti.sysbios.utils (null): */

/* Content from ti.catalog.c6000 (null): */

/* Content from ti.catalog (null): */

/* Content from ti.catalog.peripherals.hdvicp2 (null): */

/* Content from xdc.platform (null): */

/* Content from xdc.cfg (null): */

/* Content from ti.platforms.generic (null): */

/* Content from flexradio.microburst_dsp (null): */

/* Content from ti.sdo.ipc (ti/sdo/ipc/linkcmd.xdt): */

SECTIONS
{
    ti.sdo.ipc.SharedRegion_0:  { . += 0x100000;} run > 0x9fe00000, type = NOLOAD
    ti.sdo.ipc.SharedRegion_1:  { . += 0x100000;} run > 0x9ff00000, type = NOLOAD

    ti_sdo_ipc_init: load > DDR3_DATA, type = NOINIT
}


/* Content from ti.sdo.ipc.family.ti81xx (null): */

/* Content from ti.sdo.ipc.notifyDrivers (null): */

/* Content from ti.sdo.ipc.transports (null): */

/* Content from ti.sdo.ipc.nsremote (null): */

/* Content from ti.sdo.ipc.heaps (null): */

/* Content from ti.syslink.ipc.rtos (ti/syslink/ipc/rtos/linkcmd.xdt): */


    /*
     *  Set entry point to the HWI reset vector 0 to automatically satisfy
     *  any alignment constraints for the boot vector.
     */
    -eti_sysbios_family_c64p_Hwi0

    /*
     * We just modified the entry point, so suppress the "entry point symbol other
     * than _c_int00 specified" warning.
     */
    --diag_suppress=10063

    /* Add the flags needed for SysLink ELF build. */
    --dynamic
    --retain=_Ipc_ResetVector

    /*
     * Added symbol to ensure SysBios code is retained when entrypoint is
     * something other than _c_int00.  This workaround will be removed once
     * fixed in the SysBios package
     */
    -u _c_int00

/* Content from ti.sdo.ipc.gates (null): */

/* Content from configPkg (null): */


/*
 * symbolic aliases for static instance objects
 */
xdc_runtime_Startup__EXECFXN__C = 1;
xdc_runtime_Startup__RESETFXN__C = 1;
TSK_idle = ti_sysbios_knl_Task_Object__table__V + 0;

SECTIONS
{
    .text: load >> DDR3_CODE
    .ti.decompress: load > DDR3_CODE
    .stack: load > OCMC_0
    GROUP: load > DDR3_DATA
    {
        .bss:
        .neardata:
        .rodata:
    }
    .cinit: load > DDR3_DATA
    .pinit: load >> DDR3_DATA
    .init_array: load > DDR3_DATA
    .const: load >> DDR3_DATA
    .data: load >> DDR3_DATA
    .fardata: load >> DDR3_DATA
    .switch: load >> DDR3_DATA
    .sysmem: load > DDR3_DATA
    .far: load >> DDR3_DATA
    .args: load > DDR3_DATA align = 0x4, fill = 0 {_argsize = 0x64; }
    .cio: load >> DDR3_DATA
    .ti.handler_table: load > DDR3_DATA
    .plt: load >> DDR3_CODE
    .vecs: load >> DDR3_CODE
    xdc.meta: load >> DDR3_DATA, type = COPY

}

Hi Stephen,

Can you try rebuilding the kernel after increasing the default value of ProcMgr_MAX_MEMORY_REGIONS  from 96 to something larger. The error condition you see is tied to this constant getting exceeded during ProcMgr_map, which may be due to large number of sections (>96) getting mapped.

This constant is defined in .../ti/syslink/inc/knl/ProcDefs.h

via:

#define ProcMgr_MAX_MEMORY_REGIONS  96u

just edit and rebuild kernel and run your application again. ANd let's see if behavior changes.

Best regards,
Murat

I increased it to 192 and received this the first time I ran it:

Hi Steve,

Here is some documentation from the EZSDK which you might want to take a look for some information for a particular supported configuration and additional information about how to make changes to the memory map:

http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map

Murat