Forums

Daniel,

I would recommend making sure that your version of CCS is up-to-date.  I remember having this issue during some earlier release (if I remember correctly, the issue is the real-time mode is getting stuck being on). The latest version of CCS4 is 4.2.5

You can usually update CCS from within CCS.  (Help->Software Updates->Find and Install...)

---

If you desire, you can also just directly download the most recent version.  Both CCS4 and CCS5 are both currently supported (although new releases are only being planned around CCS5).  Both can be downloaded from the below link:
http://processors.wiki.ti.com/index.php/Download_CCS


Thank you,
Brett

Hi Brett,

Thanks for your input.

CCS version I was using was 4.2.1. I  uninstalled it and intalled CCS from the DVD I got with Experimenter Kit.

Now CSS version is 4.2.3.00004. I got new license and everyting seems to be working Ok.

I tried then to run Flashing LEDs example. First deleted old workspace files and created new workspace just following directions from "SystemFrameworkOverview" pdf file.

Rebuilt project with no errors. When launching the debugger I don´t get expected debugger window status. Nevertheless I try to get target running but get this error message:

Trouble Reading PC Register:
(Error -1142 @ 0x0)
Device blocked debug access because it is currently executing non-debuggable code. Choose 'Rude Retry' to disable polite mode and force the operation.
(Release 5.0.333.0)

If I choose Rude Retry, it seems that target starts running but variable Gui_LedPrd_ms value is 24382 and doesn¨t change in spite of selecting permanent refresh in Watch window.

Seems that the target is caught in an  odd status and I can´t get it out of it? May be CLA status?

Any hints will be very much appreciated.

Regards

Daniel

Hi again Brett,

New Findings: If I starrt debug session hitting debug button I get all the problems I mentioned.

If first  I "Launch TI Debugger", then "Connect Target", then "Load Program" and select FlashingLeds... RAM.out, program is loaded and everything goes smooth as expected.

I can change Gui_LedPrd_ms value and Led modifies blinking period, and I can stop the program and start it again.

With restart it goes to main line, etc.

Is any selected DEbug option misconfigured perhaps?

Thanks again for your input.

Daniel

Daniel,

FYI, v4.2.3 still isn't up-to-date, 4.2.5 is the most recent.  I would still recommend updating to the most recent and you should be able to further update CCS from within CCS.  (Help->Software Updates->Find and Install...).  However, I no longer think this is your issue directly.

Within CCS, go to Target->Debug...   Here you should be able to see your settings for a "Non-Project Debug Session" and your "Project Debug Session".  Based on what you're saying the settings for Non-Project Debug are correct and the Project Debug is wrong.  See if you can change the project debug session to make both sessions' settings identical.  I think the inconsistency would be under "Project Debug Session->Target->Generic Debugger Options->Realtime Options"

Let me know if this still doesn't fix things.  If it doesn't I think I'll need to pass you onto the CCS guys.  (their first recommendation will be to update CCS though :))


Thank you,
Brett

Brett,

Thanks for your answer.

Following your input I updated CCS to version 4.2.5. But as you aniticipated, problem was still there.

I checked realtime option for both Non-Debug and Project Debug Session, without any success.

Then I checked other configuration differences between Non- Debug and Project Debug Session.

I found that for Project Debug Session, under Common, Shared file option was selected with a Flashingled....out file selected in the corresponding window.

As in NonDebug Session, Local File option was selected, I changed Porject Debug Session configuration to Local File also.

This seems to get things working OK. But I don´t really understand the difference.

Can you please explain briefly what  changes with Local File/ Shared File selection?

Thanks for your support

Daniel

Daniel,

I'm not really sure.  CCS is not my forte, but I'm usually able to get things going. 

My guess is that somehow the project's CCS workspace got corrupted in your earliest port to the older CCS.  I have a suspicion that if you created a new workspace that things would work first pass from CCS 4.2.5.

I'll move this post to the CCS forum to see if they have any input.


Thank you,
Brett