MSP432E401Y: CCS 20.2 Exceptions when opening SysConfig

Now I'm wondering if this processor is even supported by CCS 20.2.  I tried creating a new project and it can't find the processor.  I even tried with the online compiler and it doesn't seem to be supported.  This is the latest version of CCS and it is referenced as the development tool for the MSP432E401Y on the product page.  Can someone please confirm whether or not this version supports the MSP432E401Y?

I noticed there were two versions of SysConfig.  How do I disable 1.24 and enable 1.5.0?  Or how do I install 1.21.2?  What about the compilers?  When I tried to import a example project, I got a message saying there were no compilers supporting this processor installed.  Should the CCS20.2 install the right compilers for the MSP432E401Y?

CCS does not ship with every compiler.

Each project can specify its dependencies (SDK, compiler, SysConfig)...  The MSP432E examples projects do this for the compiler (that is why you saw the message when you imported) but not SysConfig.

In CCSv20 this information is located under dependencies.  In CCSv12 and earlier I think it was products and tools (split in 2).

You can download specific SysConfig and Compiler versions from TI.com or you can do it from within CCS.

TI.com SysConfig page: https://www.ti.com/tool/download/SYSCONFIG

Ti.com older armcl compiler: https://www.ti.com/tool/download/ARM-CGT

It you install in C:\ti then CCS should find them automatically.  If you install in a custom folder you can go to Settings and tell CCS where to look (use products for SysConfig).

To do it within CCS go to View -> Resource Explorer

When that opens go to the top right and click the 3 horizontal lines (hamburger menu) and select package manager

Scroll down to SysConfig (will list the versions you have installed)

Scroll over to the right and click the arrow to install more versions:

For the compiler you can do the same.  It is called Arm code generations tools - compiler, for the older one that MSP432E uses

Regards,

John

Thank you for your help.  I'm getting closer, but still can't build any projects.  The SysConfig problem seems to be resolved.  

There's still something wrong with the compilers.  I can't build the tirtos files, and then because they are missing, my app will not build.

This is the tirtos build errors:

[0]**** Build of configuration Debug for project tirtos_builds_MSP_EXP432E401Y_release_ccs ****
[1]"C:\\ti\\ccs2020\\ccs\\utils\\bin\\gmake" -k -j 16 all -O 
 
[2]making ../src/sysbios/sysbios.aem4f ...
[3]gmake[1]: *** No rule to make target 'xdc/runtime/xdc_noinit.c', needed by 'BIOS.obj'.
[4]gmake[1]: *** No rule to make target 'xdc/runtime/Assert.c', needed by 'BIOS.obj'.
[5]gmake[1]: *** No rule to make target 'xdc/runtime/Core-mem.c', needed by 'BIOS.obj'.
[6]gmake[1]: *** No rule to make target 'xdc/runtime/Core-smem.c', needed by 'BIOS.obj'.
[7]gmake[1]: *** No rule to make target 'xdc/runtime/Core-label.c', needed by 'BIOS.obj'.
[8]gmake[1]: *** No rule to make target 'xdc/runtime/Core-params.c', needed by 'BIOS.obj'.
[9]gmake[1]: *** No rule to make target 'xdc/runtime/Diags.c', needed by 'BIOS.obj'.
[10]gmake[1]: *** No rule to make target 'xdc/runtime/Error.c', needed by 'BIOS.obj'.
[11]gmake[1]: *** No rule to make target 'xdc/runtime/Gate.c', needed by 'BIOS.obj'.
[12]gmake[1]: *** No rule to make target 'xdc/runtime/Log.c', needed by 'BIOS.obj'.
[13]gmake[1]: *** No rule to make target 'xdc/runtime/Memory.c', needed by 'BIOS.obj'.
[14]gmake[1]: *** No rule to make target 'xdc/runtime/Registry.c', needed by 'BIOS.obj'.
[15]gmake[1]: *** No rule to make target 'xdc/runtime/Startup.c', needed by 'BIOS.obj'.
[16]gmake[1]: *** No rule to make target 'xdc/runtime/System.c', needed by 'BIOS.obj'.
[17]gmake[1]: *** No rule to make target 'xdc/runtime/SysCallback.c', needed by 'BIOS.obj'.
[18]gmake[1]: *** No rule to make target 'xdc/runtime/Text.c', needed by 'BIOS.obj'.
[19]gmake[1]: Target 'all' not remade because of errors.
[20]gmake: *** [../src/makefile.libs:57: ../src/sysbios/sysbios.aem4f] Error 2
[21]gmake: Target 'all' not remade because of errors.
[22]**** Build Finished ****

Then every file in my app fails like this:

