CC2652R: XDCTool Problem With Configuro Tool

Hey Sasha,

All I mean by "building a project from scratch" is that I don't want to start with an example project and build off of it.  I can see all of the commands for xs, the compiler, and the linker in the console output within CCS.

I think I have figured out my issues with the target and platform to specify to the configuro tool.  For anyone seeing this in the future, the targets supported by a particular version of XDCTools are specified in the download folder of XDCTools.  The platforms, however, come with the Simplelink SDK, separate from XDCTools.

I ended up getting System_printf to work with a barebones setup.  Again, for anyone in the future having trouble with this, here is what I did to get it working:

For some reason, the linker command file generated by the configuro tool does not fully specify how things should be allocated to memory.  The linker command file generated by the configuro tool I got is shown below:

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

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


-l"C:\Users\alarson\workspace_v10\GettingStartedWithRTOS\Debug\configPkg\package\cfg\xdccfg_pem4f.oem4f"
-l"C:\ccs.v10\simplelink_cc13x2_26x2_sdk_4_20_00_35\kernel\tirtos\packages\ti\targets\arm\rtsarm\lib\ti.targets.arm.rtsarm.aem4f"
-l"C:\ccs.v10\simplelink_cc13x2_26x2_sdk_4_20_00_35\kernel\tirtos\packages\ti\targets\arm\rtsarm\lib\boot.aem4f"
-l"C:\ccs.v10\simplelink_cc13x2_26x2_sdk_4_20_00_35\kernel\tirtos\packages\ti\targets\arm\rtsarm\lib\auto_init.aem4f"
-l"C:\ccs.v10\xdctools_3_61_01_25_core\packages\xdc\rov\runtime\lib\xdc.rov.runtime.aem4f"

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

/* C6x Elf symbols */
--symbol_map __TI_STACK_SIZE=__STACK_SIZE
--symbol_map __TI_STACK_BASE=__stack
--symbol_map _stack=__stack


--args 0x200
-heap  0x1000
-stack 0x1000

/*
 * 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.rov (null): */

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

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

/* Content from xdc.rov.runtime (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.arm.elf (null): */

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

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

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

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

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

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

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

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

/* Content from configPkg (null): */



/*
 * symbolic aliases for static instance objects
 */
xdc_rov_runtime_Mon__checksum = 1;
xdc_rov_runtime_Mon__write = 1;
xdc_runtime_Startup__EXECFXN__C = 1;
xdc_runtime_Startup__RESETFXN__C = 1;


SECTIONS
{
    .bootVecs: load > 0x0



    xdc.meta: type = COPY
}

After trying to build my project with just this generated linker command file, I got a bunch of errors telling me that there were some sections of memory which were not properly initialized.  That surprised me -- I thought the configuro tool would handle everything for me.  Therefore, I needed to create and add another linker command file to allocate the standard sections such as .text, .data, etc.  I found a linker command file called CC26X2R1_LAUNCHXL_TIRTOS.cmd in the Simplelink SDK.  It is used by the "hello" example.  I simply copy and pasted this linker command file into my project and removed a couple pieces of it which I found unnecessary.  The code is shown below:

/*
 *  ======== CC26X2R1_LAUNCHXL.cmd ========
 */

HEAPSIZE = 0x1000;  /* Size of heap buffer used by HeapMem */

/* The starting address of the application.  Normally the interrupt vectors  */
/* must be located at the beginning of the application.                      */
#define FLASH_BASE              0x0
#define FLASH_SIZE              0x58000
#define RAM_BASE                0x20000000
#define RAM_SIZE                0x14000
#define GPRAM_BASE              0x11000000
#define GPRAM_SIZE              0x2000


/* System memory map */

MEMORY
{
    /* Application stored in and executes from internal flash */
    FLASH (RX) : origin = FLASH_BASE, length = FLASH_SIZE
    /* Application uses internal RAM for data */
    SRAM (RWX) : origin = RAM_BASE, length = RAM_SIZE
    /* Application can use GPRAM region as RAM if cache is disabled in the CCFG
    (DEFAULT_CCFG_SIZE_AND_DIS_FLAGS.SET_CCFG_SIZE_AND_DIS_FLAGS_DIS_GPRAM = 0) */
    GPRAM (RWX): origin = GPRAM_BASE, length = GPRAM_SIZE
}

/* Section allocation in memory */

SECTIONS
{
    .intvecs        :   > FLASH_BASE
    .text           :   >> FLASH
    .TI.ramfunc     : {} load=FLASH, run=SRAM, table(BINIT)
    .const          :   >> FLASH
    .constdata      :   >> FLASH
    .rodata         :   >> FLASH
    .binit          :   > FLASH
    .cinit          :   > FLASH
    .pinit          :   > FLASH
    .init_array     :   > FLASH
    .emb_text       :   >> FLASH
    .ccfg           :   > FLASH (HIGH)

    .vtable         :   > SRAM
    .vtable_ram     :   > SRAM
     vtable_ram     :   > SRAM
    .data           :   > SRAM
    .bss            :   > SRAM
    .sysmem         :   > SRAM
    .stack          :   > SRAM (HIGH)
    .nonretenvar    :   > SRAM
    /* Heap buffer used by HeapMem */
    .priheap   : {
        __primary_heap_start__ = .;
        . += HEAPSIZE;
        __primary_heap_end__ = .;
    } > SRAM align 8
    .gpram          :   > GPRAM
}

My project then compiled and linked properly.  Note also that System_flush() must be called after System_printf to get things to print to the console properly.

This was a good, but at times frustrating, learning experience.

I will now try to get the RTOS up and running.  Hopefully that process is more smooth than this one.

Thank you to Ryan, Todd, and Sasha for the assistance.