• Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 2163 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.

NO 'Run' options are eabled in CCS 6 debugger (resume, suspend, terminate, step-into .... etcetera)

robert schaefer
Expert 2050 points

HI,

 I am using CCS 6_1_3 on a mac pro, with a 432 launchpad and see no resume button, though I do see a terminate button.

 Basically, the project worked a few months back, I put down this project to go work on other things while waiting for a board with the 432 TI chip to be built, then when I came back to verify my baseline before continuing, I got the no resume button problem.

 I tried the workaround identified in the related posting, i.e. deleting the configuration and restarting, but it didn't help.

 I also tried the 432 on smaller project (supplied w/CCS) on the mac and can get the smaller project to run. 

 I also have a Windows 7 laptop CCS version 6_2_0 and see the resume button and can run the project. 

 Is this a mac only problem?

thanks,

bob s.

  • TI__Guru**** 173310 points

    Bob,

    Does this behavior happen only with a single project? You mentioned it is not seen with a smaller example project so I'm curious if you've tried running a few different projects and only observe the issue for your one project?

    Could you please attach a screenshot of the CCS Debug perspective when these buttons are missing?

  • in reply to AartiG
    Expert 2050 points

    The only difference that I can tell between a working small project supplied w/CCS and my project is my project is relatively large - 32752 bytes.

    I've successfully loaded (and got debug buttons for) 432 projects: wdt_service_the dog, wdt_interval_mode, and systick_interrupt_gpio_blink.

  • in reply to robert schaefer
    TI__Guru**** 173310 points

    Sorry about the delayed reply. 

    Thank you for attaching the screenshot to your previous post but I was hoping to see the "Debug" view that shows the state of the device (whether running or suspended). If the device is already running, then only the Suspend and Terminate options will be available for use, and Resume will be grayed out. As for why the device would come up running instead of being halted at main(), a number of different reasons could contribute to this, including code or system runtime issues. 

    You had mentioned earlier that you could run the project on a Windows 7 laptop with CCS version 6.2.0. Was that this same project? Could you try installing CCS 6.2 on the Mac to check if that works?

  • in reply to AartiG
    Expert 2050 points

    Hi,

      Yes, it was the same project. My mac'c CCS ver  6.1.3 behaves the same way as Linux, it loads into a bad state.

       The one difference I can tell between a project that will load normally, i.e. one that stops at main and one that won't,

        is the size, this is a large project over 32K bytes - if I try to load a small sample project, one that is provided with the 432, it loads and halts in main.

  • in reply to robert schaefer
    TI__Guru**** 173310 points

    robert schaefer said:

    The one difference I can tell between a project that will load normally, i.e. one that stops at main and one that won't,

        is the size, this is a large project over 32K bytes

    I don't think the size of project, in itself, is deterministic of the issue. Is it possible that the watchdog is triggering and resetting the device? This could happen if there are large arrays/variables to be initialized at runtime. A related thread on that topic is here. However, if this were the issue I would expect the behavior to be the same on the Windows machine as well.

    If the issue is not watchdog related, here a couple of things you could try:

    - install CCS 6.2 on the Mac/Linux machines and try rebuilding/loading with that version to see if that helps
    - debug why the current version is not halting at main. You can do this by disabling the autorun to main, which will allow you to halt at the entry point (under menu Run --> Debug Configurations, select your configuration in the left pane, and  select the Target tab in the right pane. You should find it under Auto Run Options). Then you could step through the code to see where it might be getting stuck, however be warned that it may not be easy to debug C runtime initialization code and could be a tedious task.  

    If the above suggestions don't help solve the issue, let us know if you would be willing to share the project with us for us to take a look at.