[148]Building file: "../ut_modbus_usb_slave.c"
[149]Invoking: Arm Compiler
[150]"C:/ti/ccs2020/ccs/tools/compiler/ti-cgt-armllvm_4.0.3.LTS/bin/tiarmclang.exe" -c -mfloat-abi=soft -mlittle-endian -O0 -I"C:/senix/code/cc/sensor_connector/Debug Gateway/syscfg" -gdwarf-3 -Werror=ti-pragmas -Werror=ti-macros -Werror=ti-intrinsics -fno-short-wchar -fcommon -MMD -MP -MF"ut_modbus_usb_slave.d_raw" -MT"ut_modbus_usb_slave.o" -I"C:/senix/code/cc/sensor_connector/Debug Gateway/syscfg" -std=gnu90 @"C:/senix/code/cc/tirtos_builds_MSP_EXP432E401Y_release_ccs/Debug/configPkg/compiler.opt"  -o"ut_modbus_usb_slave.o" "../ut_modbus_usb_slave.c"
[151]Building file: "../ut_time.c"
[152]Invoking: Arm Compiler
[153]"C:/ti/ccs2020/ccs/tools/compiler/ti-cgt-armllvm_4.0.3.LTS/bin/tiarmclang.exe" -c -mfloat-abi=soft -mlittle-endian -O0 -I"C:/senix/code/cc/sensor_connector/Debug Gateway/syscfg" -gdwarf-3 -Werror=ti-pragmas -Werror=ti-macros -Werror=ti-intrinsics -fno-short-wchar -fcommon -MMD -MP -MF"ut_time.d_raw" -MT"ut_time.o" -I"C:/senix/code/cc/sensor_connector/Debug Gateway/syscfg" -std=gnu90 @"C:/senix/code/cc/tirtos_builds_MSP_EXP432E401Y_release_ccs/Debug/configPkg/compiler.opt"  -o"ut_time.o" "../ut_time.c"
[154]tiarmclang: error: no such file or directory: '@C:/senix/code/cc/tirtos_builds_MSP_EXP432E401Y_release_ccs/Debug/configPkg/compiler.opt'
[155]gmake: *** [subdir_rules.mk:11: USBCDCD.o] Error 1
[156]tiarmclang: error: no such file or directory: '@C:/senix/code/cc/tirtos_builds_MSP_EXP432E401Y_release_ccs/Debug/configPkg/compiler.opt'
[157]gmake: *** [subdir_rules.mk:10: bincloudTask.o] Error 1
[158]tiarmclang: error: no such file or directory: '@C:/senix/code/cc/tirtos_builds_MSP_EXP432E401Y_release_ccs/Debug/configPkg/compiler.opt'
[159]gmake: *** [subdir_rules.mk:11: config.o] Error 1

I have similar problems when I try to build any example project.  I can't find much info about this new version of CCS, all the help on this topic refers to the older versions. Is there a guide of how to build an example project in CCS 20.2?

For the compiler it is using tiarmclang which would not have been tested with that old SDK.  You will want to use the older Arm compiler.  Something like the armcl 18.12.5 compiler in my previous screen capture.

For MSP432E you have a choice of operating systems.  There is a TI proprietary one called TI-RTOS, in this case a quite old one that uses an obsolete tool called xdctools as part of the build. That tool does not appear to be running correctly.  It also generates a build options file that is used later in the build whichis why the other C files are failing to compile.

The other RTOS option is FreeRTOS.  FreeRTOS is not dependent on xdctools but for this old SDK you do have to download FreeRTOS separately and then set an environment variable to point to where it is.  SDKs for newer devices have FreeRTOS bundled so you can just build out of the box.

Or you could run without an RTOS.

Are you using TI-RTOS in your old projects?  I am guessing yes.  I can loop in someone who can try to help with the xdc error.

I have many applications that I have built using the TI-RTOS and CCS 12.  I'm just trying to get them running in the new environment.  I can't even get examples to run correctly, so I don't think the environment is setup correctly.  I was able to get the XDC errors fixed by using a build of the RTOS that came from another project.  Now I am getting many unresolved file errors on files related to the SDK and RTOS.  I'm not sure why the paths are no longer part of the project.  I've added some, but I'm still getting errors.  

msp.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\devices\msp432e4\inc
1
#35: #error directive: "Failed to match a default include file"
[Ln 53, Col 1]
msp432.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\devices\msp432e4\inc
1
msp432e401y.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\devices\msp432e4\inc
1
#1965: cannot open source file "core_cm4.h"
[Ln 196, Col 1]
msp432e411y.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\devices\msp432e4\inc
1
#1965: cannot open source file "core_cm4.h"
[Ln 201, Col 1]
httpserver.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\net\http
1
#1965: cannot open source file "sys/socket.h"
[Ln 71, Col 1]
slnetsock.h
C:\ti\simplelink_msp432e4_sdk_4_20_00_12\source\ti\net
1

core_cm4.h is a CMSIS header file. The include paths are likely messed up.  By default there will be a number of include paths setup that leverage a variable that gets populated by the location of the SDK (based on where CCS discovers it).

For example one of those paths is:

${COM_TI_SIMPLELINK_MSP432E4_SDK_INSTALL_DIR}/source/third_party/CMSIS/Include

If you look at your include paths in the build options does if have a path like that.  And more importantly does it resolve to a location.  To the right of the path it should show what it resolves to.

IF all the ones that are using that variable are not resolving then CCS does not know where the SDK is installed on your PC.

The version the project is set to use should be here:

Does that show the name of the SDK as well as a version?