Quantcast
Channel: ARM Connected Community : All Content - All Communities
Viewing all articles
Browse latest Browse all 6005

ERROR(TAD9-NAL52): Why is DS-5 unable to control my target when debugging the Linux kernel via JTAG?

$
0
0

What does the following error message mean?

 

“ERROR(TAD9-NAL52): Unable to stop device "x" - Cannot attain state requested”

 

Answer:

 

DS-5 debugger may lose control of the target during Linux kernel debug with error messages as follows:


     Target Message: Could not determine target state interrupt
     ERROR(TAD9-NAL52):
     ! Unable to stop device 3
     ! Cannot attain state requested.

The behavior can be triggered by kernel power management operations. In some targets setting CONFIG_CPU_IDLE=y in the kernel configuration can cause the on chip debug logic to be powered down. This breaks the communication between the debugger and the target, resulting in the debugger losing control or being unable to connect.

Rebuild the kernel with CONFIG_CPU_IDLE=n, reload the new kernel image and restart the debug session.


Viewing all articles
Browse latest Browse all 6005

Trending Articles