CC2640R2F: build sample project in mac fail

Hi dsp999,

Your project build appears to be using XDCTools v3.62, but the SimpleLink CC2640R2 SDK v5.10 Release Notes mention a dependency on XDCTools v3.51 which also appears to have been downloaded locally.  Are you able to select Compiler Version 18.12.2.LTS from CCS Project Properties -> CCS General -> Project Tab and/or install then add the correct XDCTools version to the CCS Project Properties -> CCS General -> Product Tab?  Perhaps consider evaluating with CCS v9.0 as well since this version was used to build and test the SimpleLink SDK.

Regards,
Ryan

have managed to set xdc 3.51 as attached picture, but problem still there.

so....where to get CCS9.0 for mac?

You can get it from the Previous Versions section of the CCSTUDIO Download (CCS v9.3 may work as well) or you can visit Code Composer Studio Downloads.  Both options include MAC OS installers.

Regards,
Ryan

CCS9.3  is totally fail. see picture.

besides, even if I make CCS work, can I download/program to the customer board with XDS110? (does it has driver on macbook?)

 this is my macbook version

The first CCS release that will be properly validated on Monterey will be CCSv11.1.0.

Today I would use CCSv10.4 and make sure to have the XDCTools (3.51) and Compiler (18.12) that the SDK requires.  If you install the SDK from Resource Explorer inside CCS will download all of that automatically.  The project should automatically use those if they are installed.

I would then recommend installing CCSv11.0 when it comes out in a week as it has some fixes for macOS BigSur that I am sure will apply to macOS Monterey as well.

John

I have installed CCS V11.1.0 now. 

then I build sample, error.

then I go on try set xds tool from 3.62 to 3.51

then go back to try again, this time, I can not import the sample project!

what can I do?

You will have to completely delete the existing example from your workspace before you can import it again.  It may be worth checking if any other BLE application projects can be imported.  You should also consider fully removing the incorrect XDCTools if it continues to interfere with your build.

Regards,
Ryan

I have : 

1, delete all files in workspace folder, make it empty

2, removing xdctools unused

problem still the same

To summarize, your CCS 11 environment is still referring to XDCTools 3.62 (although not installed) with the SimpleLink SDK v5.10 on macOS Monterey?  And you cannot import a new project even if the existing workspace folder's contents are fully erased or a new workspace folder is created?

Regards,
Ryan

YES.

workspace folder is empty.

In the screen capture of the build error, it shows "line 52: Error: xdc.tools.configuro...".  Is it possible to get the rest of the error message.  One error I have see is that for some reason xdctools is not able to find the "platform".  Typically the platform name is specified in the project and then the files for it are part of the SDK.

For example if I import that same example This is what I see.  Do your settings look identical to this?

I suspect that the import problem is related.  Usually when you import and there is an error it gives you a popup explaining the error.  Something like this:

If you put your mouse over the red X on the project icon it may provide more info on why the project cannot be imported.

Regards,

John

One of my colleagues had a good point.  That import error is likely happening because you had previously had those projects in your workspace but when they were removed they were not deleted from the file-system.  That will prevent CCS from importing them into the workspace again.  

Basically if the box below was not checked then the files are still there:

In the import wizard if you put your mouse over the error indicator it would show something like this. You may have to move the mouse around a bit to get the tooltip to appear on macOS.

To recover from that you can either.

1) Create a new workspace

2) Close CCS.  Go to your workspace folder in Finder.  Delete the project folders.  Restart CCS

Note that when importing the projects with the import wizard you just need to select the app project and the stack project will get imported automatically.

Regards,

John

after I start ccs with a new workspace I can import now. but build still fail. then I rename the xdctools_3_62_01_16_core folder to make sure it does not use this version of xdctools, then I get the below building error:

Now it appears that the wrong compiler version is selected in the CCS General -> Project options inside the Project Properties, the SIMPLELINK-CC2640R2-SDK should use 18.12.2.LTS https://www.ti.com/tool/download/ARM-CGT-18/18.12.2.LTS 

Regards,
Ryan

The first error is a linker error where it is failing to find the symbol file for SYS/BIOS (which is in ROM).  It is looking in a path in your project. 

As far as I can tell that is an output of xdctools.  That must be failing eariler in the build.  You could check your build output to see if there is an error when xdctools runs.  it should also state where it generated the file.

Building file: "../TOOLS/app_ble.cfg"

Invoking: XDCtools

