• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Subscribers 56 subscribers
  • Views 6921 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Cannot debug import Energia sketch to CCS v6

Shujen Chen
Intellectual 605 points
Other Parts Discussed in Thread: ENERGIA, EK-TM4C123GXL, OMAP-L138

I imported an Energia sketch to CCS v6. The project built and debug worked fine. When I took the suggestion to update the software (I believe it was ARM compiler update), the only buttons available were the two green ones for instruction stepping. Every other buttons were gray out.

I uninstalled CCS v6 and reinstalled it. The exact same thing happened.

I uninstalled CCS v6 and reinstalled it again. This time I did not take the update. After I exited CCS and relaunched CCS, the debugger did not run. The program was loaded in the target and if I reset the board, the program ran well. The debugger had the error message of 

main() at main.cpp:67 0x00000A96 (an error occurred: Memory map prevented reading 0x20007FFC)

All the debug buttons were gray out.

I uninstalled CCS v6 and reinstalled it again. And it worked for the first time only then back to the same problem.

Energia 0101E0014

CCS  Version: 6.1.0.00104 

EK-TM4C123GXL

Windows 8.1 64-bit

  • 0
    TI__Guru**** 173310 points
    Which example sketch are you importing and building in CCS? And which compiler version did you update to when you started seeing the problems? If you provide this information, I can see if I am able to reproduce the issues here.
  • 0 in reply to AartiG
    Intellectual 605 points
    The program that failed was my own program but I just went back and imported several example programs from Energia. They all exhibited the same symptom that the project was built without errors, downloaded to the target but the debugger did not launch. When The debug session was terminated and removed (by right clicking on the debug session in debug window) the program started running on the target properly.

    The update was ARM Compiler Tools 5.2.3, which I suspect may not have anything to do with this problem. I have not taken any update for the last to reload and I am still having problems.

    Furthermore, I imported a simple sample blinky project (from Tivaware) from my CCS v5 it could not launch the debugger. I started a new project and copy the blinky main.c over, it did not launch debugger ether. The error message is different though.
  • 0 in reply to Shujen Chen
    Intellectual 605 points
    I could not find out how to attach a screenshot here. The error messages for CCS project (not Energia import) are:
    main() at blinky.c:51 0x0000045C
    _c_int00() at boot.asm:222 0x000004EE (_c_int00 does not contain frame information)
  • 0 in reply to Shujen Chen
    Intellectual 605 points
    Tried it on a Windows 7 PC and got the same results:
    Worked great the first try after installing CCS 6. Exited CCS and relaunched CCS, it would not get into debugger anymore.
  • 0 in reply to Shujen Chen
    TI__Guru**** 173310 points

    Shujen Chen said:
    Worked great the first try after installing CCS 6. Exited CCS and relaunched CCS, it would not get into debugger anymore.

    Could you attach a screenshot of your entire debug view? The whole CCS Debug perspective will be helpful.

    Do you see the same issue if you open a new clean workspace and import, build and debug the blinky example from TivaWare?

  • 0 in reply to AartiG
    Intellectual 605 points
    Aarti, I may have found the issue while trying to reproduce the problem and taking screenshot.

    It appeared when I had problem building Energia sketch for MSP432, I relocated the Energia-15 folder. For unknown reason, the Energia folder location in CCS6 was redirected to my old Energia-14 folder. When an Energia Sketch with SPI was imported, the SPI source was fetched from Energia-14 library and all the projects failed to launch debugger.

    I modified the Energia folder location in CCS6 preferences to point to Energia-15 folder and did a lot of cleaning in my workplace. Now the imported sketches and native CCS projects seem to launch debugger fine. I will continue working on it for few days to be sure.
  • 0 in reply to Shujen Chen
    TI__Guru**** 173310 points
    Thanks for the update. Glad to hear you were able to locate the source of the problems and resolve them. I will mark this thread as Answered, but feel free to post an update or start a new post if you hit other problems.
  • 0 in reply to AartiG
    Intellectual 605 points

    Unfortunately, the joy was short lived. It stopped working again. Everything seemed to work fine except all the debug buttons are grayed out.

  • 0 in reply to Shujen Chen
    Guru 15175 points
    this really is strange, in version 6.0 did not happen such thing, as I see there problems with the update 6.1!
  • 0 in reply to Shujen Chen
    Intellectual 605 points
    I started a new workspace and imported the blink sketch yesterday. The project built fine and the debugger ran.

    I restarted the computer and CCS today, the debugger would not launch on the same project. Even the imported CCS project from Tivaware does not debug.
  • 0 in reply to Shujen Chen
    TI__Guru**** 173310 points

    Shujen Chen said:
    I started a new workspace and imported the blink sketch yesterday. The project built fine and the debugger ran.

    I restarted the computer and CCS today, the debugger would not launch on the same project. Even the imported CCS project from Tivaware does not debug.

    I think I have finally been able to reproduce this issue. It seems dependent on the CCS Simple mode which is typically used when working with Energia.
    Here is the scenario that causes the same symptoms for me:

    1) Start a debug session for an imported Energia sketch by selecting the CCS Simple mode
    2) Debug buttons for Run etc are available during first run
    3) Terminate the debug session and close CCS while still in CCS Simple perspective
    4) Restart CCS
    5) Now when starting a debug session (whether it is for Energia sketch or CCS project) the debug buttons are grayed out

    Can you confirm if this is the same behavior you are seeing?

    This is definitely a bug and I will be filing a bug report. In the meantime, here are two workarounds I found:

    1st workaround:

    1) Before closing CCS, switch perspective to CCS Debug perspective each time, then close CCS
    2) Now when CCS is restarted, it starts back up in CCS Debug. You can then switch to CCS Simple and debug your project and things should work fine. Just remember to switch back to CCS Debug perspective before closing CCS

    To recover debugging capability from your current situation:

    1) Restart CCS, go to CCS Debug perspective, then menu Run->Debug Configurations, select the configuration corresponding to your Energia project in left pane and click the Delete icon to delete it. Click Close. 
    2) Close and restart CCS
    3) Now you should be able to go to CCS Simple perspective and debug your project and the debug buttons should be recovered. Again, just remember to switch to CCS Debug perspective before closing CCS so you do not hit the issue again.


    Let me know if the above steps help your situation.

  • 0 in reply to AartiG
    Intellectual 605 points
    Aarti,

    Thanks so much for the procedure to work around the problem. On the top of that, you even provided the way to recover.
  • 0 in reply to Shujen Chen
    TI__Guru**** 173310 points
    The bug tracking number for this issue is SDSCM00051770.
  • 0 in reply to AartiG
    Prodigy 90 points

    AartiG,

    Many thanks for this post. I just came across this now after two weeks of banging my head. I am using the OMAP-L138 DSK + XDS100v2 in a lab (20 of them) with ccs v6.1. Upon testing my programs prior to having the student use them, I noticed this strange behaviour (both under ccs v6.1.0 and ccsv 6.1.1). I had been using ccs v5 (and all others prior to that for the last 14 years) without a problem. When I bumped into it, I noticed that free-running would allow me to do my initial work, so for the first two weeks of the term I kept it that way and started looking into possible configuration/incompatibility errors that I might have made. 

    However, as soon as the students went beyond the 1st project, this "greying out" of the debug buttons (i.e., ccs refusing to work on debug mode) started to get annoying for the students. And yes, I had instructed them to use the "simple view" (which is great for the teaching environment and came with v6). I have held things at bay with the free-running, but that does not solve the problem. Now I bumped into your work around (and thanks again!).

    Still, as you can see, this problem is HUGE when it comes to teaching multiple classes a day with about 40 students each. To keep reminding a full class to switch back to debug before closing CCS is possible but not ideal. Right now, the clearing of the debug-launch is preventing a riot, but again, this is really a bug of ccsv6x.

    So the question is: Is there a permanent solution for this problem already?

    Again I thank you and look forward for your response.

    Perhaps this post should also be somewhere in the OMAP-L138, XDS100v2 or c6748 threads?

    Cheers,

    bkf@

  • 0 in reply to Bruno Korst
    TI__Guru**** 173310 points

    Bruno Korst said:
    So the question is: Is there a permanent solution for this problem already?

    Yes, this bug is fixed in CCS 6.1.1 which is available for download here: http://processors.wiki.ti.com/index.php/Download_CCS

  • 0 in reply to AartiG
    Prodigy 90 points

    Thank you for the reply; perhaps I should have been clearer in my post. 

    I've been running v6.1.1 for the last three days and the problem is there. I tried about 15 different projects, which work fine as free-run, but go into that debug grey-out mode suddently.

    The work around you suggested does the trick to reverse the problem, but the problem is still there. 

    Cheers,

    bkf@

  • 0 in reply to Bruno Korst
    TI__Guru**** 173310 points

    Bruno Korst said:
    I've been running v6.1.1 for the last three days and the problem is there.

    I'm surprised to hear that. Are you using the same workspace you did with the earlier version of CCS? If so, could you start up 6.1.1 in a new workspace, import your projects into the new workspace and check if the issue persists?

  • 0 in reply to AartiG
    Expert 1470 points
    Hello,

    I am running CCS 6.1.1.00022 and I can debug my project with the debug button, but there is no freerun button. I am t rying to solve this for past day, CCS cloud has a flash button, that will upload the code to the launchpad and start running. Desktop CCS does not have this at the moment.

    I tried manythings, such as configuring a view to include run configurations, etc, but those are for other things I assume.

    Right now, I am using debug, then detach debugger, and it is kind of time consuming during development.

    Best,
    C.
  • 0 in reply to Shujen Chen
    Prodigy 10 points
    One Year later :)

    CCS6.1.1 on Win7 64Bit, MSP-EXP430G2, Rev. 1.5 launchpad with G2553.
    Same problems with Energia sketches in perspective CCS Simple and CCS Edit. After all I also started a new Workspace and imported the Energia blink example and an older Energia sketch of my own. Both built without errors and debugging worked just fine.
    Then I restarted CCS and all worked fine. After that I switched to an older Workspace with the same result. I then switched back to my new Workspace, everything worked as it should.

    My solution was pretty simple: A new, empty workspace.
    Ernst