This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM64X: CCS 10.3.1 randomly loses breakpoint focus and must be restarted

Part Number: PROCESSOR-SDK-AM64X

Hello, 

in CCS 10.3.1 with the AM64 MCU+SDK running on the evm board it happens sometimes randomly that the breakpoint stepping loses focus resulting in a not responding processor.

This happens if you step and the the step doesn't progress but gets unmarked. The target still seems to be halted but if you press "resume" only the "terminate" button is available, the other two are greyed out. You can't reset the CPU or anything. Only solution is to kill the ccs process with the task manager, reset the evm board, restart CCS and then it's working again. We are using the XDS110 Debugger with the JTAG pin-header.

Sometimes it also happens that the focus gets lost, the CPU-load for ccs increases a lot and after like 20 seconds it resumes. But I'm not sure this is related to the other problem. 

How can I fix this?

Best regards

Felix Heil

  • Hello,

    This happens if you step and the the step doesn't progress but gets unmarked. The target still seems to be halted but if you press "resume" only the "terminate" button is available, the other two are greyed out. You can't reset the CPU or anything.

    Can you provide a screenshot of when this happens?

    Thanks

    ki

  • well a screenshot does not work I think because of the size. But in fact this seems to only happen when a function returns. In this case at the blue line a return is issued. You see at the top: after it loses focus the buttons available for debug are resume and terminate. Clicking Resume results in the screenshot. Only terminate is clickable. 

    Btw. I found out that a CPU Reset seems to work as well sometimes. There is no need to power reset the whole target and terminate the sessions. But it happens occasionally. 

  • ok, it seems to work! here is the other case where it loses focus too but increases the cpu-load and returns after some seconds.

  • Thanks. The screenshots are helpful.

    In both cases, I see the "Debug" text in the Debug view as italicized. This indicates that the Debug view is in the process of refreshing data. If it stays italicized for a long time, it means some issue with updating the view. This can explain why you lose context. 

    How large is the executable you are loading (*.out file)? 

  • We are loading elf-files. They are up to 3.3 MB.

  • That is not large at all. Would it be possible to share the file with me? You can start a private e2e conversation with me if you do not wish to post to this thread.

    Thanks

    ki

  • Sorry for the late response. 

    Yes this is possible, I will write you a private message. 

    We just had the idea that it is not really related to the CCS or Debugger but maybe to the USB-Ports-/Driver-Implementations at our Notebooks, because they are causing trouble often. Have you heard about such problems from other vendors?

  • This issue is being discussed further via private E2E conversation. Any relevant updates will be posted here

  • what is the status?

  • just a reply so the dashboard does show this topic is still in progress.

  • Sorry for the delayed response. I finally got access to an AM64 EVM and loaded the executables you provided. I do not see any issues so far. No issues with debug context or CCS hanging or locking up. I am using a different debug probe however (XDS560v2 LAN)

    Is your AM64 board a custom one or the EVM?

    Thanks

    ki

  • This happens if you step and the the step doesn't progress but gets unmarked. The target still seems to be halted but if you press "resume" only the "terminate" button is available, the other two are greyed out. You can't reset the CPU or anything

    I believe I can reproduce something similar:

    I can't always reproduce it easily. But when it does happen, I usually see "ClockP" in the call stack for CPU1. I saw this with both my XDS560v2 and XDS110 (onboard and external).

    You are right, a CPU reset will get the target out of this state. It looks like an issue with the state of the CPU and not a debugger issue per se.

    However, I don't see the issue of losing focus or the system CPU load spiking up and locking up CCS. I wonder if that is because I don't have the related source files. 

  • Hey Ki,

    so I did send you the source-file.  maybe this helps here.

    Regards

    Felix

  • Got it, thank you!