CC3235S: Unable to build the projects

Hello Jesse,

Thanks for the prompt response. I checked what you suggested, however, there is no other COM instance open it seems. Also, I checked another thing. I created a new project for CC3235 and selected XDS110 debugger in it and verified the connection. It was all okay over there. Post this verification, I again tried to build the program, however, no success. 

here is the message that I received from CCS while creating a new CCS project and checking/verifying  the connection.

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\admin\AppData\Local\TEXASI~1\CCS\

ccs1110\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.

This utility will load the adapter 'jioxds110.dll'.

The library build date was 'Dec 8 2021'.

The library build time was '11:16:32'.

The library package version is '9.6.0.00172'.

The library component version is '35.35.0.0'.

The controller does not use a programmable FPGA.

The controller has a version number of '5' (0x00000005).

The controller has an insertion length of '0' (0x00000000).

This utility will attempt to reset the controller.

This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.

The controller is the XDS110 with USB interface.

The link from controller to target is direct (without cable).

The software is configured for XDS110 features.

The controller cannot monitor the value on the EMU[0] pin.

The controller cannot monitor the value on the EMU[1] pin.

The controller cannot control the timing on output pins.

The controller cannot control the timing on input pins.

The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End]

Hi H.C.,

I'll need some time to investigate the most recent information you shared.

Can you confirm you followed the steps in the Quick Start Guide for SimpleLink CC32xx SDK to install CCS and the CC32xx SDK properly?

Best regards,

Jesse

Hello Jesse,

following are the steps that I carried out:

1. CCS11 => standard installation. went for complete installation instead of custom installtion.

2. Downloaded SDK5.30. Unzipped the compressed file and kept the unzipped folder into C/ti folder.

3. Verified in CCS that SDK is available. See the image below.

Please let me know if I have missed something here.

Hi H. C.,

What changes have you made so far?

Trivedi said:

gmake: D:/Communication: No such file or directory

gmake: *** No rule to make target 'D:/Communication'. Stop.

• When I build tirtos_builds_cc32xx_release_ccs, I don't see anything regarding D:/Communication in the console.

Trivedi said:

Error: SLImageCreator.exe: could not open port 'COM14': WindowsError(5, 'Access is denied.')

• I've only seen this error when the COM port is open elsewhere. This could be TeraTerm, PuTTy, UniFlash, serial terminal within CCS, etc.

Your CCS properties look ok, except I don't have the "//10.61....." folder in my product discovery path. Perhaps this is causing issues?

Best regards,

Jesse

Hello Jesse,

I've tried following:

1. \\10.61.122.153.. folder was not causing any issue. I'd created a folder in the local system just to check whether there is any issue with the folder location or not. However, the same error still persists even though the workspace and project are on local system now.

2. I've updated to SDK 6.10, however, the issue still persists.

Regards,

H C Trivedi

Hi H. C.,

I haven't been able to recreate this issue--importing and building the example projects continues to work for me.

