• Locked Locked
  • Replies 12 replies
  • Subscribers 55 subscribers
  • Views 3847 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Compilation error: Cannot open command file './configPkg/compiler.opt'

Harald Ilg
Genius 3060 points
Other Parts Discussed in Thread: SYSBIOS, CC2640

Hy,

all of a sudden (it wasn't me...) my project does not rebuild any more. Compilation error is "cannot open source file "ti/sysbios/knl/Clock.h" etc, root cause is probably the error message "ERROR: Cannot open command file './configPkg/compiler.opt': No such file or directory"

When I copy the file "compiler.opt.defs" to "compiler.opt" in folder myProject\CC26xx\CCS\myProject\FlashROM\configPkg\ everything works fine.

1) What did I change? Project works fine for some months now, I did not change any settings intentionally, even switched back to an older svn version, error persists. Deleted projects and reimported as CCS project, error persists. There was an automatic update of CCS last night (TI ARM compiler 5.2.6?) It is not used in my project (still using TI 5.2.4), does that installation have negative side effects?

2) Who is responsible to create the compiler.opt file in configPkg? It gets deleted on a "clean" or "rebuild

I use Code Composer Studio Version: 6.1.0.00104 and work with a CC2640.

Any help appreciated, regards

Harald

//Edit:unfortunately, "everything works fine" is not correct. The project builds with no errors, but it would not run (no advertsing...). In the meantime I even switched to a different workspace which I used for a different branch of development, which I have not touched for some weeks. Same behaviour. I am in trouble...

  • TI__Mastermind 29650 points
    Hi Harald,

    All the content in configPkg.opt are generated when the TI RTOS kernel are built. compiler.opt is used as input to the compiler when building the application itself (after the kernel build is done). Similarly there is a linker.cmd which is input to the linker.

    The compiler.opt file is in a build from last week similar to the compiler.opt.defs except for the following: --endian=little -mv7M3 --abi=eabi
    Since the include path for the TIRTOS_path\products\bios_6_42_xxx\packages is a part of this the compiler will fail on including the file as you see.

    Tested updating my installation of CCS 6.1.1 and SimpleBLEPeripheral still works fine on my side (both compiler.opt / compiler.opt.defs are generated).

    I cannot see why this should happen so I am moving the thread over to the Code Composer Studio forum, hopefully they should be able to sort this out. (Note they are on US time)

    Found similar threads here if it helps:
    e2e.ti.com/.../1556086
    e2e.ti.com/.../1559949

    Regards,
    Svend
  • in reply to svendbt
    Genius 3060 points

    Hy Svend,

    thanks a lot for your quick response and your hints about related threads. In the meantime, I installed the CCS on another PC, everything works fine there. When I compare the build output, I see the following items only on the PC, that works fine:

    'Building file: C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/appBLE.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_31_01_33_core/xs" --xdcpath="C:/ti/tirtos_simplelink_2_13_00_06/packages;C:/ti/tirtos_simplelink_2_13_00_06/products/bios_6_42_00_08/packages;C:/ti/tirtos_simplelink_2_13_00_06/products/uia_2_00_02_39/packages;C:/ti/xdctools_3_31_01_33_core/packages;C:/ti/ccsv6/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2640F128 -r release -c "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5" --compileOptions "-mv7M3 --code_state=16 --abi=eabi -me -O2 --opt_for_speed=0 --fp_mode=relaxed --include_path=\"C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.5/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/Source/Application\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ICall/Include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/Profiles/Roles/CC26xx\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/Profiles/Roles\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/Profiles/LoggerDataProfile\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/Profiles/SysProfile\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/Profiles/ConfigureProfile\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/applib/heap\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/ble/hci\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/ble/controller/CC26xx/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/ble/host\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/hal/target/CC2650TIRTOS\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/hal/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/hal/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/osal/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/services/sdata\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/services/saddr\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/icall/include\" --include_path=\"C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Components/ble/include\" --include_path=\"C:/ti/tirtos_simplelink_2_13_00_06/products/cc26xxware_2_21_01_15600\" --include_path=\"C:/ti/tirtos_simplelink_2_13_00_06/packages/ti/boards/Sensortag/interfaces\" --include_path=\"C:/ti/tirtos_simplelink_2_13_00_06/packages/ti/boards/Sensortag/devices\" --include_path=\"C:/ti/tirtos_simplelink_2_13_00_06/packages/ti/boards/STSPrototypeBoard\" -g --define=USE_ICALL --define=BST01 --define=POWER_SAVING --define=SBP_TASK_STACK_SIZE=700 --define=GAPROLE_TASK_STACK_SIZE=520 --define=HEAPMGR_SIZE=2672 --define=TI_DRIVERS_SPI_DMA_INCLUDED --define=TI_DRIVERS_I2C_INCLUDED --define=ICALL_MAX_NUM_TASKS=3 --define=ICALL_MAX_NUM_ENTITIES=6 --define=FEATURE_OAD --define=xdc_runtime_Assert_DISABLE_ALL --define=xdc_runtime_Log_DISABLE_ALL --define=MAX_NUM_BLE_CONNS=1 --define=CC26XXWARE --define=CC2650EM_4XS --define=CC26XX --define=ccs --define=DEBUG --define=CC2640F128RGZ --define=STSREALHW --diag_wrap=off --diag_suppress=48 --diag_warning=225 --display_error_number --gen_func_subsections=on " "C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/appBLE.cfg"
