Hanging debug session

Hi,

Thank you for your inquiry.

Can you please let us know which version of CCES that you are using.

Are you facing this issue in specific project or all projects.

Waiting for your reply.

Best Regards,
Santhakumari.K

I am facing this issue in my project for custom board. I noticed this issue in 2.12.0 and 2.12.1. I try to test in 3.0.2 and this issue raised there.

Hi,

Could you please answer to the below questions.

1. Please provide more details about the error message that you are facing along with screenshot. In your query you mentioned that "I find next solutions: create new workspace or rewrite the folder .metadata/.plugins from backup version.". Here can you provide more information about "backup version". Did you mean like the same application works in older versions of CCES

2. Are you facing this error always or randomly and also please run the code in another custom board and let us know the results. This will be helpful for us to isolate the issue.

3. Could you please let us know whether you are able to run a simple project in your custom board.

4. Can it be possible for you to simulate the issue in ADSP-21569 Evaluation kit if you have or help us to simulate the issue along with steps.

5. Also please share us your metadata file in a zip format from workspace where the issue will be simulated

This will help us to proceed further.

Waiting for your reply.

Regards,
Santhakumari.V

Hi.

1. Please provide more details about the error message that you are facing along with screenshot.

No errors. I press F5 or Debug button than I wait 3-5 minutes after it I can debug.

. In your query you mentioned that "I find next solutions: create new workspace or rewrite the folder .metadata/.plugins from backup version.". Here can you provide more information about "backup version". Did you mean like the same application works in older versions of CCES

I develop test solution without control version system. So sometimes I do archive of my develop folder. That folder include source folders and CCES folders:

For example:

Develop folder

1. CCES

1.1. .metadata

1.1.1. .plugins

1.2. the folder of my CCES project

2. Source (that folder has many nested folders)

Before archiving I clean the data from plugin .metadata/.plugins/org.eclipse.cdt.core

If enter to debug became longer than normal I can delete .metadata folder and copy it from the from nearest archive.

I don't change CCES version when I delete and copy .metadata folder 

2. Are you facing this error always or randomly and also please run the code in another custom board and let us know the results. This will be helpful for us to isolate the issue

As I said I develop test solution. So it take the time to check it to another board.

3. Could you please let us know whether you are able to run a simple project in your custom board.

Yes. When I found occurring of the issue I try to develop some project from ADSP-2156x_EZ-KIT BSP. And the problem was gone. The difference between debug sessions is my debug session doesn't preload.exe.

4. Can it be possible for you to simulate the issue in ADSP-21569 Evaluation kit if you have or help us to simulate the issue along with steps.

ADSP-21569  EZ-KIT doesn't permit to use my code without changing and it can demand some time.

5. Also please share us your metadata file in a zip format from workspace where the issue will be simulated

I try to prepare data. But now I'm busy with another tasks. I will return.

Best regards.

Hi,

Can you please check if you have set the CCES_HOME environment variable in your PC. If you set the environmental variable CCES_HOME to any of the CCES install directory, then Debug sessions will not operate correctly.

If there, Please try remove environment variable from your PC and restart CCES and then debug your session.

If you still facing the issue, We recommend to use the new workspace as you discovered already, A ".metadata" folder is where your CrossCore Embedded Studio (CCES) preferences and intermediate files created by Eclipse plugins. And It's just stores all the project errors and warnings in the particular workspace.

Copying the .metadata/plugins from the existing workspace will not help you though.

Regards,
Nishanthi.V

Hi.

I checked Environment Variables and CCES_HOME is missing.

The first time when the issue appeared I tested CCES 2.12.0. I reassembled my project as new in CCES 3.0.2 and the issue is gone. After about 1.5-2 months when I started debug  without getting supply voltage to my board I got an error. After it the debug session may start very slow.

Best regards.

Hi.

I checked Environment Variables and CCES_HOME is missing.

The first time when the issue appeared I tested CCES 2.12.0. I reassembled my project as new in CCES 3.0.2 and the issue is gone. After about 1.5-2 months when I started debug  without getting supply voltage to my board I got an error. After it the debug session may start very slow.

Best regards.

Hi,

In order to find the cause of the issue, There is a log file that is generated by CCES that can be found in the .metadata folder inside the workspace. It is called CrossCore(R) Embedded Studio.log. There is also a .log file in that same folder. Please send those to us after crashing. Note, they should enable logging before the file can be generated.

To enable logging, in CCES main menu, enter Window->Preferences. Then in the left tree view of the page, enter General->Logging. Enable ‘Log debug events to the debug file’ check box and click "Apply and close".

It would also be useful if they could create a .zip file only with the .metadata directory that's located in work space directory and share it with us.

Do you have access to another PC? If you do, please let us know, whether you are facing the issue only on your PC or on another PC as well.

Also, please let us know if transitioning to a new workspace poses any challenges for you.

Regards,
Nishanthi.V