• Are you using the installer to install the SDK? (https://www.ti.com/tool/download/SIMPLELINK-CC32XX-SDK)
• You could try changing the build configuration of the project from "MCU + Image" to "debug" and see if the build is successful
  • Right click on the project (out of box or gpio interrupt) -> Build Configurations -> Set active -> Debug
• Are you using a launchpad or a custom board?

Best regards,

Jesse

Hello Jesse,

Are you using the installer to install the SDK? (https://www.ti.com/tool/download/SIMPLELINK-CC32XX-SDK)

• yes, I've recently downloaded SDK 6.10 from TI website and ran the executable to install the SDK.

You could try changing the build configuration of the project from "MCU + Image" to "debug" and see if the build is successful.

• I tried this thing post your recommendations. However, getting the same errors.  They are as follows:

Configuration failed!
gmake: *** [all] Error 2
gmake: *** No rule to make target 'D:/Communication'.  Stop.
gmake[1]: *** [build-121333681] Error 2
gmake[1]: Target 'configPkg/linker.cmd' not remade because of errors.
gmake[2]: *** [build-121333681-inproc] Error 1
xdc.cfg.SourceDir: "C:/ti/ccs1110/xdctools_3_62_01_16_core/packages/xdc/cfg/SourceDir.xs", line 211: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:
xdctools_3_62_01_16_core\gmake.exe: *** [package/cfg/release_pem4.xdl] Deleting file 'package/cfg/release_pem4.c'
xdctools_3_62_01_16_core\gmake.exe: *** [package/cfg/release_pem4.xdl] Deleting file 'package/cfg/release_pem4.h'
xdctools_3_62_01_16_core\gmake.exe: *** [package.mak:202: package/cfg/release_pem4.xdl] Error 1
xdctools_3_62_01_16_core\gmake.exe: *** Deleting file 'package/cfg/release_pem4.xdl'
Invalid project path: Include path not found (C:\ti\simplelink_cc32xx_sdk_6_10_00_05\.;C::\ti\ccs1110\xdctools_3_62_01_16_core\packages).
XDCpath repository 'C:/ti/simplelink_cc32xx_sdk_6_10_00_05/.;C:/ti/ccs1110/xdctools_3_62_01_16_core/packages' cannot be found! Visit project's 'Properties > General > Products' tab to adjust the XDCpath.

**** Build of configuration Debug for project tirtos_builds_cc32xx_release_ccs ****

"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 10 all -O 
 
making ../src/sysbios/sysbios.aem4 ...
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
asmem4 C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages/ti/sysbios/family/arm/m3/Hwi_asm_switch.sv7M ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
asmem4 C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages/ti/sysbios/family/arm/m3/IntrinsicsSupport_asm.sv7M ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
asmem4 C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages/ti/sysbios/family/arm/m3/TaskSupport_asm.sv7M ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
asmem4 C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages/ti/sysbios/family/arm/m3/Hwi_asm.sv7M ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
clem4 C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages/ti/sysbios/BIOS.c ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
gmake[1]: Entering directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
arem4 BIOS.obj m3_Hwi_asm.obj m3_Hwi_asm_switch.obj m3_IntrinsicsSupport_asm.obj m3_TaskSupport_asm.obj ...
gmake[1]: Leaving directory 'D:/Communication Systems/Harsh/Wireless Communication/test2/tirtos_builds_cc32xx_release_ccs/src/sysbios'
Building file: "../release.cfg"
Invoking: XDCtools
"C:/ti/ccs1110/xdctools_3_62_01_16_core/xs" --xdcpath="C:/ti/simplelink_cc32xx_sdk_6_10_00_05/.;C:/ti/ccs1110/xdctools_3_62_01_16_core/packages;C:/ti/simplelink_cc32xx_sdk_6_10_00_05/source;C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos/packages;C:/ti/simplelink_cc32xx_sdk_6_10_00_05/kernel/tirtos7/packages;C:/ti/simplelink_cc32xx_sdk_6_10_00_05;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.simplelink:CC32XX -r release -c "C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-arm_20.2.5.LTS" "../release.cfg"
configuring release.xem4 from package/cfg/release_pem4.cfg ...
generating custom ti.sysbios library makefile ... 
Starting build of library sources ...
Build of libraries failed.
subdir_rules.mk:12: recipe for target 'build-121333681-inproc' failed
gmake: D:/Communication: No such file or directory
gmake: *** No rule to make target 'D:/Communication'.  Stop.
error: xdc.cfg.SourceDir: "C:/ti/ccs1110/xdctools_3_62_01_16_core/packages/xdc/cfg/SourceDir.xs", line 211: xdc.cfg.SourceDir : Build of generated source libraries failed: exit status = 2:
 
js: "C:/ti/ccs1110/xdctools_3_62_01_16_core/packages/xdc/cfg/Main.xs", line 160: Error: Configuration failed!
xdctools_3_62_01_16_core\gmake.exe: *** [package.mak:202: package/cfg/release_pem4.xdl] Error 1
xdctools_3_62_01_16_core\gmake.exe: *** Deleting file 'package/cfg/release_pem4.xdl'
xdctools_3_62_01_16_core\gmake.exe: *** [package/cfg/release_pem4.xdl] Deleting file 'package/cfg/release_pem4.h'
xdctools_3_62_01_16_core\gmake.exe: *** [package/cfg/release_pem4.xdl] Deleting file 'package/cfg/release_pem4.c'
js: "C:/ti/ccs1110/xdctools_3_62_01_16_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake[2]: *** [build-121333681-inproc] Error 1
subdir_rules.mk:9: recipe for target 'build-121333681' failed
gmake[1]: *** [build-121333681] Error 2
gmake[1]: Target 'configPkg/linker.cmd' not remade because of errors.
makefile:127: recipe for target 'all' failed
gmake: *** [all] Error 2

**** Build Finished ****

**** Clean-only build of configuration Debug for project portable_CC3235S_LAUNCHXL_tirtos_ccs ****

"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 10 clean -O 
 
DEL /F  "portable_CC3235S_LAUNCHXL_tirtos_ccs.bin"  "syscfg\error.h" "syscfg\error.h"  "portable_CC3235S_LAUNCHXL_tirtos_ccs.hex"  "portable_CC3235S_LAUNCHXL_tirtos_ccs.out" 
DEL /F "console.obj" "main_tirtos.obj" "temperature.obj" 
DEL /F "console.d" "main_tirtos.d" "temperature.d" 
RMDIR /S/Q  "syscfg\" "syscfg\" 
Could Not Find D:\Communication Systems\Harsh\Wireless Communication\test2\portable_CC3235S_LAUNCHXL_tirtos_ccs\Debug\console.obj
Could Not Find D:\Communication Systems\Harsh\Wireless Communication\test2\portable_CC3235S_LAUNCHXL_tirtos_ccs\Debug\console.d
Finished clean
 

**** Build Finished ****
Buildfile generation error occurred..
Cannot build project. Referenced RTSC Configuration project 'tirtos_builds_cc32xx_release_ccs' contains build-errors.
Build stopped..

Are you using a launchpad or a custom board?

• I'm using launchpad (LaunchXL-CC3235S)

Regards,

Trivedi

Hello Jesse,

one more update on this. I carried out following steps and it seems to be working on my end:

1. created a new project.
2. selected CC3235S as a device and identified the connection as XDS110 USB Debug Probe.
3. from the available project templates, I selected "Hello World" example.
4. from the project properties, increased the heap size to 0x800 just to make sure printf() function works.
5. built the project and flashed it into the Launch XL board using Debug Perspective.
6. all went successfully and got the Hello World Message on my console. 
7. Does this help you by any means in eliminating some possibilities of errors?

Along with the same, I checked few other things as well:

upon checking Project -> RTSC Configuration, I got the following message. By any chance is this the once causing the issues? Cause in the error message, I could see errors related to XDC Tools. Please find the snapshot below.

Regards,

Trivedi

Hi Trivedi,

Check out Jan's suggestion of "I think you should remove white-space from your workspace path "D:/Communication Systems/Harsh/Wireless Communication/test2" and see if that helps.

I don't believe it has to do with the Project -> RTSC Configuration. I see the same snapshot on my end. 

Best regards,

Jesse