We're seeing some erratic operation in how CCS updates the Message Log
window.
Normally we'll get messages are they occur. Sometimes however, we'll
see none, but all will be displayed when we terminate program execution.
I've tried putting in TSK_sleep statements etc, but they don't seem to
help.
Any Ideas?
Thanks
Mark
Message Window Updates
Started by ●August 23, 2005
Reply by ●August 24, 20052005-08-24
This is out of memory, so it could be wrong:
If you right click on the log window i think you get an option akin to
"scroll to the end of the message buffer auto". Enable that option and I
think you may get better updates of the message log.
Even so, it is worthwile to understand that these messages are sent from
the target to host during "idle cycles of CPU" and NOT "as and when" as you
might be used to expect. Also the formatting of these messages are done at
the host and not in the target.All this indicates that a fair amount of
delay (and even doscontinuity) is plausible especially when the load on the
CPU is very high (i.e RTDX cant find CPU idle cycles)
Hope this helps some.
--Bhooshan
On 8/23/05, Bell Mark (ST-VS/ENG6) <mark.bell@mark...> wrote:
>
> We're seeing some erratic operation in how CCS updates the Message Log
> window.
>
> Normally we'll get messages are they occur. Sometimes however, we'll see
> none, but all will be displayed when we terminate program execution.
>
> I've tried putting in TSK_sleep statements etc, but they don't seem to
> help.
>
> Any Ideas?
>
> Thanks
>
> Mark
If you right click on the log window i think you get an option akin to
"scroll to the end of the message buffer auto". Enable that option and I
think you may get better updates of the message log.
Even so, it is worthwile to understand that these messages are sent from
the target to host during "idle cycles of CPU" and NOT "as and when" as you
might be used to expect. Also the formatting of these messages are done at
the host and not in the target.All this indicates that a fair amount of
delay (and even doscontinuity) is plausible especially when the load on the
CPU is very high (i.e RTDX cant find CPU idle cycles)
Hope this helps some.
--Bhooshan
On 8/23/05, Bell Mark (ST-VS/ENG6) <mark.bell@mark...> wrote:
>
> We're seeing some erratic operation in how CCS updates the Message Log
> window.
>
> Normally we'll get messages are they occur. Sometimes however, we'll see
> none, but all will be displayed when we terminate program execution.
>
> I've tried putting in TSK_sleep statements etc, but they don't seem to
> help.
>
> Any Ideas?
>
> Thanks
>
> Mark
