I am working on Stellaris ARM Cortex-M3 form LuminaryMicro & i am new to ARM Cortex architechture.
I am using code Code Composer Studio Version: 4.2.3 as a IDE & Stellarisware which is given by LuminaryMicro.
while importing the Stellarisware folder in Code Composer Studio i am getting error & if i go proceed the project will not build & gives following error.
gmake: *** No rule to make target `C:/StellarisWare_firmware/boards/dk-lm3s9b96/blinky/blinky_ccs.cmd', needed by `blinky.out'.
gmake: *** No rule to make target `C:/StellarisWare_firmware/boards/dk-lm3s9b96/blinky/blinky.c', needed by `blinky.obj'.
gmake: *** No rule to make target `C:/StellarisWare_firmware/boards/dk-lm3s9b96/blinky/startup_ccs.c', needed by `startup_ccs.obj'.
I tried a lot,but i am not getting the exact solution.
I am attaching my error image,please kindly help me regarding this error.
The error image shows a macros.ini error. The macros.ini file defines the path to the SW_ROOT (stellarisware root). The image makes it appear you are attempting to bring in another project that has a different SW_ROOT definition.
I think the best place to start would be to find the quick start quide located on the project CD. Also here. I suspect that you may have missed a step along the way in this document which would result in this type of error. Start with a fresh workspace and follow these directions. Let us know what you find.
I am getting the same type of error and I am following the Quick Start as closely as possible. However, I see in the document it says if I install CCS from the DVD included with my LM3S9B96-EK the license should automatically be installed. This wasn't the case for me. I didn't have the document at the time and I was very confused which options to pick. It wasn't obvious what to do to ensure I had the full version of CCS to use with my EK. I had to log in to TI to have a license file emailed to me. I could really use a more definitive answer than "check the Quick Start" because the Quick Start has already failed me.
I was able to fix this by copying the *.cmd for my specific device in C:\Program Files (x86)\Texas Instruments\ccsv4\arm\include and renaming it safertos_demo_ccs.cmd which is <project name>_ccs.cmd. Although I should mention that safeRTOS is currently crashing so that may have not been an entirely correct solution. I hope this is helpful to someone else.
I could still use an answer to the other question I posed regarding the licensing.
CCS Installation from either the DVD or the TI website should recognize that you have one of our kits and unlock full features of CCS while connected to the kit.
safertos_demo_ccs.cmd should be included in the example folder in the StellarisWare installation. It is also usually imported into the CCS project when you originally import the project. If this file was missing from your project this may be part of the original problem.
Please explain "safeRTOS is currently crashing"? How does it crash? Is it in a fault handler? What code is executing?
Try using LMFlashProgrammer to install the binary from a clean and fresh StellarisWare installation. Does the binary (as we ship it) behave the same as your build?
It was going straight to the SafeRTOSErrorHook function as soon as I started running. The project (none of the projects in the C:\StellarisWare\boards\dk-lm3s9b96 directory for that matter) didn't include the safertos_demo_ccs.cmd file so I had to pull a generic one from C:\Program Files (x86)\Texas Instruments\ccsv4\arm\include but that one wasn't setting aside the first 0x20C bytes of RAM for the safeRTOS kernel. Once I changed the cmd file to set aside enough RAM everything started working as expected.
I'm not sure about the license yet. I had to get one from the TI website to get things to work. So far I haven't experienced any limitations but it didn't really appear to "know" I was using a dev kit. If it did, why would it ask me to select a licensing option?
First, good to hear you got things up and running.
The licensing question you got probably happened on install or first execution after install. The kit detection does not occur until you start a debug session.
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. 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 respect to these materials. 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.