I'm having the same problem :
I'm sorry Craig, I did not understant what you said...
It worked until today when I have this same message again and again, and I chaged nothing.
I tried to reinstall VDSP++ but it looks like a driver is missing.
I have branched this to a new discussion, as the cause of the error is unlikely to be related to the thread you posted on originally.
Can you provide a little extra information, and check a couple of things for me.
First, you have selected the "21469 EZ-KIT Lite via Debug Agent" session. This is for the 21469 EZ-Board, coupled with a Stand-Alone Debug Agent (SADA) board. Can you confirm that this is the hardware setup you are using.
When you connect power to the EZ-Board, and USB to the SADA, does anything show up in the Windows Device Manager? If the device is correctly recognised it will show under 'ADI Development Tools', otherwise it may be listed as an 'unknown USB device'.
You say that you have re-installed VisualDSP++: Did you ensure to apply the latest update, Update 10.1? The Base Release of VisualDSP++ 5.0 does not support the 21469 processors or evaluation boards. When the VisualDSP++ installation is correctly updated, the drivers can be found in "...\Setup\Emu_drivers\". The update is available at:
Can you also tell me which operating system you are using? e.g. Windows 7 x64.
Hi Craig ! Thank you for answering so fast.
OS is : Windows 7 x64.
The update version is 10.1.
Yes I'm using the 21469 EZ-Board, but I'm not sure what SADA is. There is a "small card" under the ADSP 21469 in which I plug the USB cable.
When I plug USB to my computer, my computer is looking for a driver and it fails. I actually pointed the driver researching to Emu_drivers and it fails to.
So here is a temporary solution :
I remove the "small card" and replaced it with another (that I extracted from ADSP 21489). And it worked.
So maybe the first "small card" as a problem.
The "small board" on the EZ-KIT Lite is the SADA board. As removing this and replacing it with another works, it does suggest the issue might lie in the SADA board; can you ensure that all jumpers are set the same on both SADA boards?
Note that if you have the older SADA board (ADZS-DBGAGENT-BRD) rather than the SADA2 (ADZS-SADA2-BRD) there are no jumpers.
OK, thanks for your help.
I unplugged then I replugged the SADA and it works now. It is SADA2 with no jumpers.
Retrieving data ...