• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 448 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Sharing code with Stellaris and Tiva chips, debugging with TivaWare and StellarisWare

John Lee101781
Prodigy 130 points
Other Parts Discussed in Thread: CODECOMPOSER

I am porting an existing product from a Stellaris to a Tiva part, and when working in CodeComposer I can create a build configuration for both the TM4C and LM3S parts and they compile for the different hardware.  I can share the project with both the TivaWare or StellarisWare libraries included that I wish to use, then exclude them from the build of the respective build configurations.  The problem occurs when I want to step into the TivaWare utility when debugging on TM4C part.  Code Composer thinks that it should use the StellarisWare file rather than the TivaWare file.  The only way I have found for the debugger to resolve to the correct source file is to delete the source file links in the .project file, then teh correct source file is referenced during debugging.

  • 0
    TI__Guru**** 244440 points
    Hello John

    When debugging using Code Composer, you need to make sure that the device type selected in the Configuration file is a TM4C.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Prodigy 130 points
    Amit,

    Yes, in the LM3S build configuration, the LM3S part is selected and in the TM4C build configuration the TM4C part is selected. Both configurations produce binaries that load and run correctly on the respective targets, and both configurations build from StellarisWare and TivaWare for the respective configurations. The issue is when I use the debugger to step into a TivaWare file, the StellarisWare file is used. The debug pointer indicating code step location is out of regstration with the source file, since the StellarisWare file is pulled up in the debugger instead of the TivaWare File.
  • 0 in reply to John Lee101781
    TI__Guru**** 244440 points
    Hello John,

    This would happen when the file paths have been mapped in CCS. One way of working around the issue is to compile the driverlib and then use the local copy of the driverlib files. This will allow CCS to search the source directory locally to the path of the driverlib.

    Regards
    Amit