Sei sulla pagina 1di 7

Blackhawk Emulation Drivers for Windows

Version 1.11.08.16

The Blackhawk\Emulation\Drivers folder contains the latest device drivers supporting

Blackhawk JTAG Emulators for both 32-bit and 64-bit Microsoft Windows Operating Systems. Every attempt has been made to automatically install the drivers and update previous

installations.

install them correctly.

However, if necessary, please refer to the information below on how to manually

Blackhawk(tm) Windows Device Drivers

===================================

Blackhawk

123 Gaither Drive Mount Laurel, New Jersey 08054-1701

Tel: +1 (856) 234-2629

http://www.blackhawk-dsp.com =================================== 2011 (c) EWA Technologies, Inc.

=> VERSION

Version 1.11.08.16

16 Aug 2011

Includes:

USB-PCI

v3.2.0.9

17 Nov 2010

LAN

v2.0.0.4

17 Nov 2010

Bh560v2

v1.0.0.5

09 Mar 2011

=> WHAT’S NEW

Version 1.11.08.16

16 Aug 2011

Corrected the sequence to handle the situation where a Blackhawk device is attached to the system during the driver install.

=> HISTORY

Version 1.11.04.12

22 Apr 2011

RE-Fixed install issue on systems that already had previous installations.

Version 1.11.03.29

29 Mar 2011

Fixed install issue on systems that already had previous installations.

Version 1.11.03.14

14 Mar 2011

Bh560v2 v1.0.0.5 Updated host side drivers to fix issue with STM acknowledge (stall).

Version 1.11.03.03

03 Mar 2011

Fixed Minor Uninstall problem on Windows x64 systems.

Version 1.11.02.10

10 Feb 2011

Modified un/installer cleanup of previous driver files.

Bh560v2 v1.0.0.4 Updated driver package to include support for the Blackhawk XDS560v2-USB Mezzanine Emulator.

Version 1.10.11.17

USB-PCI v3.2.0.9

17 Nov 2010

Modified BH510USB SYS file for processing error codes correctly, where minor codes in XP are critical in Windows 7.

USB-PCI v3.2.0.9

LAN

Bh560v2 v1.0.0.3 Removed “setup” tab from i386 CPL. No longer needed/necessary

v2.0.0.4

For CCSv4 and later.

Version 1.10.10.14

14 Oct 2010

Bh560v2 v1.0.0.2 Modified SYS file for processing error codes correctly, where minor codes in XP are critical in Windows 7.

Version 1.10.08.12

12 Aug 2010

LAN v2.0.0.3 Modified INF file (driver files are the same). Changed Installer to copy LAN560 Files to eliminate the need for manual INF installation.

Version 1.10.03.03

03 Mar 2010

Bh560v2 v1.0.0.1 Added Blackhawk XDS560v2 System Trace Emulator drivers to installer.

LAN v2.0.0.2 Driver package and files are the same. Added BhEthStatus.exe command line utility.

General Moved installer project from using InstallShield to InstallJammer.

Version 1.09.11.20

20 Nov 2009

LAN v2.0.0.2 Fixed an installer issue with Windows 7 (x64).

Also applies for Windows Vista (x64) No actual driver file updates were made.

Version 1.09.03.23

23 Mar 2009

USB-PCI v3.2.0.8 Updated blackhawk.cpl to be backwards compatible with Windows XP Pro x64. Changes with the latest Microsoft build environment for Windows Vista/Server2008 generated some backwards compatibility inconsistencies.

Version 1.09.01.15a

20 Feb 2009

Fixed an installer dialog issue. There is no effect or change to driver files from previous non-a version.

Version 1.09.01.15 LAN v2.0.0.1

15 Jan 2009

BhEthCfg.exe GUI allows more than 9 ports (i.e. BH560ETH n). BH560ETH.SYS updated for proper error return for Vista 32/64-bit. Before, if the IP address specified for the LAN560 did not

exist or accept connection on port 5988, CCStudio or BhEthCfg.exe would hang indefinitely. Now you get the same error as on XP, “Error Initializing Emulator”.

Version 1.08.11.14 USB-PCI v3.2.0.7

14 Nov 2008

BH510USB.SYS fixed issue with multiple ICEPICK_C devices set with Custom=YES declared in CCSetup. BH560USB.SYS modified to issue “reset-port” for VMWare/Linux BHPCI.SYS has minor updates/optimizations.

V1.08.11.10

USB-PCI v3.2.0.5 Fixed kernel mode driver install issue with Windows Vista x64.

V1.08.09.10

Fix install issue with CCS v3.3 drivers.

V1.08.07.29

First deployments of Windows device driver install separate from CCStudio files. Moved drivers to folder:

\Program Files\Blackhawk\Emulation\Drivers.

USB-PCI v3.2.0.3 Updated USB and PCI drivers for possible race conditions and changes in Vista 64-bit driver model requirements.

USB-PCI v3.2.0.1 Added support for new 510-class products (USB510L/USB2000).

LAN v2.0.0.0 USB-PCI v3.2.0.0 This release has updated Windows Device Drivers to include releases for Windows Vista 32-bit and 64-bit versions. This also includes support for the Windows XP Pro x64 operating system.

>> Host Operating System Support

Microsoft Windows 2000/XP/Vista/7 32-bit

Microsoft Windows Vista/XP/7

64-bit

Microsoft Windows 2003 Server

32 and 64-bit

>> Product(s) Supported

USB-JTAG Emulator

USB 2.0 JTAG Emulator P/N: BH-USB-2 (32-bit support only)

P/N: BH-USB-1 (32-bit support only)

PCI510 JTAG Emulator

P/N: BH-PCI-510

USB510 JTAG Emulator

P/N: BH-USB-510

USB510L JTAG Emulator P/N: BH-USB-510L

