Select 'Have Disk' and browse to \Setup\Emu_Drivers Choose "Search for the best driver in these locations", 'Next'.ġ5. Choose "Install from a Specific Location", 'Next'.ġ4. At this point Windows should detect the new hardware.ġ3. ![]() Disconnect USB cable from the ICE-1000.ġ2. Note: searching for files containing this string should return several files named "oem**.inf", all of which are Analog Devices inf files, and must be deleted to ensure that your system does not pick up the existing drivers.ĩ. Go to Windows\inf folder (note this may be hidden) and search or grep for "89982A59-5EEA-45aa-AF97-52EC351018C2", delete all files which contain this string. Go to Windows\system32 folder and delete the WmHpUsb.sys and WmUsbIce.sys files.ħ. Go to Windows Device manager and uninstall the driver for the "ICE-1000" from the Cross core Development tools.Ħ. Note: The driver for all emulators and evaluation boards in 32 - bit Operating Systems is WmUsbIce.sys and in 64 - bit Operating Systems is WmUsbIce64.sysġ.Disconnect power and USB cable from the ICE-1000.ĥ. : \ Analog Devices \ CrossCore Embedded Studio x.x.x \ Setup \ Emu_Drivers \ You can find the Emu-drivers from the below path. When the installer requests a location from which to install the driver, navigate to the driver location: ![]() Click the Driver tab and choose Update Driver. The Device Properties dialog box appears. To install the driver manually follow below steps:ĭouble-click on the device. If listed,double-click on your emulator to show the driver properties and ensure there are no issues listed. You should find your emulator listed under 'ADI Development Tools' or 'Cross core Development tools'. Also we have attached the emulator drivers herewith.Ĭan you please check that your emulator is installed properly by checking your computer's 'Device Manager'. The emulator and evaluation board hardware device drivers are installed automatically when the device is plugged in and powered up for the first time after installing CCES and VDSP tools. The ICE test fails in Opening Emulator Interface, the most common cause is that the emulator driver is not installed properly. We understand that you have already contacted our private support.To avoid duplication of efforts, you can continue the discussions through private support and we will post the final resolution here for others to benefit. My computer is running Win7 professional 64bit. Note that the error is identical on both the SADA2 and ICE1000 emulator boards. Please help, I don't have a clue what might go wrong here. Although, the device driver seems to point to some general "winusb.inf", and I can't get this to change. But this is done automatically after selecting adiusb.inf as device driver, as instructed in EE-356. ![]() That's what I think too.īut, if I open the device manager, everything seems to work fine, except for the driver files to be in the "system32" map, while I'm on a 64bit system. It says that "the most common cause is that the emulator driver is not installed properly". I checked EE-356 Troubleshooting document and can't find anything. So, I guess it's not a broken hardware problem. This is identical if I use the SADA2 board that came with the EZkit, or if I use the ICE1000 emulator we already purchased for future custom boards. In the ICE test utility the first item fails "Opening emulator interface - could not open emulator interface. I have a new ADSP-21489 EZkit, but can't get it to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |