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.

Issue when debugging with CCS v5.5 on Concerto microcontroller

Hi,


I got a new contract with a new customer on embedded development. They use a concerto F28M35H52C1 microcontroller and development was made by successive teams from different companies without any good documentation of either tools documentation and software architecture.

I got some feedback about development environnment etc.... So from that, I installed CCS v5.5 + TI-rtos, IPC etc... with same versions of previous developers. I imported the project and tried to launch a debug and got couple of issues I have already fixed.

From now, I can load application on both ARM and C28 cores and run them. But, I still have an issue setting breakpoints. Breakpoints keep grey and program never stops. Of course, I tried to reload symbols without any help (CCS doesn't even show that symbols are loaded).

I noticed I have a warning message in the debug window below te ARM core description: xxxxx does not contain frame information

Do you have any idea from what this issue is coming? Is there any issue with the generation of symbols in the *.out file or is it something with the debug configuration?


Thanks

Chris

  • Hi Chris,

    Christophe Dohen said:

    From now, I can load application on both ARM and C28 cores and run them. But, I still have an issue setting breakpoints. Breakpoints keep grey and program never stops. Of course, I tried to reload symbols without any help (CCS doesn't even show that symbols are loaded).

    I noticed I have a warning message in the debug window below te ARM core description: xxxxx does not contain frame information

    It sounds like the program you loaded is optimized and/or debug symbolic information not (or minimally) generated when building the application. This would limit your ability for source line debug like setting breakpoints on any source line in source files. Check the project build options and look at the "Optimization" and "Debug Options" settings under the compiler options.

    Thanks

    ki

  • Hi ki,

    I checked options of CCS and I have:
    - debugging model: Full symbolic debug
    - Optimization level: Off

    I think these options are fine but maybe you can confirm. I also want to make sure I do the right process when starting the debug mode.
    Below is the process I follow to start:
    1. I build C28 application in flash mode and ARM application in debug mode.
    2. I launch the selected configuration
    3. I connect ARM and DSP cores by right clicking on them from the debug window
    4. I load the program *.out file for ARM
    5. I load the symbol *.out file for ARM
    6. I load the program *.out file for C28
    7. I run ARM core
    8. I run C28 core
    At this stage, the application runs but I can not set any breakpoints and I have the warning message described in the previous post.

    Thanks
  • The build options look fine. Just to confirm, did you rebuild the program from the project you are working with? Or are you loading an existing out file?
  • I rebluit the project. I can try to load *.out file from previous developers, just to see what's going on. Thanks
  • Actually, working with the rebuilt program is the best since you know the program was build with the compiler options in the project you are looking at

    Are you able to set breakpoints if you halt the target first?
  • I loaded the *.out from previous developers and it doesn't show warnings like the one I have with my own built program. I have something wrong in my configuration but can't figure it out for the moment. Can be an issue with the gel file or something like that?
    I remember some devolepment I did on Picolo in 2009/2010 with CCS3.3. I had a wrong gel file and had to download a new one.
    For the new project, I am using the default gel file. Is it fine with that file?
  • For custom boards, there is a custom gel file created. It is possible you need the custom gel file created for your particular target. In some cases, you don't need a gel file at all (since the application itself will do the necessary target initialization).

    Also make sure you are building the correct build configuration. A project can have multiple build configurations. Make sure you are using the correct one.