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.

CCS/AWR1843: CCS/AWR1843

Part Number: AWR1843
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hello,

I have AWR1843 board with me and I am tring to run demo code of HWA given in mmwave sdk. I have created a new project and copy pasted main.c file code of demo into my main file. After a build I got some linking error which after giving library paths are resolved but some linking errors are still there for which I don't know which library or source file should be added in my project. 

**** Build of configuration Debug for project SRR6xx_HWA1.0 ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k -j 4 all -O

'Building target: "SRR6xx_HWA1.0.out"'
'Invoking: C6000 Linker'
"C:/ti/ccsv7/tools/compiler/ti-cgt-c6000_8.2.6/bin/cl6x" -mv6740 -Ooff --opt_for_speed=0 --define=__TI_NO_PARALLEL_LOADS=1 --define=SUBSYS_MSS --define=SUBSYS_DSS --define=SOC_XWR18XX -g --diag_warning=225 --diag_wrap=off --display_error_number -z -m"SRR6xx_HWA1.0.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/ccsv7/tools/compiler/ti-cgt-c6000_8.2.6/lib" -i"C:/ti/ccsv7/tools/compiler/ti-cgt-c6000_8.2.6/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="SRR6xx_HWA1.0_linkInfo.xml" --rom_model -o "SRR6xx_HWA1.0.out" "./main.obj" "../xwr1843_C674x.cmd" -l"C:/ti/mmwave_sdk_03_01_01_02/packages/ti/utils/testlogger/lib/libtestlogger_xwr18xx.ae674" -llibc.a -l"C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/soc/lib/libsoc_xwr18xx.ae674" -l"C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674" -l"C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/hwa/lib/libhwa_xwr18xx.ae674" -l"C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/hwa/lib/libhwa_xwr18xx.aer4f"
<Linking>
warning #10247-D: creating output section ".MCPILogBuffer" without a SECTIONS specification
warning #10247-D: creating output section ".sysmem" without a SECTIONS specification

undefined first referenced
symbol in file
--------- ----------------
ti_sysbios_BIOS_exit__E ./main.obj
ti_sysbios_BIOS_start__E ./main.obj
ti_sysbios_family_c64p_EventCombiner_disableEvent__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
ti_sysbios_family_c64p_EventCombiner_dispatchPlug__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
ti_sysbios_family_c64p_EventCombiner_enableEvent__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
ti_sysbios_knl_Semaphore_Params__init__S C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
ti_sysbios_knl_Semaphore_create C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
ti_sysbios_knl_Semaphore_delete C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
ti_sysbios_knl_Semaphore_pend__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
ti_sysbios_knl_Semaphore_post__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
ti_sysbios_knl_Task_Params__init__S ./main.obj
ti_sysbios_knl_Task_create ./main.obj
xdc_runtime_Assert_raise__I C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<DebugP_tirtos.oe674>
xdc_runtime_Main_Module__id__C C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<DebugP_tirtos.oe674>
xdc_runtime_Memory_alloc__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<MemoryP_tirtos.oe674>
xdc_runtime_Memory_free__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<MemoryP_tirtos.oe674>
xdc_runtime_System_printf__E ./main.obj

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "SRR6xx_HWA1.0.out" not built

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

**** Build Finished ****

I need a help to resole this errors.

Also I want to know if TI gives any document which gives detail about how to create new project in CCS with AWR1843 board?

  • Hello Mohammed,

    use Project Properties  -> General -> Products and add needed versions of RDCTools and SYS/BIOS.

  • Hello Tom,

    Below is the screenshot of my Project Properties  -> General -> Products page in which appropriate SYS/BIOS package is selected.

    Still problem is there. 

  • Hi,

    I assume you are trying to create a CCS project for the hwa test example provided in

    C:\ti\mmwave_sdk_03_01_00_02\packages\ti\drivers\hwa\test

    The easiest way to create a CCS project is to create a CCS project spec.

    Please see following thread that shows how to create a CCS project spec for the spi driver

    e2e.ti.com/.../2533370

    Thank you
    Cesar
  • Hello Cesar,
    Thank you for the thread , I checked the thread and there was this alternating approach in which library file path should be given in linker search path and additional include paths should be mentioned in compilation part which I have already done. What issue I am currently facing in build is that I am not able to understand which library is pending to get rid of the undefined symbol error which I am currently getting.

    These are the undefined errors I am getting and I don't know which library or source code is required for these.

    undefined first referenced
    symbol in file
    --------- ----------------
    ti_sysbios_BIOS_exit__E ./main.obj
    ti_sysbios_BIOS_start__E ./main.obj
    ti_sysbios_family_c64p_EventCombiner_disableEvent__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
    ti_sysbios_family_c64p_EventCombiner_dispatchPlug__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
    ti_sysbios_family_c64p_EventCombiner_enableEvent__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<HwiP_tirtos.oe674>
    ti_sysbios_knl_Semaphore_Params__init__S C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
    ti_sysbios_knl_Semaphore_create C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
    ti_sysbios_knl_Semaphore_delete C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
    ti_sysbios_knl_Semaphore_pend__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
    ti_sysbios_knl_Semaphore_post__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<SemaphoreP_tirtos.oe674>
    ti_sysbios_knl_Task_Params__init__S ./main.obj
    ti_sysbios_knl_Task_create ./main.obj
    xdc_runtime_Assert_raise__I C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<DebugP_tirtos.oe674>
    xdc_runtime_Main_Module__id__C C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<DebugP_tirtos.oe674>
    xdc_runtime_Memory_alloc__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<MemoryP_tirtos.oe674>
    xdc_runtime_Memory_free__E C:/ti/mmwave_sdk_03_01_01_02/packages/ti/drivers/osal/lib/libosal_xwr18xx.ae674<MemoryP_tirtos.oe674>
    xdc_runtime_System_printf__E ./main.obj
  • What Cesar said is correct. It is difficult to create a SysBios CCS project just by dropping in code and trying to get all the linkage correct to the required libs. It is easier to make a projectspec and let CCS automatically figure it out. All of the mmWave demos in the Automotive and Industrial toolboxes provide projectspecs that you can use as an example, and also the thread he references.

    -dave