[quote user="Akhilesh Raju"]
But could you just elaborate on how to carry out the changes suggested by you in the following points ? I am not so well versed with the advanced settings of CCS.
- SysCtlDelay() is part of TivaWare; which is compiled as an optimized library. From the looks of your screenshot, it is executing it; but without the debug artifacts. If you want to step through the SysCtlDelay(), you need to recompile driverlib.lib with debug symbols (and no optimization to make it easier to follow the flow of execution).
- The same is happening here. In CCS (at least), the reset vector is named as "_c_int00". In this case, the boot code for Tiva C parts also comes from an optimized SYS/BIOS library. To be able to step through this code you will want to use the graphical configuration to use "Custom Debug" SYS/BIOS libraries.
[/quote]
Akhilesh, before I can do that, I need to know more about your setup. Are you using TI-RTOS for your project or are you using a SYS/BIOS project and added TivaWare to it?
The process is essentially the same and in either case, just the location of the source files might differ. The idea is that you would import the CCS project that comes with TivaWare, build it with debug symbols and no optimization, and rebuild the driverlib library. Relink (or rebuild) your application the the rebuild library and you should be set.
If you are using TI-RTOS you should be able to find the TivaWare CCS project at C:\ti\tirtos_1_21_00_09\products\TivaWare_C_Series-2.0.1.11577a\driverlib\ccs. After importing the CCS project, edit the CCS project properties and change the ARM Compiler's "Optimization" level to 0 (-O0) and ensure that the Debugging model is set for "Full symbolic debug" in the "Advanced Debug Options". Rebuild the "driverlib" project and the rebuild your blinky project.
To have debuggable SYS/BIOS libraries see this wiki page.