"/Applications/ti/ccs1100b11/xdctools_3_62_01_16_core/xs" --xdcpath="/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source;/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/kernel/tirtos/packages;/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2640R2F -r release -c "/Users/a0792138/ti/ti-cgt-arm_18.12.5.LTS" --compileOptions "-mv7M3 --code_state=16 -me -O4 --opt_for_speed=0 --include_path=\"/Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app\" --include_path=\"/Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app/Application\" --include_path=\"/Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app/Startup\" --include_path=\"/Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app/PROFILES\" --include_path=\"/Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app/Include\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/controller/cc26xx/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/rom\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/common/cc26xx\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/icall/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/target\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/target/_common\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/target/_common/cc26xx\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/heapmgr\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/icall/src/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/osal/src/inc\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/services/src/saddr\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/services/src/sdata\" --include_path=\"/Users/a0792138/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/devices/cc26x0r2\" --include_path=\"/Users/a0792138/ti/ti-cgt-arm_18.12.5.LTS/include\" --define=DeviceFamily_CC26X0R2 -g --c99 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../TOOLS/app_ble.cfg"

making package.mak (because of package.bld) ...

generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

configuring app_ble.xem3 from package/cfg/app_ble_pem3.cfg ...

generating custom ROM library makefile ...

Starting build of library sources ...

making /Users/a0792138/workspace_v11b11_2/ble5_simple_peripheral_cc2640r2lp_app/TOOLS/src/sysbios/rom_sysbios.aem3 ...

1, I don't know how to import or open project again, it can import again. so I have to make a new workspace and do it again. is there better way?

2, I can not set 18.12.2.LTS. see snapshot

3, I build again and get the below error message. (stack build is ok)

dsp999 said:

I don't know how to import or open project again, it can import again. so I have to make a new workspace and do it again. is there better way?

Select "Delete project contents on disk (cannot be undone)" when removing the project from the workspace in CCS or delete the project folder from your workspace folder using your system's File Explorer.

dsp999 said:

I can not set 18.12.2.LTS. see snapshot

Go to Project Properties -> CCS General -> Compiler Version -> More -> Add Tool discovery path and select the folder containing the desired downloaded version.

Regards,
Ryan

1, do I have to delete the previous workspace folder and import every time I launch CCS? do I have other way to open the project which I have already imported last time?

2, where to download 18.12.2.lts compiler? I do not have this on my computer.

1. Once a project is imported, it should be available in your workspace.

2. https://www.ti.com/tool/download/ARM-CGT-18/18.12.2.LTS 

**** Build of configuration FlashROM_StackLibrary for project ble5_simple_peripheral_cc2640r2lp_app ****

/Applications/ti/ccs1100/ccs/utils/bin/gmake -k -j 7 all -O 

Building file: "../TOOLS/app_ble.cfg"

Invoking: XDCtools

"/Applications/ti/xdctools_3_51_03_28_core/xs" --xdcpath="/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source;/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/kernel/tirtos/packages;/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.simplelink:CC2640R2F -r release -c "/Applications/ti/ti-cgt-arm_18.12.2.LTS" --compileOptions "-mv7M3 --code_state=16 -me -O4 --opt_for_speed=0 --include_path=\"/Users/franson/CCSWorkSpace/test/ble5_simple_peripheral_cc2640r2lp_app\" --include_path=\"/Users/franson/CCSWorkSpace/test/ble5_simple_peripheral_cc2640r2lp_app/Application\" --include_path=\"/Users/franson/CCSWorkSpace/test/ble5_simple_peripheral_cc2640r2lp_app/Startup\" --include_path=\"/Users/franson/CCSWorkSpace/test/ble5_simple_peripheral_cc2640r2lp_app/PROFILES\" --include_path=\"/Users/franson/CCSWorkSpace/test/ble5_simple_peripheral_cc2640r2lp_app/Include\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/controller/cc26xx/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/rom\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/common/cc26xx\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/icall/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/target\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/target/_common\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/target/_common/cc26xx\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/hal/src/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/heapmgr\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/icall/src/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/osal/src/inc\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/services/src/saddr\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/ble5stack/services/src/sdata\" --include_path=\"/Applications/ti/simplelink_cc2640r2_sdk_5_10_00_02/source/ti/devices/cc26x0r2\" --include_path=\"/Applications/ti/ti-cgt-arm_18.12.2.LTS/include\" --define=DeviceFamily_CC26X0R2 -g --c99 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../TOOLS/app_ble.cfg"

making package.mak (because of config.bld) ...

TOOLS/subdir_rules.mk:10: recipe for target 'build-1103652863-inproc' failed

js: "/Applications/ti/xdctools_3_51_03_28_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 139); 'linker.cmd' deleted.

gmake[1]: *** [build-1103652863-inproc] Error 1

gmake: *** [build-1103652863] Error 2

TOOLS/subdir_rules.mk:7: recipe for target 'build-1103652863' failed

gmake: Target 'all' not remade because of errors.

**** Build Finished ****

It appears that this is an XDCTools issue, even the latest version does not yet support MacOS Monterey according to the Release Notes.  I am following up with this Tools Team to determine when an update can be expected but even then I am not confident that it will be compatible with the current released SimpleLink CC2640R2 SDK.

Regards,
Ryan