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/LAUNCHXL-CC26X2R1: Rebuild display driver failed

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: AM3352, SIMPLELINK-CC13X2-26X2-SDK

Tool/software: Code Composer Studio

Hi Ti Experts,

I study the link as below and try to rebuild display driver got failed.
 https://dev.ti.com/tirex/explore/node?node=AE7RAnqQArlbuhRki8hahA__pTTHBmu__LATEST

/gcc/m4f/display.a ...
clm4fg package/package_ti.display.c ...
clm4fg Display.c ...
clm4fg DisplayExt.c ...
clm4fg DisplayHost.c ...
clm4fg DisplaySharp.c ...
clm4fg DisplayUart.c ...
clm4fg DisplayUart2.c ...
clm4fg lcd/SharpGrLib.c ...
clm4fg DisplayDogm1286.c ...
clm4fg lcd/LCDDogm1286.c ...
clm4fg lcd/LCDDogm1286_util.c ...
archiving package/lib/lib/display/package/package_ti.display.om4fg package/lib/lib/display/Display.om4fg package/lib/lib/display/DisplayExt.om4fg package/lib/lib/display/DisplayHost.om4fg package/lib/lib/display/DisplaySharp.om4fg package/lib/lib/display/DisplayUart.om4fg package/lib/lib/display/DisplayUart2.om4fg package/lib/lib/display/lcd/SharpGrLib.om4fg package/lib/lib/display/DisplayDogm1286.om4fg package/lib/lib/display/lcd/LCDDogm1286.om4fg package/lib/lib/display/lcd/LCDDogm1286_util.om4fg into lib/display.am4fg ...
clrm4f package/package_ti.display.c ...
C:/Users/Think/AppData/Local/Temp/make16196-2.sh: 1: C:/Users/Think/AppData/Local/Temp/make16196-2.sh: Syntax error: "(" unexpected
gmake[1]: *** [lib/iar/m4f/display.a.mak:18: package/lib/lib/iar/m4f/display/package/package_ti.display.orm4f] Error 2
xdctools_3_61_02_27_core\gmake.exe: *** [c:/ti/xdctools_3_61_02_27_core\packages\xdc\bld\xdc_top.mak:387: .,.libraries] Error 2
gmake: *** [makefile:50: all] Error 2

C:\ti\simplelink_cc13x2_26x2_sdk_4_30_00_54\source\ti\display>


Thanks a lot.

BRs,

Zell Wu

  • Hi Zell,

    With what project are you trying to rebuild and evaluate the Display TI Driver?  Have you referred to the display example and Display.h file reference?  Please note that the BLE-5 Stack User's Guide contains references for enabling/disabling display capabilities.

    Regards,
    Ryan

  • Hi Ryan,

    Our project needs to use UART interface to communicate between AM3352 by HEX message. 
    System hangs after I merged the uartecho project to my current project.

    However, the display driver can be rebuilt now. Thanks.

    BRs,
    Zell Wu

  • Hi Zell,

    The Display TI Driver is only for generating output from the CC2652R1, if you need bilateral communication then you should disable this interface and use a full UART TI Driver instance instead.  You can utilize the Network Processor Interface (NPI) and Transport Layer (TL) of the BLE5-Stack to further understand a host implementation if this is what you are trying to accomplish.

    Regards,
    Ryan

  • Hi Ryan,

    Thank you. I will try it.

    BRs,

    Zell Wu

  • Hi Ryan,

    I removed "Display" and enable "UART" at multi_role.syscfg, but I also got compile error.

    What else should  be configured to remove "Display"?

    undefined first referenced
    symbol in file
    --------- ----------------
    Display_doClearLines <whole-program>
    Display_doOpen <whole-program>
    Display_doPrintf <whole-program>

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

    >> Compilation failure
    makefile:180: recipe for target 'multi_role_CC26X2R1_LAUNCHXL_tirtos_ccs.out' failed
    gmake[1]: *** [multi_role_CC26X2R1_LAUNCHXL_tirtos_ccs.out] Error 1
    makefile:176: recipe for target 'all' failed
    gmake: *** [all] Error 2

    **** Build Finished ****

    BRs,

    Zell Wu

  • You should define Display_DISABLE_ALL in your Project Properties -> Build -> ARM Compiler -> Predefined Symbols, this worked for me using the default SIMPLELINK-CC13X2-26X2-SDK v4.30 multi-role example.

    Regards,
    Ryan