• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 6154 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 - New Project won't let me debug

Rkensparc
Prodigy 130 points
Other Parts Discussed in Thread: MSP430F2619

I've got a project on the MSP430F2619 - it's running well.  We are in the testing phase of the project and I needed to create some custom firmware for one of the tests that will use the majority of the code already written.  I didn't want to mess with the original source files, so I copied them all to a new directory and created a new project in CCS for the test firmware.

When I click the Debug button to enter debug mode in CCS, it goes through the normal sequence of steps:

1- Build

2- Configuring the debugger

3- Erasing Memory

4- Loading Program

I don't get any errors, but in the Debug Pane instead of saying "Entry Point Reached" it says "Running.  The green "Resume" button is grayed out.  Terminate, Suspend and Reset buttons are all active, but seem to have no effect (Terminate will exit the debug session) - but the MSP430 is not running (at least not the code I just built and downloaded.  None of my periphals are responding (UART, SPI, Blinking LED etc).  I've placed breakpoints in the code and they never trip.

I'm sure it's something simple in the project configuration, but I haven't been able to find any differences in this new project, and the original, except the original runs and allows debugging and the new project does not.

Any thoughts or suggestions are appreciated.

  • 0
    Guru 20525 points

    Hi!

    Perhaps this is issue of incorrect Debug configurations for new project. Make sure that configurations for old & new project are similar.

    Regards,

    Igor

  • 0
    TI__Guru*** 130875 points

    Hi,

    I would try the following

    1 - make a back up copy of your files

    2- import, don't manually copy your project to a fresh workspace.  Project->import existing ccs/eclipse project

    Please keep us informed.
    Best Regards,
    Lisa 

  • 0
    Guru 92251 points

    Rkensparc said:
    I don't get any errors, but in the Debug Pane instead of saying "Entry Point Reached" it says "Running.  The green "Resume" button is grayed out.  Terminate, Suspend and Reset buttons are all active, but seem to have no effect (Terminate will exit the debug session) - but the MSP430 is not running (at least not the code I just built and downloaded.

    The problem may be that the WDT fires during C startup code. One reason why the problem may show in a new project is the "output format" selected under CCS Project Properties -> General -> Advanced Settings.

    A newly created project will select an output format of "eabi (ELF)" by default. The other option is "legacy COFF"

    "eabi (ELF)" causes the BSS segment to be zero-initialized, which depending upon the program may slow down the C startup code sufficiently so that the watchdog fires, such that the C main entry point is never reached.

    Some possible options suggestions on how to allow the new project to initialize:

    a) If the new project has an output format of "eabi (ELF)", try changing to "legacy COFF".

    b) Try adding a _system_pre_init function to disable the watchdog during the C startup code, as per WDT fires during C startup code

     Are there any linker warnings from the new project?

     Did the original project contain a customized linker command file?

  • 0 in reply to Lisa TI
    Prodigy 130 points

    Lisa -

    I'll try that next time - I didn't this because last year I tried to do something with a new project(I don't remember for sure, but was thought it might have been the import) and CCS created a sub directory, in which it created another sub directory, in which another sub directory was created....  It did this until the windows allowable file name size was maxed out.  I couldn't access or delete any of the sub directories using windows. I  finally found an app someone had written that would delete the directory structure.

    Like I stated, I don't remember if it was the import function, but I didn't want to risk running into the same problem, so I was hesitant to try the Import and have the same issue.  I thought coping my original files to a new directory, and creating a new project would be easiest.

    Chester Gillon nailed it.  I changed the output to COFF and it fixed my problem

    Thanks for the suggestion.

  • 0 in reply to Chester Gillon
    Prodigy 130 points

    Chester - THANKS!

    That fixed it.  I assumed it was something simple in the properties, setup or configuration.  I just wasn't have any luck finding it.

    I switched to "legacy COFF" and I can now debug to my hearts content.

  • 0 in reply to Rkensparc
    TI__Guru*** 130875 points

    Ok, thanks for the udpate and glad all is well.  

    All the best with development.  My thanks as well for the help Chester.

    Best Regards,
    Lisa