GUI composer: Could not read,write execution state prevented access

Hi Praneeth,

What exact device are you using?

Thanks

ki

Hi,

I am using AM263x.
I used the hello world example of it in MCU+SDK.

My question is something similar to this
https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/344353/how-to-enable-halt-the-target-before-any-debugger-access-in-gui-composer-runtime
but this was in an older version of gui composer, so how to do it in the current version?

Thank you
Praneeth

Unfortunately that option in not availble in current (v2 and v3) versions. Which CPU of the AM263 is the program for?

Ok

Anyhow my question is not how to enable that Halt the target before any debugger access.

Still, my main question is how to remove those red cross beside widgets that say could not read execution state prevented access. And let the widgets connect to the target global variable.
Is there any alternative way to resolve this issue?

Thank you

Praneeth G said:

Still, my main question is how to remove those red cross beside widgets that say could not read execution state prevented access. And let the widgets connect to the target global variable.

This typically happens because the tool (GC) is unable to access memory while the target is running. I assume you are using an XDS JTAG connection. Some CPUs allow for real-time memory access, hence does not need the target halted to read memory. Hence I asked which CPU is getting blocked from accessing memory. ARM Cortex CPUs typically allow real-time memory access via the DAP.

Hi,

Sorry for late reply.
Ok. Yes what you told is right. Using DAP we can access real time memory.

But how to make the GC to access memory via DAP? So that the error goes away and the GUI widgets are able to read.

Thank you

Praneeth G said:

But how to make the GC to access memory via DAP?

It typically should. Which is why I was asking for which CPU the program is running on.

Hi,

I am using r5fss0-0 freertos.

Thank you