• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 1532 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.

CCS/TMS570LS3137: Debug VectorCast binary in code composer studio

David Cothran
Intellectual 300 points
Part Number: TMS570LS3137


Tool/software: Code Composer Studio

Hi,

We have a project where we are utilizing vectorcast as for unit testing. We have developed code in CCS and are able to flash the project's binary to the TMS570. We are now integrating our project with VectorCast for the unit testing. VectorCast has generated a binary and it seems to be flashing successfully to the TMS570. My problem is that I am not sure how to get CCS to debug the project files generated by VectorCast. The flash settings state to halt at symbol main but I dont think CCS knows where the symbol is.

Any information would be appreciated.

Thanks,

David Cothran

  • 0
    TI__Mastermind 49120 points

    Hi David,

    I am afraid I do not have experience with VectorCast (VC), so can only provide generic pointers:

    • When you generate a binary using VC, can you confirm which compiler & linker does it use? I see on VC's page that you can set it up to use the same version of the tool-chain that your CCS install uses.
    • Which tool does VC use to flash the generated binary to the TMS570?

    Another possibility is that the program executes after being loaded to TMS570 but never makes it to "main". This could be the case if there was an exception that leads it to a "branch here forever", for example.

    Regards, Sunil

  • 0 in reply to Sunil Oak
    Intellectual 300 points

    Sunil,

    Thanks for the quick reply,

    • When you generate a binary using VC, can you confirm which compiler & linker does it use? I see on VC's page that you can set it up to use the same version of the tool-chain that your CCS install uses.
      • We are using the same ARM compiler and linker from CCS (ti-cgt-arm_18.1.2.LTS)
    • Which tool does VC use to flash the generated binary to the TMS570?
      • We are using the built-in CCS debug configuration functionality utilizing the XDS100v2 USB Debug Probe. Vectorcast generates a map and out file (along with all its own source files in a {project}/test/{VC Project Files} directory and I simply create a debug configuration in CCS to point to the out file.

    I think vectorcast just adds in all its testing harnesses to the code but i'm not completely sure. It uses the standard I/O stream to detect test completions. It still utilizes our same compiler/linker with all the same commands. It is also possible it never makes it to main though so that is worth looking into. My biggest concern at the moment is the ability for CCS to connect the debug symbols between the source and the binary. How do I tell CCS that the source for the binary is the /test/{VC} set of files since they differ from our own?

    Let me know if I don't make sense or anything needs clarifying.

    Thanks,

    David Cothran

  • 0 in reply to David Cothran
    Intellectual 300 points

    Figured out one part. Vectorcast was not including assembly files in its compilation and was missing its initial vectors such as c_int00 so it would immediately error not knowing where to go. Will resolve this and get back to you if I need more help regarding CCS debug symbols.

    Thanks,

    David Cothran

  • 0 in reply to David Cothran
    Intellectual 300 points

    Got it all working, thanks for you assistance. Once everything was compiled correctly and I adjusted the sys_link.cmd file for VectorCast it connected everything smooth and went straight to main. If anyone has future problems be sure to look at your map file.

    Thanks,

    David Cothran