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.

Code composer online installer does not work

Christin,

Sorry for the delay in response here - long holiday weekend and I wanted to be sure to try all avenues before popping back up.

As Chris stated in his last post, I have been working in parallel with him on a number of issues we are debugging together. I think the newest of these issues may be tangental to the bug that Chris found earlier in the BLE stack. If you deem this issue separate from this thread, please feel free to split this into it's own thread.

However, as stated earlier, we were previously working with CCS v7.2 and complier v16.9.4.LTS with the new SDK v2.30.00.34.

Per your suggestion to update compilers as it was a "dependency" for the SDK - I attempted to go through this process and continue to work through our issues.

My first step was to attempt to stay in CCS v7.2 and update only my compiler to v18.1.3.LTS - but the "Install New Software..." option listed a newer one than that v18.9.0.CTS. In an attempt of getting around having to re-update to a new compiler in the future, I downloaded v18.9.0.CTS and ran with that. Things failed, specifically I was getting errors containing text such as "gmake[1]: *** [build-xxxxx] Error 1" and "recipe for target 'build-xxxxx' failed." If I put my compiler back to v16.9.4.LTS - all was fine, and I could run my program. Every time the compiler was upgraded, the same error popped up. I continually tried the effort of cleaning, rebuilding, deleting the compiled files (the entire build folder), opening/closing CCS, and even shutting my computer down and rebooting -- all with the same result.

The next step I took was to update XDCTools to v3.50.08.24 from v3.50.05.12 - again, the same issues.

This is when I decided to "use CCS 8.2 to see if it gives me less trouble" but the online installer ran for literally 22 hours and didn't complete (wasting a day of my time) and today I used the offline installer and successfully updated to CCS v8.2, only to see the same exact issue. CCS v8.2 did install the proper compiler v18.1.3.LTS, and I ensured the XDCTools version was proper as well. This did not make a difference.

I can now confirm that all build configurations of our project do not compile, all giving the same exact build errors, as shown in the build console output below. I am running CCS v8.2.0.00007, I have compiler TI v18.1.3.LTS, I have XTCTools v3.50.08.24, and I assume TI-RTOS v3_70_00_12 is included with the current SDK 2.30.00.34. If not, I don't know where to find it, having tried the CCS App Center, Resource Explorer, and the Install New Software options all within CCS v8.2.

**** Build of configuration FlashROM_Release for project ble5_simple_peripheral_cc26x2r1lp_app ****

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O 
 
