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.
Part Number: CCSTUDIO-TM4X
Tool/software: Code Composer Studio
Have been rebuilding our development environment; Just installed CCS v7.4 - so far so good.
Next, installed TivaWare_C_Series-188.8.131.52 from TI Resource Explorer. proceeds with no error. However, builds seem unable to recognize TivaWare as installed; it's simply Unknown:
Presumably as a result, the COM_TI_TM4C_LIBRARIES variable is not populated:
Goal is to build secure_iot demo for EK-TM4C129EXL as a test of environment.
What magic do I need?
OS Env: is macOS 10.12.6
LouEEEE!Next, installed TivaWare_C_Series-184.108.40.206 from TI Resource Explorer. proceeds with no error.
Did you actually download and install it directly from Resource Explorer, and did it install correctly? I ask because the TivaWare package is not available for Mac, and typically users copy the package over from Windows. One quick way to confirm if the TivaWare installation is good is to see if you can import and build example projects from TivaWare successfully.
Also, what is the error you are getting when building the secure_iot project?
Please click This Resolved My Issue if the reply answers your question.
Explore Code Composer Studio documentation and resources using online Resource ExplorerTrack a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to AartiG:
Indeed, installed directly from TI Rex... No errors, looked smooth. And, sure enough, the whole thing is there, in the filesystem, among all other TI packages installed.
I was surprised/heartened to see it offered directly there on TiRex, on macOS - thinking this was one of the mods to the new CCS. ( Yes, I had myself copied it from a Windows archive on previous installs of CCS. )
First, clean-only build:
**** Clean-only build of configuration Debug for project secure_iot ****
/Applications/ti/ccsv7/utils/bin/gmake -k clean
cleaning ../src/sysbios ...
../src/makefile.libs:60: recipe for target '.sysbios_clean' failed
gmake: C:/ti/xdctools_3_32_02_25_core/packages/../bin/rm: Command not found
gmake: *** [clean] Error 127
gmake: [.sysbios_clean] Error 2 (ignored)
rm -rf "secure_iot.bin" "configPkg/linker.cmd" "configPkg/compiler.opt" "secure_iot.out"
rm -rf "configPkg/"
rm -rf "EK_TM4C129EXL.obj" "UARTUtils.obj" "board_funcs.obj" "cloud_task.obj" "command_task.obj" "ntp_time.obj" "secure_iot.obj" "tictactoe.obj"
rm -rf "EK_TM4C129EXL.d" "UARTUtils.d" "board_funcs.d" "cloud_task.d" "command_task.d" "ntp_time.d" "secure_iot.d" "tictactoe.d"
**** Build Finished ****
One thing very interesting there is CCS looking for rm on a Windows path. My xdctools (several versions, by the way) all report their correct install locations in my /Users/<me>/ti directory.
Then, Debug build:
Buildfile generation error occurred..
Product 'tm4c' v220.127.116.11 is not currently installed and no compatible version is available. Please install this product or a compatible version.
Tks for your thoughts on this...
FWIW, I'd built the secure_iot demo some months ago, as part of my initial learning process on the TI ecosystem. This was intended to be a simple repeat experiment!
Next, I'm gonna drag TivaWare_C_Series-18.104.22.168 out of the filesystem manually, then back in, to see if CCS 'discovers' it. Think I've tried this already, but...
---- OK, Now this is interesting. Having done this, CCS reports 'Importing <Tiva...>' on next start - whereas it did not recognize it as installed after install from Resource Explorer. Hmm...
**** Build of configuration Debug for project secure_iot ****
/Applications/ti/ccsv7/utils/bin/gmake -k all
making ../src/sysbios/sysbios.aem4f ...
gmake: Entering directory '/Users/drlou/DEVELOPMENT/TI/workspace_v7/secure_iot/src/sysbios'
gmake: Leaving directory '/Users/drlou/DEVELOPMENT/TI/workspace_v7/secure_iot/src/sysbios'
../src/makefile.libs:56: recipe for target '../src/sysbios/sysbios.aem4f' failed
gmake: *** No rule to make target 'BIOS.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'knl/Clock.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'knl/Idle.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'hal/Cache.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'hal/CacheNull.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'heaps/HeapMem.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'gates/GateHwi.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'gates/GateMutex.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'family/arm/m3/Hwi.c', needed by 'BIOS.obj'.
gmake: *** No rule to make target 'family/arm/m3/TaskSupport.c', needed by 'BIOS.obj'.
gmake: Target 'all' not remade because of errors.
gmake: *** [../src/sysbios/sysbios.aem4f] Error 2
Building file: "../secure_iot.cfg"
"/Users/drlou/ti/xdctools_3_32_00_06_core/xs" --xdcpath= xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4F -p ti.platforms.tiva:TM4C129ENCPDT -r release -c "/Applications/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.6.LTS" --compileOptions "-mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path=\"/Applications/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.6.LTS/include\" --include_path=\"/products/TivaWare_C_Series-22.214.171.124b\" --include_path=\"/products/ndk_2_25_00_09/packages/ti/ndk/inc/bsd\" --include_path=\"/Users/drlou/ti/wolfssl-3.10.2\" --define=NET_NDK --define=ccs=\"ccs\" --define=PART_TM4C129ENCPDT --define=ccs --define=TIVAWARE --define=WOLFSSL_TIRTOS -g --c89 --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --abi=eabi " "../secure_iot.cfg"
subdir_rules.mk:59: recipe for target 'build-1846500401-inproc' failed
js: "/Users/drlou/ti/xdctools_3_32_00_06_core/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: Error: Can't find the platform package 'ti.platforms.tiva'. TI platforms are no longer shipped as part of XDCtools (/Users/drlou/ti/xdctools_3_32_00_06_core). Please ensure you are either using a pre-3.30 version of XDCtools or you have added a product that includes your platform support along the path ';/Users/drlou/ti/xdctools_3_32_00_06_core/packages'. Check that this path names a directory containing the necessary platform support and that the platform name is properly spelled.
gmake: *** [build-1846500401-inproc] Error 1
gmake: *** [build-1846500401] Error 2
subdir_rules.mk:56: recipe for target 'build-1846500401' failed
gmake: Target 'all' not remade because of errors.
**** Build Finished ****
Looks like this may now be down to adding library paths to preferences, and reverting to an older XDCTools. I was helped with these things months ago by 'Stellaris' Sai Reddy. Even that crazy semicolon error looks familiar. I'd better check my notes. Meanwhile....
What is the relationship between TivaWare-(presumably complete)-126.96.36.199 and the SW-EK-TM4C129EXL-188.8.131.52 package - which seems newer(?) and more specialized(?) for the EK-TM4C129EXL? Which should I prefer? How to differentiate the usage?
In reply to LouEEEE!:
Sounds like you making progress and are on the right track.
For the build errors, I agree that the TM4C device forum would be the better place to ask. They are more familiar with the secure_iot demo and should be able to provide assistance there.
LouEEEE!What is the relationship between TivaWare-(presumably complete)-184.108.40.206 and the SW-EK-TM4C129EXL-220.127.116.11 package - which seems newer(?) and more specialized(?) for the EK-TM4C129EXL? Which should I prefer?
All TivaWare releases are available either as a complete package or as packages for specific kits. http://www.ti.com/tool/sw-tm4cSW-EK-TM4C129EXL-18.104.22.168 is the latest version of the software for the EK-TM4C129EXL kit. There is also a complete software release of the same version. In general, we do recommend using the latest version.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.