First time with an ICE-1000 - "Error in final launch sequence"

OK, I looked at a "related" issue from ColinJ.  The reply said "

• Right click on your project and then click on “Debug As: CrossCore Application”. This brings up the launch configuration dialog, and launches the ‘Session Wizard’ dialog.

So....

This led to:

Once I clicked on the "Debug" button the project compiled again and tried to run.  This is the error window I got:

Does anyone have an idea of where to go from here?

Alan

OK, I looked at a "related" issue from ColinJ.  The reply said "

• Right click on your project and then click on “Debug As: CrossCore Application”. This brings up the launch configuration dialog, and launches the ‘Session Wizard’ dialog.

So....

This led to:

Once I clicked on the "Debug" button the project compiled again and tried to run.  This is the error window I got:

Does anyone have an idea of where to go from here?

Alan

More info I just found.  I tried the ICE Test and got this result:

 So I looked at one of the PDFs for the ICE-1000 and it said the the most common cause is the emulator driver is not installed correctly.  I dove into the Emulator Properties window and found this intriguing piece of information.

My question is why would the device not start but the "Device status" portion of the "General" tab shows "The device is working properly"? Is the device actually starting? If so why can't the ICE Test complete properly?

Confused again Alan

Hello,

Could you please try replacing the original files in your installation with the attached ones and uninstall the existing driver, and install the new one. Hopefully this helps.

Please find the attached emulator drivers and place them into below path:
<installation path>\Analog Devices\CrossCore Embedded Studio 2.8.2\Setup:\Setup\Emu_Drivers

Refer to the chapter "Installing drivers manually" in Emulator and Evaluation Hardware Troubleshooting Guide
https://www.analog.com/ee356

On occasions, target connection errors can be caused by the processor booting corrupt code. If possible, please try changing the boot mode of the processor to default and let us know if this has any affect on the behavior you're seeing.

If you are still facing the same issue, can you please answer the following questions to assist you further on this issue?
1. Try opening the example in the new workspace and let us know if you are facing the same issues.
2. Do you have another target board you can use to connect to your emulator with? Does that still behave the same way? Do you still encounter the same error messages?
3. Do you have access to another PC? If you do, please let us know if the driver successfully installs on this machine. Are able to connect ICE-1000/2000 with CCES now?
4.Please let us know that you have purchased the board directly from Analog Devices or from distributor.
5. Complete screenshot of the system information of your both machines. This can be done by pressing Windows+R to open the Run box. Type “msinfo32” into the “Open” field, and then hit Enter.

Regards,
Santha kumari.K

ez.analog.com/.../Emu_5F00_Drivers.rar

Hi Santha,

I tried to load the new drivers on my Win10 laptop.  Win10 fought me all the way.  It decided that the installed CCES 3.8 drivers were newer and wouldn't even allow me to update/load the files fro the RAR file you sent me.

I did get a CCES 3.7  from a co-worker that installed well and I finally have the ICE testing working and completing.

This is what I currently have for a "Debug Configurations" on a stripped-down project:

The "Application with CrossCore Debugger at least doesn't report any errors before hitting the "Debug" button. Both the "GDB and OpenOCD" and "GDB and QEMU" selections have this in the upper portion of the window : "(Main): This program dies not match the selected debug session type", and I have a grayed-out "Debug" button.

When I do press the "Debug" button on the "CrossCore Debugger" selection I still get this Error window:

I'm stuck at this point. I will be running this problem by our hardware engineer for analysis.

Alan

Hi,

Please note that, GDB and OpenOCD (emulator) or QEMU (simulator) is used for ARM core-only debugging.

For Blackfin BF700 processor you have to use "Application with Crosscore Debugger" from debug configurations window.Please try importing your example in new workspace and debug your project and let us know how you gets on.

As you are using a custom board, can you please confirm that it complies with the JTAG Technical Reference Guide EE-68, which is available online at the following location:
http://www.analog.com/ee68

If you are still facing the same issues, could you please answer the sort of questions that we asked in previous response.This will help us to assist you better.

Regards,
Santha kumari.K

Hi Santha,

I got my debugging going by downgrading to CCES 2.7.0. I was not able to debug using 2.8.0, but a co-worker got debugging to work with 2.7.0.  I'm good, please close this out.

Alan