• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 614 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.

can i use ccs v5.3.0 to debug the tms320f28335?

xiong ai
Prodigy 10 points
Other Parts Discussed in Thread: TMS320F28335

a few days ago ,my colleague downloaded the ccsv5.3.0 from the ti.com, however i can not find it on the ti.com now.

i find out that the v5.3.0 support the cortex-m4f in which i am interested in.

can i use the ccs v5.3.0 to debug the cortex-m4f,and also the tms320f28335 now ?

the flash api 2.1 for the tms320f28335 which is used in the ccsv4.0 can also used in the ccsv 5.3.0?

today i use the ccs5.2.1 to build  a program which was created under ccs4.2.4, and then use the emulator（seed 560v2）to download in the tms320f28335, a warningwarning"no source available for 0x3ff9ce" appears, what's the matter?

 

  • 0
    TI__Guru*** 130875 points

    HI Xiong,

    yes both of those targets will be/are supported in CCSv5.3.   Regarding the flash api,this has remained the same in CCSv5 so yes you will be on the same flash api version

    Regarding the "no source available" message ..

    How did you import the project from v4?  Do you see the same behaviour there?  What debug settings do you use?


    Best Regards,
    LIsa

  • 0 in reply to Lisa TI
    TI__Guru**** 162315 points

    Well for 5.3 it is not yet a beta release, there will be a beta in a couple of weeks.  You might want to wait until beta before using it.  I believe the image we have posted right now is for people who are trying out the GUI Composer tool.

    "no source available" can happen for a number of reasons.  In CCSv5.1/5.2 one reason is that there is an issue when only skeletal debug information is present.  That is the default for the Release build configuration.  You can workaround that by selecting -g (full debug information) and also select --optimize_with_debug   That gives you good debug info but still enables a lot of compiler optimizations.  That particular issue is fixed in CCSv5.3.

    On MSP430 I have also seen an issue with source correlation when using ELF debug output format.  That one is also fixed in 5.3.

    John