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.

Missing driverlib-cm4f.lib



I am just starting to use my LM4F120 Launchpad and trying to run Lab 2. I have CCS  Version: 5.3.0.00090

First I found that I needed to add #include "inc/hw_types.h" to eliminate the tBoolean error that is generated without the hw_types.h. Now it seems that I need StellarisWare v9453 to eliminate the next error:

error #10008-D: cannot find file
   "C:/StellarisWare/boards/MyLaunchPadBoard/Lab2/ccs/../../../../driverlib/ccs

>> Compilation failure
   -cm4f/Debug/driverlib-cm4f.lib"

but I can only find a download for StellarisWare v10636 that does not support the M4.

Where can I download StellarisWare v9453?

  • Hello David,

    Unfortunately, the website does not currently provide links to the older software packages. The transition to the Tiva branding is still ongoing and that will include a refresh of the Launchpad Lab projects to use the TivaWare software libraries. There is also an effort to get the StellarisWare v9453 re-posted for the current Lab projects as well.

    As neither of those efforts are yet complete, the best I can suggest is to download the TIRTOS package which will include a StellarisWare v9453 in it's products folder. Unfortunately, this is a rather large download and it will not include any board files. It should, however, allow you to build the Lab projects. You can pull the StellarisWare from the directory <base install location>\tirtos_1_01_00_25\products\StellarisWare_9453e. Or if you install it where CCS can find it (such as the default C:\TI\ location), CCS should pull all the products into the environment (the full install does have a rather large footprint, however: ~1.5GB). You can find that here: http://www.ti.com/tool/ti-rtos .

  • Stellaris Mitch,

    Thanks for the pointers. I was able to download the RTOS and put the -cm4f directories and files in the new StellarisWare directory. That allowed the program to compile and run as expected while maintaining the new installation of the rest of StellarisWare.

    Dave