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/CCSTUDIO: CC2640R2F simple_peripheral sample - Build error with Linux installation

Part Number: CCSTUDIO
Other Parts Discussed in Thread: CC2640, CC1350

Tool/software: Code Composer Studio

Hi folks,

I have Debian 9 with XFCE graphical engine installed in my notebook. I installed the CCS  Version: 8.1.0.00011 in /home/user/ti

The SDK also is located in /home/user/ti. I have imported the simple_peripheral_cc2640r2lp_app and simple_peripheral_cc2640r2lp_stack_library into my workspace which is located in /home/user/workspace_v8.

Others informations
Compiler version: TI v18.1.2LTS
XDCTools 3.50.7.20_core
SDK version 2.20.0.49.

Firstly I build the simple_peripheral_cc2640r2lp_stack_library project and after I tried to build the simple_peripheral_cc2640r2lp_app, but I found the following error:

error #10008-D: cannot find file "/home/user/workspace_v8/simple_peripheral_cc2640r2lp_stack_library/FlashROM_Library/ble_r2.symbols"
error #10008-D: cannot find file "/home/user/workspace_v8/simple_peripheral_cc2640r2lp_stack_library/FlashROM_Library/lib_linker.cmd"

I looking for possibles solutions in other threads from this forum, but with no success.

Can anyone help me?

Thank you in advanced.

 

  • Are you sure that the build of simple_peripheral_cc2640r2lp_stack_library project completed successfully? The stack_library project contains a pre-build step that generates those two files, so I would check first whether that pre-build step ran correctly and created those two files.

  • You are right. The build simple_peripheral_cc2640r2lp_stack_library project failed. Look the log below

    **** Build of configuration FlashROM_Library for project simple_peripheral_cc2640r2lp_stack_library ****

    /home/user/ti/ccsv8/utils/bin/gmake -k -j 4 all -O

    /home/user/ti/simplelink_cc2640r2_sdk_2_20_00_49/source/ti/blestack/../../../tools/blestack/lib_search/lib_search
    /home/user/workspace_v8/simple_peripheral_cc2640r2lp_stack_library/TOOLS/build_config.opt
    /home/user/ti/simplelink_cc2640r2_sdk_2_20_00_49/source/ti/blestack/blelib
    /home/user/workspace_v8/simple_peripheral_cc2640r2lp_stack_library/FlashROM_Library/lib_linker.cmd cc2640
    /home/user/ti/simplelink_cc2640r2_sdk_2_20_00_49/source/ti/blestack/../../../tools/blestack/lib_search/lib_search.xml
    /home/user/ti/simplelink_cc2640r2_sdk_2_20_00_49/source/ti/blestack/symbols
    makefile:198: recipe for target 'pre-build' failed
    gmake[1]: [pre-build] Error 127 (ignored)

    gmake[1]: Nothing to be done for 'main-build'.

    **** Build Finished ****

    I notice that lxml is requirement for lib_search, so I installed it with apt install python-lxml. Is it correct?

    Until know I have no success with pre build.

    PS. I executed also the steps described here e2e.ti.com/.../2228206

    From this pointOnce you import your project you need to change the prebuild step on the stackLibrary project to invoke the lib_search.py script by adding ".py" to the end of the existing command as shown below in the project properties -> Build -> Steps tab. Just add .py to the existing lib_search command; everything else remains the same.

    Thanks in advanced

  • I executed the pre-build manually with the command lib_search.py. I put the arguments conform the positional arguments:
    opt Local project configuration file for stack project
    lib_dir Directory containing library files
    cmd Linker command file that will be written to
    device device (e.g. cc2640, cc1350)
    xml path to features xml
    symbol_src path directory containing symbols

    The lib_linker.cmd file was created successfully. Therefore, the simple_peripheral_cc2640r2lp_app build is OK and debbuger is OK too.

    However, inside CCS the pre-build no works.
    Any idea about this?
  • Arubu said:
    I executed the pre-build manually with the command lib_search.py.

    How does the manual command differ from the one in the pre-build step? Are they the same? 

    Try using the same command that works from command line in the CCS pre-build step. You could save off the default pre-build step command before replacing it, in case you have a need to revert back to it later.

  • Arubu,

    Since I haven’t heard back from you, I’m assuming you were able to move past this issue and will be closing this thread. If you require further support, please feel free to post a reply with an update below. Thanks!
  • Aartig,

    All works fine. The lib_search.py file had not execution permission.

    Thank you for all.