Debug Session hangs

Hi,

When you installed CCS v5.5, was is a fresh installation in a different directory?

Regards,

Gautam

Hallo Gautam,

thank you for your fast response,

The problem occurred without any changes in the source code of my project, when I'm working with CSS5.3. My program contains a "for-loop-for ever" (for(;;);) on which I set a braekpoint. It works all the time, but suddenly without any changes in the source this strange behavior pops up.

At that point I startet an update via the link in the help-menu of CCS.

CSS is installed on Windows XP.

Regards,

Ludger

Hi Ludger,

Can you go for an offline CCS v5.5 installation and revert whether this issue prevails or not? Also, install the setup in a different directory.

Regards,

Gautam

Hi Gautam,

a complete new installation, offline and in a different directory, is quite a good idea. Although, I'm in a little time pressure, I would like to understand this behavior. That's why I tell some more details of my observations in the last hour:

At first I've to mention that the data-array for plotting in the "Single Graph Window" is quite huge (1k words of 32Bit floating point).

Earlier I wrote that there is an update Problem in that window (i.e. no trace is displayed). Only after some attempts the window show the correct result.

The workflow is as follows:

1.)After the breakpoint hit a Restart(Ctrl+shift+r)  followed by a reload set the Program back to the main-entry point. Now I cancel the activ not working Single Graph window and create a new one. If this window opens in the "Process-Window" (accessible via a new tab) the prediction that it will not work becomes true. If this window opens in the "Problems-Window", most of the time it works. I don't know, how I can contol this behavior.

2.)There is a "window counter" displayed in the tab. This counter counts up no matter wether I close the old one or not. If I close the old window or restart CCS this counter is remembered by Eclipse.

3.)Sometimes there is a little progress bar in the lower right corner of Eclipse. If it is there and runs, then it seems that there is some work on the old, just closed Single Graph windows (looks like short flashing of lying underneath but closed windows ).

Maybe this background activity let the Debug-View crash (no response), when the session tries to close concurrently.

Is there any idea preventing such background activities? If I find out some more information, I will post it.

Regards,

Ludger

Hi Ludger,

I would like you to atleast check the behavior of CCS with other similar example codes. Also, you didn't mention what board you're using, kit or a custom board?

Regards,

Gautam

Hi Gautam,

for a few days I've to work on another project, then I will come back zo this problem. You are right, I didn't mention the hardware we are working with. It is a ControlCard TMS320F28335 for prototyping a radar application. May be later we will rewrite the code for a fixed-point TMS320F280xx.

Regards,

Ludger

Hi Ludger,

So you  mean to say you're facing this issue with all the codes? Can you try working on a new workspace? Just create a new one and add the project and check.

Regards,

Gautam