Building file: "../TOOLS/ble_release.cfg"
Building file: "../TOOLS/ble_release_modified.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_08_24_core/xs" --xdcpath="C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC2642R1F -r release -c "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS" --compileOptions "-mv7M4 --code_state=16 -me -O4 --opt_for_speed=0 --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Application\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Startup\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/PROFILES\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Include\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/controller/cc26xx/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/rom\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/target\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/heapmgr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/osal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/saddr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/sdata\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/devices/cc13x2_cc26x2_v1\" --include_path=\"C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS/include\" --define=DeviceFamily_CC26X2 -g --c99 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../TOOLS/ble_release_modified.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_08_24_core/xs" --xdcpath="C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC2642R1F -r release -c "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS" --compileOptions "-mv7M4 --code_state=16 -me -O4 --opt_for_speed=0 --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Application\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Startup\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/PROFILES\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Include\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/controller/cc26xx/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/rom\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/target\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/heapmgr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/osal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/saddr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/sdata\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/devices/cc13x2_cc26x2_v1\" --include_path=\"C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS/include\" --define=DeviceFamily_CC26X2 -g --c99 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../TOOLS/ble_release.cfg"
making package.mak (because of package.bld) ...
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring ble_release.xem4 from package/cfg/ble_release_pem4.cfg ...
configuring ble_release.xem4 from package/cfg/ble_release_pem4.cfg ...
generating custom ROM library makefile ... 
generating custom ROM library makefile ... 
TOOLS/subdir_rules.mk:12: recipe for target 'build-933296719-inproc' failed
/cygdrive/c/ti/xdctools_3_50_08_24_core/bin/mkdir: cannot create directory `package/internal': File exists
js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/cfg/Main.xs", line 48: XDC runtime error: can't find the library 'lib/boot.aem4' specified by package ti.targets.arm.rtsarm.  It wasn't found along the path 'C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;C:/ti/xdctools_3_50_08_24_core/packages;..;'.
js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/cfg/Main.xs", line 48: XDC runtime error: can't find the library 'lib/boot.aem4' specified by package ti.targets.arm.rtsarm.  It wasn't found along the path 'C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;C:/ti/xdctools_3_50_08_24_core/packages;..;'.
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Error 1
gmake.exe: *** Deleting file `package/cfg/ble_release_pem4.xdl'
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.h'
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Deleting file `package/cfg/ble_release_pem4.c'
js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-933296719-inproc] Error 1
gmake.exe: *** [package/cfg/ble_release_pem4.xdl] Error 1
gmake: *** [build-933296719] Error 2
TOOLS/subdir_rules.mk:9: recipe for target 'build-933296719' failed
TOOLS/subdir_rules.mk:26: recipe for target 'build-1288926767-inproc' failed
js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[1]: *** [build-1288926767-inproc] Error 1
TOOLS/subdir_rules.mk:23: recipe for target 'build-1288926767' failed
gmake: *** [build-1288926767] Error 2
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

Where exactly are we to go with this now? Do the above build errors mean anything specific that we can fix to get our code to build with this new compiler?

On a different note, it's quite concerning that we need to update IDEs, compilers, software, and more every time the SDK is changed, and we can't just continue to run our setup with the new software added in. If we have to wade through this level of effort and debug every time there is a code change on TI's side, I think that that is an indication of poor tool support, which is disappointing to see.

  • Christin, 

    Disregard the Console message in the previous post - I had two .cfg files included in the project, so it was invoking XDCTools twice. After fixing this, I still get a similar issue - but with a different message. Updated Console message is below.

    **** Build of configuration FlashROM_ReleaseModified for project ble5_simple_peripheral_cc26x2r1lp_app ****
    
    "C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O 
     
    Building file: "../TOOLS/ble_release_modified.cfg"
    Invoking: XDCtools
    "C:/ti/xdctools_3_50_08_24_core/xs" --xdcpath="C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC2642R1F -r release -c "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS" --compileOptions "-mv7M4 --code_state=16 -me -O4 --opt_for_speed=0 --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Application\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Startup\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/PROFILES\" --include_path=\"C:/Users/twitt.SENTRILOCK/Documents/Projects/Lockbox/Gen4/Firmware/workspace/ble5_simple_peripheral_cc26x2r1lp_app/Include\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/controller/cc26xx/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/rom\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/target\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/target/_common/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/hal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/heapmgr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/icall/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/osal/src/inc\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/saddr\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/sdata\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack/services/src/nv/cc26xx\" --include_path=\"C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/devices/cc13x2_cc26x2_v1\" --include_path=\"C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS/include\" --define=DeviceFamily_CC26X2 -g --c99 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../TOOLS/ble_release_modified.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring ble_release_modified.xem4 from package/cfg/ble_release_modified_pem4.cfg ...
    generating custom ROM library makefile ... 
    TOOLS/subdir_rules.mk:12: recipe for target 'build-1288926767-inproc' failed
    js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/cfg/Main.xs", line 48: XDC runtime error: can't find the library 'lib/boot.aem4' specified by package ti.targets.arm.rtsarm.  It wasn't found along the path 'C:/ti/ccsv8/ccs_base;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source/ti/ble5stack;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/source;C:/ti/simplelink_cc26x2_sdk_2_30_00_34/kernel/tirtos/packages;C:/ti/xdctools_3_50_08_24_core/packages;..;'.
    gmake.exe: *** [package/cfg/ble_release_modified_pem4.xdl] Error 1
    gmake.exe: *** Deleting file `package/cfg/ble_release_modified_pem4.xdl'
    gmake.exe: *** [package/cfg/ble_release_modified_pem4.xdl] Deleting file `package/cfg/ble_release_modified_pem4.h'
    gmake.exe: *** [package/cfg/ble_release_modified_pem4.xdl] Deleting file `package/cfg/ble_release_modified_pem4.c'
    js: "C:/ti/xdctools_3_50_08_24_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake[1]: *** [build-1288926767-inproc] Error 1
    gmake: *** [build-1288926767] Error 2
    TOOLS/subdir_rules.mk:9: recipe for target 'build-1288926767' failed
    gmake: Target 'all' not remade because of errors.
    
    **** Build Finished ****
    

  • Christin,

    I found the issue to the issue in my two previous posts - when you change the compiler version it will change your target under the CCS General -> Products tab from ti.targets.arm.elf.M4F to ti.targets.arm.elf.M4.

    Then it goes looking for the wrong files and fails.

    I'm not sure this is an intended action for CCS to change - especially as even if you re-confirm your part variant under CCS General -> Project tab as CC2642R1F, it does not return to the correct version of M4F.

    Now that we have an actual working debug environment, we will be able to assess if the connection issue is any better when the code is compiled under these circumstances.

  • Hi,

    Sorry that you need to go through all the trouble the get out of box project work.

    We are continuously improving our tool and thus we would like to take advantage on the improvement in our newest SDK. That's why we update our tool dependency as often as possible to make sure users can have better user experience and better code size optimization.

    I separated your thread to bring attention to our CCS team that the online installer took 22hr and did not finish installing new CCS.
  • Tyler,

    TylerWitt said:
    This is when I decided to "use CCS 8.2 to see if it gives me less trouble" but the online installer ran for literally 22 hours and didn't complete (wasting a day of my time) and today I used the offline installer and successfully updated to CCS v8.2, only to see the same exact issue. 

    Every now and then we get reports of the online installer getting stuck because of connection timeouts. The offline installer typically resolves such issues. I'm glad to hear you are up and running now and sorry that you had to go through the earlier troubles. If you hit this issue again in the future with a different version of CCS please let us know and provide us with the installation logs so we can investigate further.

    TylerWitt said:
     when you change the compiler version it will change your target under the CCS General -> Products tab from ti.targets.arm.elf.M4F to ti.targets.arm.elf.M4.

    Were you on CCS 7.2 when you hit this issue? It sounds a bit familiar and could have been a bug in that version of CCS. If you see a similar issue when working with CCS 8.2 please let us know. 

  • AartiG,

    I see the issue on both CCS 7.2 and CCS 8.2.

    The easiest way I've found to replicate it is to just change the compiler version in the Project tab of the CCS General properties window, then switch over to the Products tab to see that it has been changed. I've been able to get this change to happen when changing my compiler from 18.1.3.LTS down to 16.9.4.LTS as well as the other way around.

    It seems like a silly issue that should be able to be fixed by a setting in the Device Variant or something like that. After all, the core of the device you are debugging should be dictating what target the compiler is building for.

    Regards,
    Tyler

  • Tyler,

    TylerWitt said:
    The easiest way I've found to replicate it is to just change the compiler version in the Project tab of the CCS General properties window, then switch over to the Products tab to see that it has been changed. I've been able to get this change to happen when changing my compiler from 18.1.3.LTS down to 16.9.4.LTS as well as the other way around.

    Thank you for the details. I was able to reproduce this behavior in CCS 8.2. Changing the compiler version should not impact the RTSC Target field so this is definitely a bug. I filed bug ID CCSIDE-3460 to track this issue. Feel free to track its status using the SDOWP link in my signature. For the moment, the workaround (as you already determined) is to manually set the Target field back to ti.targets.arm.elf.M4F.

    Thank you for bringing this to our attention.

  • Just an update for folks that might be interested in tracking this bug report.

    The bug was initially filed as CCSIDE-3460, however after investigation the root cause was found to be SYS/BIOS so the bug was migrated to SYS/BIOS and the new tracking ID is SYSBIOS-848. It is fixed in SYS/BIOS version 6.76.xx.