P/N: BH-USB-2000

USB2000 Controller

PCI560 JTAG Emulator LAN560 JTAG Emulator USB560 JTAG Emulator USB560 JTAG Emulator USB560 JTAG Emulator

P/N: BH-PCI-560 P/N: BH-LAN-560 P/N: BH-USB-560 P/N: BH-USB-560m P/N: BH-USB-560bp

Bh560v2 System Trace Emulator P/N: BH-XDS-560v2 Bh560v2 System Trace Emulator P/N: BH-XDS-560v2-BP

Blackhawk XDS560v2-USB Mezzanine Emulator

=> WHAT’S INCLUDED

Blackhawk\Emulation\Drivers\

P/N: TBD

Main folder with this read me file.

vX.X.X.X signifies the version of the driver INF file for the USB-PCI and LAN drivers within this release, as specified above.

Blackhawk\Emulation\Drivers\USB-PCI\vX.X.X.X

Includes the main INF file, "bhjtag.inf" that will allow the Windows Found New Hardware wizard to determine which drivers to install 32 bit vs. 64 bit for Blackhawk USB and PCI products.

Blackhawk\Emulation\Drivers\USB-PCI\vX.X.X.X\i386

Contains the 32 bit production drivers. Windows 2000/XP/Vista/7 32-bit

Blackhawk\Emulation\Drivers\USB-PCI\vX.X.X.X\amd64

Contains the 64 bit production drivers. Windows XP/Vista/7 64-bit

Blackhawk\Emulation\Drivers\LAN\vX.X.X.X

Includes the main INF file, "bheth.inf" that will allow the Windows Found New Hardware wizard to determine which drivers to install 32 bit vs. 64 bit for Blackhawk Ethernet-based products (i.e. LAN560).

Blackhawk\Emulation\Drivers\LAN\vX.X.X.X\i386

Contains the 32 bit production drivers. Windows 2000/XP/Vista/7

Blackhawk\Emulation\Drivers\LAN\vX.X.X.X\amd64

Contains the 64 bit production drivers. Windows XP/Vista/7 64-bit

Blackhawk\Emulation\Drivers\Bh560v2\vX.X.X.X

Includes the main INF file, "bhdtc.inf" that will allow the Windows Found New Hardware wizard to determine which drivers to install 32 bit vs. 64 bit for Blackhawk USB and PCI products.

Blackhawk\Emulation\Drivers\ Bh560v2\vX.X.X.X\i386

Contains the 32 bit production drivers. Windows 2000/XP/Vista/7 32-bit

Blackhawk\Emulation\Drivers\ Bh560v2\vX.X.X.X\amd64

Contains the 64 bit production drivers. Windows XP/Vista/7 64-bit

>> Installation

The following update can be installed on 32 or 64-bit Microsoft Windows operating systems.

1. Run the Blackhawk Emulation Drivers for Windows EXE distribution.

This should install the latest drivers and mark previously installed emulators to be updated the next time they are attached. When prompted by the “Found New Hardware” wizard, select the option to “automatically locate and install drivers”. If there is an issue where the driver cannot be located, continue with the instructions below.

2. Continue here only if #1 does not work properly.

3. Files should be installed to \Program Files\Blackhawk\Emulation\Drivers

4. If you had your emulator drivers previously installed follow these steps:



For USB and PCI:

A.

Make sure the emulator is installed and/or attached to the PC and powered.

B.

Locate the emulator entry in the Blackhawk Control Panel.

C.

Highlight it with the mouse, right click and choose “Update…” from the pop-up menu.

D.

Browse to folder “\Program Files\Blackhawk\Emulation\Drivers\USB-PCI\vX.X.X.X”, and select the file “bhjtag.inf”.

E.

This will cause Windows to copy, install and update your emulator to the latest Windows device drivers and automatically select the correct 32-bit or 64-bit driver(s).



For LAN:

F.

Browse to folder “\Program Files\Blackhawk\Emulation\Drivers\LAN\vX.X.X.X”, and highlight the file “bheth.inf”.

G.

Right click the file with your mouse and choose “Install…” from the pop-up menu.

H.

This will cause Windows to copy, install and update your emulator to the latest Windows device drivers and automatically select the correct 32-bit or 64-bit driver(s).



For Bh560v2:

I. Make sure the emulator is installed and/or attached to the PC and powered.

J. Locate the emulator entry in the Blackhawk Control Panel.

K. Highlight it with the mouse, right click and choose “Update…” from the pop-up menu.

L. Browse to folder “\Program Files\Blackhawk\Emulation\Drivers\Bh560v2\vX.X.X.X”, and select the file “bhjtag.inf”.

M. This will cause Windows to copy, install and update your emulator to the latest Windows device drivers and automatically select the correct 32-bit or 64-bit driver(s).

5. If you have not had your emulator drivers previously installed, follow these steps:



For USB and PCI:

N.

Make sure the emulator is installed and/or attached to the PC and powered.

O.

When the Windows PnP Found New Hardware Wizard starts, follow the instructions and select the option to automatically install/find drivers.



For LAN:

P.

Browse to folder “\\Program Files\Blackhawk\Emulation\Drivers \LAN\vX.X.X.X”, and highlight the file “bheth.inf”.

Q. Right click the file with your mouse and choose “Install…” from the pop-up menu.

R. This will cause Windows to copy, install and update your emulator to the latest Windows device drivers and automatically select the correct 32-bit or 64-bit driver(s).



For Bh560v2:

S. Make sure the emulator is installed and/or attached to the PC and powered.

T. When the Windows PnP Found New Hardware Wizard starts, follow the instructions and select the option to automatically install/find drivers.

6. At this point your drivers should be updated for your emulator. If you have more than one emulator, you may need to repeat this process.