making package.mak (because of package.bld) ...
configuring appBLE.xem3 from package/cfg/appBLE_pem3.cfg ...
generating custom ROM library makefile ... 
Starting build of library sources ...
making C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/src/sysbios/sysbios.aem3 ...
gmake[1]: Entering directory `C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/src/sysbios'
Preprocessing library source files ...
Library build complete.
gmake[1]: Leaving directory `C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/src/sysbios'
Build of libraries done.
clem3 package/cfg/appBLE_pem3.c ...
'Finished building: C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/appBLE.cfg'
' '

    So apparently, the TI RTOS kernel is not built on my original PC. What can I do to have it build again?

    Best regards

    Harald

  • in reply to Harald Ilg
    TI__Mastermind 29650 points
    I have never encountered this issue before so hard to say. It would be helpful if you could share the build log of the failing build as well.

    Regards,
    Svend
  • in reply to svendbt
    Genius 3060 points
    Hy,
    my final workaround was a complete new installation of BLE Stack and CCS. So now, it is up and running again.
    I didn't save the failing build's log output. The first couple of lines were identical to the running one, than the lines from my last post were missing, the next thing in the log was the compilation of the first .c file with the error message "ERROR: Cannot open command file './configPkg/compiler.opt".
    So anyway, a fresh install helped me out, still, it would be kind of interesting what happened to my original installation.
    Harald
    P.S. I updated the ARM compiler on my second PC to 5.2.6, it still works. On my original PC, I don't dare...
  • in reply to Harald Ilg
    Genius 3060 points

    Hy,

    it happened again. Same symptoms, same workaround (Complete deinstallation, complete reinstallation). Again, I suspect some CCS update to be responsible. I hope, this doesn't happen too often, because it costs me a couple of hours to reinstall the whole IDE and all project environment. Is there any information I could give, that helps to find the root cause of my trouble? I would track this down the next time it happens...

    Regards

    Harald

  • in reply to Harald Ilg
    Genius 3060 points

    And again, after one day of working, again after installing all available update. Unfortunately I can't revert to my old installation due to

    > If you have a problem, can you list the exact modifications to the reference project you are using?

    I started from SimpleBLEPeripheral and did a lot of changes, but actually only application things, not that much system wise.

    > Do the default projects build w/o error?

    Yes, the original SBP compiles without problems.

    On error case, this is the build log: 5367.BuildLog.txt

    This is the project file of the project, that does not compile any more:

    8400.cproject.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <?fileVersion 4.0.0?><cproject storage_type_id="org.eclipse.cdt.core.XmlProjectDescriptionStorage">
    <storageModule configRelations="2" moduleId="org.eclipse.cdt.core.settings">
    <cconfiguration id="com.ti.ccstudio.buildDefinitions.TMS470.Default.67178137">
    <storageModule buildSystemId="org.eclipse.cdt.managedbuilder.core.configurationDataProvider" id="com.ti.ccstudio.buildDefinitions.TMS470.Default.67178137" moduleId="org.eclipse.cdt.core.settings" name="FlashROM">
    <externalSettings/>
    <extensions>
    <extension id="com.ti.ccstudio.errorparser.CoffErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="com.ti.ccstudio.errorparser.LinkErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="com.ti.ccstudio.errorparser.AsmErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="com.ti.rtsc.XDCtools.parsers.ErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="com.ti.rtsc.XDCtools.parsers.ErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="org.eclipse.rtsc.xdctools.parsers.ErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
    <extension id="com.ti.ccstudio.binaryparser.CoffParser" point="org.eclipse.cdt.core.BinaryParser"/>
    </extensions>
    </storageModule>
    <storageModule moduleId="cdtBuildSystem" version="4.0.0">
    <configuration artifactExtension="out" artifactName="${ProjName}" buildProperties="" cleanCommand="${CG_CLEAN_CMD}" description="" errorParsers="org.eclipse.rtsc.xdctools.parsers.ErrorParser;com.ti.rtsc.XDCtools.parsers.ErrorParser;com.ti.ccstudio.errorparser.CoffErrorParser;com.ti.ccstudio.errorparser.LinkErrorParser;com.ti.ccstudio.errorparser.AsmErrorParser" id="com.ti.ccstudio.buildDefinitions.TMS470.Default.67178137" name="FlashROM" parent="com.ti.ccstudio.buildDefinitions.TMS470.Default" postbuildStep="&quot;${CG_TOOL_HEX}&quot; -order MS --memwidth=8 --romwidth=8 --intel -o &quot;${ProjName}.hex&quot; &quot;${ProjName}.out&quot;;python c:\Python27\Scripts\hexmerge.py --overlap=error -o &quot;${ProjName}AllIncluded.hex&quot; &quot;${ProjName}.hex&quot; &quot;../../&quot;${ProjName}Stack&quot;/FlashRom/${ProjName}Stack.hex&quot; &quot;${PROJECT_BLE_ROOT}/util/BIM_extflash_Lyten/CCS/FlashOnly_SensorTag/BIM_ExtFlashLyten.hex&quot;" prebuildStep="cmd.exe /c echo // &gt;&gt; &quot;${SOURCE_ROOT}\Application\devinfoservice_.c&quot;">
    <folderInfo id="com.ti.ccstudio.buildDefinitions.TMS470.Default.67178137." name="/" resourcePath="">
    <toolChain id="com.ti.ccstudio.buildDefinitions.TMS470_5.2.exe.DebugToolchain.234296018" name="TI Build Tools" superClass="com.ti.ccstudio.buildDefinitions.TMS470_5.2.exe.DebugToolchain" targetTool="com.ti.ccstudio.buildDefinitions.TMS470_5.2.exe.linkerDebug.802016903">
    <option id="com.ti.ccstudio.buildDefinitions.core.OPT_TAGS.1849686932" superClass="com.ti.ccstudio.buildDefinitions.core.OPT_TAGS" valueType="stringList">
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This is my installation details:

    What other information would be helpful to track down my problem? Any hints are highly appreciated!

    Regards

    Harald

  • in reply to Harald Ilg
    TI__Mastermind 29650 points
    Hi Harald,

    I am very sorry that you are experiencing these issues with CCS. We (in LPRF) have not seen others having these issues so I cannot give you an exact answer on what is going on. I will get in touch with our tools team + the CCS team to see if they can figure out what goes wrong here.

    Regards,
    Svend
  • in reply to Harald Ilg
    TI__Guru** 105180 points
    Hello,

    There is no CC13XX/CC26XX device support listed in your install details snap shot, so any CC2640 build will fail. Can you re-run the installer and post screen grabs of the install screens which has wireless MCU support (?) selected.

    Best wishes
  • in reply to svendbt
    TI__Guru**** 451251 points
    Hi Harald,
    Can you try cleaning the project and then rebuilding? Then please attach the full build log here. I'm most interested in the compilation of the SYS/BIOS appBLE.cfg file. I suspect that it failed and that is the root cause.

    Thanks
    ki
  • in reply to JXS
    Genius 3060 points

    Hy JXS,

    > Can you re-run the installer and post screen grabs of the install screens which has wireless MCU support (?) selected.
    thanks for the response. At this moment, I have a running environment and am not able to do more trials, because the project is in a critical phase. But as soon as it gets a bit slower, I will try to generate my error state again. I am pretty sure, that I am able to do so by installing all availabe updates. And then, I will create a screenshot of the install page with the selection of wireless MCU. I know for sure that I enable this during original setup and never touch it again. The only thing that changes my installation is the automatic updates started from within CCS.
    I'll get back to you as soon as I have the erroneous state again.
    Regards, Harald

  • in reply to Ki
    Genius 3060 points

    Hy Ki,

    >Can you try cleaning the project and then rebuilding?

    Well, this is actually what brings me in trouble in the first place. I have a running develoment environment and work with no problems for some weeks. Then, I suspect after an update, I still can work without problems until I do a "Clean" or "Rebuild". Then, the described error happens. When I rename the existing "compiler.opt.defs" to "compiler.opt", it will compile again, but my project won't run on the target.

    > I'm most interested in the compilation of the SYS/BIOS appBLE.cfg file. I suspect that it failed and that is the root cause.

    Apparently, the SYS/BIOS does not build at all. I am pretty sure, that this is the root cause.

    When I compare a running build log with my failing one, I am missing the very first lines

    'Building file: C:/ti/simplelink/ble_cc26xx_2_01_00_44423/Projects/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/appBLE.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_31_01_33_core/xs" --xdcpath="C:/ti/tirtos_simplelink_2_13_00_06/packages;C:/ti/tirtos_simplelink_2_13_00_06/products/bios_6_42_00_08/packages;/ble/ProofOfConceptRealHW/CC26xx/CCS/Config/appBLE.cfg"  (...)
making package.mak (because of package.bld) ...

    I didn't find out, who is responsible to build the SYS/BIOS at all. I tried the workaround described in this post, but it didn't change a thing.

    Best regards

    Harald

  • in reply to Harald Ilg
    TI__Guru**** 451251 points

    Harald Ilg said:
    Apparently, the SYS/BIOS does not build at all. I am pretty sure, that this is the root cause.

    When you experience the same symptoms again, can you try:

    In Windows Explorer (or whatever system file browser):

    Browse to the following folder: C:\ti\simplelink\ble_cc26xx_2_01_00_44423\Projects\ble\<PROJECT>\CC26xx\CCS\Config and delete the 'src' folder inside.

    Then rebuild again.