Connection to target with debugger

Hi Fabien,

Thank you for your inquiry.

When CCES connects to the emulator target, it will try halting the target's processor or core if it is running. From the error screenshot we suspect that the emulator target failed to halt the processor/core. This happens when the hardware is in a bad state and it needs to be power cycled . Usually unplug the board's power cable, unplug the emulator's power cable, plug the power cables back into board and emulator, and re-launch the debug session, to get around this error.

Also please ensure that boot mode switch has been set to No boot while debugging the application. Kindly try some basic examples from the below BSP and let us know the results.
C:\Analog Devices\EV-2156x_EZ-KIT-Rel3.0.0\EV-2156x_EZ-KIT\Examples\services\gpio\LEDBlink

If you are still facing the same issue, can you please share us the below details to assist you further on this issue.

1. Does the ICE Test utility run successfully or does it fail at any point? If the Test fails, please provide us with a screenshot showing the ICE Test results.

2. Do you have any other emulators of the same type or different one, which operates correctly with the same target board and PC?

3. Does the emulator is detected by PC ? Check whether the emulator listed under 'Crosscore tools'. If listed, double-click on the emulator to show the driver properties and ensure there are no issues listed. If there, please share the screenshot of the device manager which shows the emulator and screenshot of the driver tab by clicking the emulator > properties > Driver.

Waiting for your reply.

Best Regards,
Santha kumari.V

Hello and thanks for the prompt answer!

Boot mode is 0 for no boot. Your interpretation about failing to halt the processor confirms what I thought.

I created a new workspace, imported the blink example => it works, I can load, attach to the target and step debug

Closed CCES, tried again => still working

Closed again, tried again => stops at loading, impossible to attach to the target anymore (but program is loaded)
unplugged power, unplugged USB, closed CCES, relaunched, replugged => not working

Did this several time, impossible to make it step debug.

1. ICE test did not fail a single time. LED is green, truns purple when loading.

2. Debug Agent has the same issues than ICE1000. Exactly the same behavior.

3. No problems with the driver, "This device is working properly."

I did not have a single error this time. It just stops at "Load complete" with no more message.

Thank you for any help you could provide me. I am quite stuck at the moment.

Best,

Fabien

Hi,

Could you please let us know whether you have connected cable in the USB hub port. If so, try connecting it directly to a dedicated USB port on your PC and check if the issue persists.

To use the board with Debug Agent connection, all positions on SW1 (on the carrier board) must be in the ON position. Can you confirm once.

Inorder to isolate the issue, try connecting the board on a different PC and see if the same problem occurs.

Also, let us know whether you have set the environment variable(CCES_HOME) in your machine for specific version of CCES.

CCES_HOME can be used to overwrite internal behavior but is not generally required to be set by the user. If you set the environmental variable CCES_HOME to a directory other than the CCES installation that you're using then Debug sessions will not operate correctly.

Note that, CCES_HOME shouldn't be used, and it isn't required. In fact, it's use has been dropped in CCES 2.9.4+.

So, remove the environment variable in your PC(if set) by following.

The steps to check the Environment variable PATH:

1. Go to Control Panel -> System and Security -> System
2. Click the Advanced system settings.
3. Click Environment Variables.
4. Find and remove the CCES variable.

Now, try opening CCES with the new workspace and see if the issue persists.

Regards,
Santhakumari.V

Hello,

Thank you for your time.

We found the issue, and it is now working properly.

When in debug perspective, launching a debug session will not always display the step debugger, neither fill the disassembly/breakpoint/variables tabs. It is often needed to manually click on the "Debug" tab next to the "Project" tab, on the left side of the screen to actually allow step debugging. As I was often on the tab displaying project files, I could not debug.

This behavior is not systematic and apparently depends on the state in which the project was closed.

Fabien