Broadcom (R) Corporation

Broadcom USH CD
for the BCM5880/BCM5882 USH product
RELEASE 3.0.00031.30.7.021.0
(06/28/2014)
RELEASE NOTES
These notes describe release software for the BCM5880 USH Product
For release version information for individual products, see the
"Release Version Information Table" below.
Software Compatibility
======================
This release of software supports:
- BCM5880 USH with A0/B0/C0 step silicon version.
- BCM5882 USH with A0/B0 step silicon version.
Upgrading from the Previous Driver Release
==========================================
It is highly recommended that you upgrade any previous installations
of the Broadcom BCM5880/BCM5882 USH software.
If you are installing on a platform that is currently running DCP version 1.
3
or earlier (with USH firmware 1.3 or earlier), the upgrade to DCP version 3.
0
(and USH firmware 3.0) MUST occur in the following order:
1) Upgrade firmware to 3.0
2) Upgrade USH host components to 3.0
Contents of the CD
==================
*** Release Version Information Table ***
Product
1.
2.
3.
4.
5.
6.
7.
8.
9.

Version

USH Firmware
30.7.021.0
MA Bios-Driver
4.0.4
MP Bios-Driver
4.0.4
WinXp Drivers and Applications
4.1.3
USH DOS Diagnostics
2.17
CV host software
0.24G
CV host software 64 bit
0.24G
CV Firmware
1.0.2.53
Installer for host components that 3.0.00029
includes USH host components

Previous Rel.
30.7.020.0
4.0.4
4.0.4
4.1.3
2.17
0.24G
0.24G
3.0.00028

This release contains the following software programs:

1) BCM5880 USH Firmware. Supports TPM 1.2 and PCSC. For more
deatils, please refer to the release notes under firmware/
2) USH MA Bios-Driver. Supports TPM 1.2 for TPM bios access. For more
details, please refer release notes under bios-driver/madriver
3) USH MP Bios-Driver. Supports TPM 1.2 for TPM bios access. For more
details, please refer release notes under bios-driver/mpdriver
4) USH Windows XP TPM drivers and tpm applications which includes
TPM Diagnostics and Firmware upgrade tool. For more details,
please refer release notes under windowsxp/
5) CV host sofware that includes CV USB host driver, CV API user library,
User DLL, and applications. For more details refer to release notes
under windowsxp and windowsxp/cv
6) CV host software for XP 64 bit platform. Includes CV USB host driver,
CV API user library, User DLL and applications.
7) Installer for host components. This includes CV, TPM and UCC components.

Changes/Additions
=================
In Release 3.0.00031.30.7.021.0
===============================
Firmware:
- added CID 7 FW images
In Release 3.0.00030.30.7.021.0
===============================
Host:
CVUSB/WBF WHQL'd drivers supporting Windows 7, Windows 8 & Windows 8.1
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to
erase the 2079x NVRAM and instruction will be provided.
In Release 3.0.00029.30.7.021.0
===============================
Firmware:
ESPSW-2826: Fix for RFID card enrollment in Windows 7.
ESPSW-2740. Route Mifare tags back to HID since Mifare Classic 4K tags a
re proprietary NXP.
ESPSW-2693: Implemented action items 4, 6 and 11 from a CID-7 review mee
tings, based on a decision in the meeting.
Host:
-

ESPSW-2693. WHQL'd drivers.

ESPSW-2808 wpeushupgrade modified to only update PBA on systems that su

pport bios PBA app.
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to
erase the 2079x NVRAM and instruction will be provided.
In Release 3.0.00028.30.7.020.0
===============================
Firmware:
- ESPSE-2740. Routed Mifare Classic tags to NFC.
- ESPSW-2733: Fix for the "card left on the reader" scenario. For a boot
up case, on the first power on message from the NFC driver, suspend the HID sta
ck and then call resume only when we get RF_DISCOVER from the NFC driver (meanin
g that it's ready) and don't pass activations to HID during that time. For the r
esume from S3 case, reset the value of bIsRunningTrasceive flag to workaround a
problem in the HID code which doesn't handle this flag properly. Also changed th
e timeout in an NFC diag to fix the CV timeout problem from ESPSW-2757.
- ESPSE-2747. Ok to clear the pktProcessing flag before sending usb resp
onse to host.
Notes for this release:
- Mifare Classic tags are also routed to NFC stack. The only tags that c
an be enrolled by DDPST are iClass tags.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are sh
ared with the UART. Please disconnect the RX line if you have the USH console co
nnected for proper detection of the NFC module
- In certain cases, the 2079x firmware may not be properly updated by th
e NFC driver. If a yellow bang on the driver is observed after installation, we
need to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM
and instruction will be provided.
In Release 3.0.00027.30.7.019.0
===============================
Firmware:
- ESPSW-2693: When the NFC chip is powered off, stopping the HID polling
. To prevent a 3 seconds loop trying to wait for insertion, when the NFC chip is
powered off, not allowing to read a contactless card id
- ESPSW-2752. Routing DesFire T4 and Mifare T4 tags to NFC in case Dell
makes a decision this way.
Host Components Installer:
- ESPSW-2724. Following changes in the NFC driver. Antenna tuning change
s for CAC/PIV cards. Wait longer (1 sec) for CORE_RESET NTF in the USB "test" co
mmand procedure.
Known Issues:
- S3/S4/Reboot issues are observed when RFID tag is placed on reader.
Notes for this release:
- Since Dell has not decided how to handle NFC Forum T4 tags, this relea
se routes Mifare and DesFire T4 tags to NFC as a test. This results most CAC/PIV

cards to go the NFC stack as well. Please make sure NFC stack does not lockup o
r yellow bang with CAC/PIV cards. Even with this change some Mifare Classic T4 c
ards will show up as RFID tags.
- Changes were made to NFC driver and USH firmware. Please retest S3/S4/
Reboot cases (without tag on reader) to see if you notice improvement.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are sh
ared with the UART. Please disconnect the RX line if you have the USH console co
nnected for proper detection of the NFC module
- In certain cases, the 2079x firmware may not be properly updated by th
e NFC driver. If a yellow bang on the driver is observed after installation, we
need to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM
and instruction will be provided.
In Release 3.0.00026.30.7.018.0
===============================
Firmware:
ESPSW-2757: Properly restarting the NFC timer and the discovery after ru
nning the NFC diag commands. This is needed because without this change the stac
k was dead after running an NFC diag command.
ESPSW-2814, ESPSW-2815, ESPSW-2816, ESPSW-2752, ESPSW-2740. Fixed interr
upt issue. Enabled DesfireT4 and MifareT4 tags for NFC.
ESPSW-2747, ESPSW-2804, Added 100ms delay in 2079x power up sequence to
help with SPI_INT autosense.
Host Components Installer:
ESPSW-2693: Added NFC drivers for Windows 7 to the release folder.
ESPSW-2729, ESPSW-2785 and ESPSW-2818: In Win7 NFC endpoint should be di
sabled so for RFID diags to work in Win7 the code needs to be based on the NFC p
resence bit instead of on the NFC enabled bit.
ESPSW-2693: The broadcom usbccid smartcard driver (in Win7) should not u
se the NFC endpoint. This change is needed to allow the Win7 NFC driver to use t
he NFC endpoint.
ESPSW-2612: Merging from 2.3.x branch. Checking in these config files th
at we've received from Dell based on their request. They say that they still see
the error "You PC needs the following feature: .NET 3.5" but our PQA cannot rep
roduce it. We've been considering 2612 as fixed already.
ESPSW-2793: Updating the NFC Windows 7 drivers to the latest.
ESPSW-2733: Updated NFC drivers to version 410.
Known Issues:
On Windows 7, the Microsoft Inbox CCID drivers will install. The brcmcci
d driver was updated and will not install on Windows 7 platforms until the drive
rs are WHQL d.
Notes for this release:
This release also include includes preliminary support for Windows 7 (Re
lease 1.5).
To install NFC drivers for Windows 7, the following command should be us
ed msiexec /i CVHCI.msi NeedNFCW7=1 or msiexec /i CVHCI64.msi NeedNFCW7=1
The NFC tray application can be used to test NFC functionality on Window
s 7.
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the

NFC driver. If a yellow bang on the driver is observed after installation, we ne

ed to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM an
d instruction will be provided.
In Release 3.0.00025.30.7.016.0
===============================
Firmware:
ESPSW-2799. Backed out additional interrupt code including setup code.
In Release 3.0.00024.30.7.015.0
===============================
Firmware:
- ESPSW-2806. Updated HID library rc6 to support suspend/resume. USH fir
mware code added to suspend HID stack on NFC chip power off and resume HID stack
on NFC chip power on.
- ESPSW-2729: Fixed individual test for iClass 14b cards
- ESPSW-2813: init_get_systemID should not be hardcoded to return 2
- ESPSW-2799. Temporarily backed out interrupt mode pending further inve
stigation on S3 stability.
Host Components
- ESPSW-2789. Updated NFC driver to program antenna tuning registers cor
rectly. This should improve detection and performance of failing CAC/PIV cards.
WinPE
- ESPSW-2693. Updated WinPE NFC drivers.
Known Issues:
- For 64-bit installs Microsoft Test certificate should be pre-installed
.
Other notes:
- This release backs out the Interrupt change, per further investigation
of stability during S3 resume issue. Please verify S3 stability is same as prio
r release without interrupt. Also please
test whether is JIRA 2815 & JIRA
2816 are seen with this release.
- This release includes updated NFC drivers which properly programs the
antenna tuning values. This should improve CAC/PIV detection. Please retest all
NFC/RFID tags as discussed.
Tuning parameters for CAC/PIV will be provided s
eparately.
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are sh
ared with the UART. Please disconnect the RX line if you have the USH console co
nnected for proper detection
of the NFC module
- In certain cases, the 2079x firmware may not be properly updated by th
e NFC driver. If a yellow bang on the driver is observed after installation, we
need to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM
and instruction will be provided.
- When running the individual RFID test please place the card after clic
king Run Test .
In Release 3.0.00023.30.7.014.0
===============================
Firmware:
ESPSW-2799. Enabled interrupts on SPI Int GPIO line. Interrupts are only
enabled for short duration after NFC command is sent to handle credit notificat
ions faster. Trimmed NFC debug output.
ESPSW-2729: Implemented the individual test. Also cleaned up some tempor

ary code that we had. Note: At the moment, the user has to place the card after
clicking "Run Test".
ESPSW-2808. Updated do not update systemIDs.
Host Components:
ESPSW-2808Only update PBA on systems that support bios PBA app.
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM an
d instruction will be provided.
When running the individual RFID test please place the card after clicki
ng Run Test .
In Release 3.0.00022.30.7.013.0
===============================
Firmware:
ESPSW-2747. Added code to power on the NFCC after restart. Initialized r
fid activated flag.
ESPSW-2802. Updated HID library to fix SEOS functionality. Updated remov
al polling and credit notification handling.
ESPSW-2744: Fix for the "reset card" loop. To avoid this infinite loop a
dded a small 3 seconds timeout to this loop while waiting for a contactless card
placement. Note that this is just a fix for the loop. We are still looking into
why CLSC is not working after resume from S3.
ESPSW-2785: Implemented a low risk change to get the grp diag to work wh
en in cv only radio mode. This fixes the issue as described in this Jira and in
BITS152899. But at this moment, enrollment and authentication does not work in c
v only radio mode.
Host Components:
ESPSW-2744: Fix for the "reset card" loop. To avoid this infinite loop a
dded a small 3 seconds timeout to this loop while waiting for a contactless card
placement. Note that this is just a fix for the loop. We are still looking into
why CLSC is not working after resume from S3.
ESPSW-2794, 2799, 2744, 2733. Updated NFC drivers to address resume from
S3 issue and enable UseSCR setting in registry.
Notes for this release:
Several changes were made to the USH firmware and NFC driver, please ret
est the following JIRAs: ESPSW-2802, 2795, 2754, 2751, 2729 (Should pass all Grp
tests on all cards except CAC/PIV)
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM an
d instruction will be provided.
In Release 3.0.00020.30.7.012.0
===============================

Firmware:
ESPSW-2770: Setting NFC presence flag at initialization time, based on i
f the NFC device is available
ESPSW-2693. Set SPI CS to high if timeout. Added proper timeout error ha
ndling to nci_cmd_rsp.
ESPSW-2771. Prevented queueing of multiple NFC packets which was causing
overflow of USH task queue.
ESPSW-2740, ESPSW-2796, ESPSW-2782, ESPSW-2776, ESPSW-2751, ESPSW-2740,
ESPSW-2726, ESPSW-2729. Updated HID library version rc3
ESPSW-2693. Clear isActivated flag when NFC tag is detected
Known Issues;
There seems to be an issue with resume from S3 in this release. (Workaro
und is to Enable/disable NFC driver after resume).
Notes for this release:
UseSCR=1 Registry setting is required.
Several changes were made to the USH firmware, please retest the followi
ng JIRAs: ESPSW-2747, 2734, 2754.
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM an
d instruction will be provided.
In Release 3.0.00020.30.7.011.0
===============================
Firmware:
ESPSW-2782. ESPSW-2776. ESPSW-2726. ESPSW-2752. ESPSW-2740. Updated HID
library with improved handling for NCI Deactivate NTF and improved removal hand
ling. Resolved issue where card had to be removed from the field following a Pro
cessCard APDU before being available for new commands.
ESPSW-2652, ESPSW-2647: Merging from 2.3.x branch a fix for the consiste
nt contactless yellow bang issue in Windows 8.1 and also intermittent contactles
s yellow bang issues that are seen during stress testing in Win7 and Win8.1
ESPSW-2770: Don't allow enabling NFC when NFC is set as not present.
ESPSW-2746: As part of the fix to this ushupgrade problem we see that if
a user doesn't swipe a finger during the physical presence request for 30 secon
ds (for example because the user looks away from the screen at that time), the p
opup window disappears and the upgrade fails. Increasing this timeout to 5 minut
es.
Host Components:
ESPSW-2770: Don't allow enabling NFC when NFC is set as not present.
ESPSW-2780. Removed multiple KMDFLibraryVersion statements from inf file
.
WinPE:
ESPSW-2693: Updated NFC drivers in the WinPE release folder to the lates
t version that we currently use - 370.
Notes for this release:
UseSCR = 1 Registry setting is required.
Known Issues:

Following RFID tags currently do not work: iClass SEOS Px JAH

On 64-bit systems. MSFT Test certificate should be pre-installed into th
e trusted root of Local machine store on the laptop before installing the HCI.
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of NFC module.
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separater utility to erase the 2079x NVRAM i
s provided.
In Release 3.0.00018.30.7.010.0
===============================
Firmware:
ESPSW-2749. Can t enroll fingerprints using upek sensor.
ESPSW-2759. Sometimes cant login OS on resume from S3
ESPSW-2743. Fingerprint icon disappear in Gina after resume from S3/S4
ESPSW-2750. NFC Type 1 & Type 3 read value shows empty.
ESPSW-2652. MSFT Usbccid becomes yellow banged after ushradio mode.
ESPSW-2647. Contactless card get yellow bang.
ESPSW-2722. WriteDelay of 50ms registry setting required for NFC drivers
.
ESPSW-2723. Firmware patch filename change in NFC driver package.
ESPSW-2746. First time to upgrade USH firmware will show error message.
ESPSW-2760. It will show Broadcom Usbccid Smartcard Reader yellow bang r
esumed from hybrid S3
ESPSW-2773. It will show Broadcom Usbccid Smartcard Reader yellow bang r
esumed from hybrid S3
ESPSW-2747. NFC proximity device shows yellow bang after resume from S3.
Updated HID driver to detect Samsung tectiles tag.
Host Components:
ESPSW-2725. Topaz NFC tags do not work.
Notes for this release:
Note the firmware from this release requires updated drivers included in
the release.
Please update the firmware first and then update the NFC drivers by inst
alling the HCI.
Failure to do so may cause issues.
WriteDelayMs Registry setting of 50ms is no longer required.
Several changes were made to the USH firmware and NFC drivers, please re
test the following JIRAs: ESPSW-2736. ESPSW-2753, ESPSW-2735, ESPSW-2769, ESPSW2737, ESPSW-2758, ESPSW-2748.
Known Issues:
Following RFID tags currently do not work: iClass SEOS Px JAH
On 64-bit systems, MSFT Test certificate should be pre-installed into th
e trusted root of Local machine store on the laptop before installing the HCI..
Other notes:
GPIO code for detection of NFC module reads GPIO pins 0/1 which are shar
ed with the UART. Please disconnect the RX line if you have the USH console conn
ected for proper detection of the NFC module
In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after installation, we ne
ed to erase the NVRAM on the 2079x. Separate utility to erase the 2079x NVRAM an
d instruction will be provided.

In Release 3.0.00016.30.7.009.0
===============================
Firmware:
ESPSW-2729. Updated HID library to address the Grp/Ind diag test.
Known issues:
- Following NFC tags are known to be detected: T4T MiFare Classic 32 byte, T3T F
elica Lite, T2T Kovio, NFC Forum Type 2 Tag, Tag-it Pro (256 bit), T2 MUL 64, T2
MUL 192.
- Following NFC tags currently do not work: Topaz 512K
- Following RFID tags are known to be detected: iClass Clamshell, iClass GP, iCl
ass Px G8L, DesFire D8H, 1430L
- Following RFID tags currently do not work: iClass SEOS Px JAH.
- On 64-bit systems, MSFT Test certificate should be pre-installed into the trus
ted root of Local machine store on the laptop before installing the HCI.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are shared wit
h the UART. Please disconnect the RX line if you have USH console connected for
proper detection of NFC module.
- After installation the WriteDelayMS registry entry must be set to 50. To do so
, open regedit, and search for StartupSequence . It should take you to the registry
settings for the driver. Please add two REG_DWORD values for UseSCR and
WriteDela
yMs . To do this right click on the right hand pane and select New and DWORD (32-b
it) value. Set UseSCR to 1 and WriteDelayMs to 50 (decimal)
- In certain cases, the 2079x firmware may not be properly updated by the NFC dr
iver. If a yellow bang on the driver is observed after installation, we need the
erase the NVRAM on the 2079x. Separate utility to erase 2079x NVRAM and instruc
tions will be provided.
In Release 3.0.00016.30.7.007.0
===============================
Firmware:
- ESPSW-2727. RFID Desfire tags do not work.
Host Components:
- ESPSW-2728. Restarting the PC (warm boot) causes yellow bang on smartcard.
- ESPSW-2694. WinPE 4.0 not able to detect USH.
The following may also be address, please retest with this release:
JIRAs 2733, 2735, 2739
Known issues:
- Following NFC tags are known to be detected: T4T MiFare Classic 32 byte, T3T F
elica Lite, T2T Kovio, NFC Forum Type 2 Tag, Tag-it Pro (256 bit), T2 MUL 64, T2
MUL 192.
- Following NFC tags currently do not work: Topaz 512K
- Following RFID tags are known to be detected: iClass Clamshell, iClass GP, iCl
ass Px G8L, DesFire D8H, 1430L
- Following RFID tags currently do not work: iClass SEOS Px JAH.
- On 64-bit systems, MSFT Test certificate should be pre-installed into the trus
ted root of Local machine store on the laptop before installing the HCI.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are shared wit
h the UART. Please disconnect the RX line if you have USH console connected for
proper detection of NFC module.

- After installation the WriteDelayMS registry entry must be set to 50. To do so

, open regedit, and search for StartupSequence . It should take you to the registry
settings for the driver. Please add two REG_DWORD values for UseSCR and
WriteDela
yMs . To do this right click on the right hand pane and select New and DWORD (32-b
it) value. Set UseSCR to 1 and WriteDelayMs to 50 (decimal)
- In certain cases, the 2079x firmware may not be properly updated by the NFC dr
iver. If a yellow bang on the driver is observed after installation, we need the
erase the NVRAM on the 2079x. Separate utility to erase 2079x NVRAM and instruc
tions will be provided.
In Release 3.0.00014.30.7.006.0
===============================
Firmware:
Bug Fixes
- JIRA 2712 It returns 0x100003 when run CV Read NFC UUID
- JIRA 2713 Yellow banged on NFC Proximity device after running
n Windows ushdiag.

CV Read NFC UUID i

Known issues:
- Following NFC tags are known to be detected: T4T MiFare Classic 32 byte, T3T F
elica Lite, T2T Kovio, NFC Forum Type 2 Tag, Tag-it Pro (256 bit), T2 MUL 64, T2
MUL 192.
- Following NFC tags currently do not work: Topaz 512K
- Following RFID tags are known to be detected: iClass Clamshell, iClass GP, iCl
ass Px G8L.
- Following RFID tags currently do not work: DesFire D8H, 1430IL, iClass SEOS Px
JAH.
- Restarting PC causes yellow bang on both smartcard drivers. Disabling/enabling
the smartcard makes things work again. This issue is not observed on cold boot.
- On 64-bit systems, MSFT Test certificate should be pre-installed into the trus
ted root of Local machine store on the laptop before installing the HCI.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are shared wit
h the UART. Please disconnect the RX line if you have USH console connected for
proper detection of NFC module.
- After installation the WriteDelayMS registry entry must be set to 50. To do so
, open regedit, and search for StartupSequence . It should take you to the registry
settings for the driver. Please add two REG_DWORD values for UseSCR and
WriteDela
yMs . To do this right click on the right hand pane and select New and DWORD (32-b
it) value. Set UseSCR to 1 and WriteDelayMs to 50 (decimal)
- In certain cases, the 2079x firmware may not be properly updated by the NFC dr
iver. If a yellow bang on the driver is observed after installation, we need the
erase the NVRAM on the 2079x. Separate utility to erase 2079x NVRAM and instruc
tions will be provided.
In Release 3.0.00014.30.7.006.0
===============================
Firmware:
- Updated HID library.
- Fixes to allow NFC chip firmware upgrade.
- Note: Due to a server issue, the firmware could not be built normally, and the
refore had to be compiled manually.
Host Components:
- Updated NFC drivers to version 340.
WinPE:

- NFC firmware upgrade through WinPE.

Bug Fixes:
- ESPSW-2718. CVHCI cannot be installed on 64-bit systems.
Known issues:
- Following NFC tags are known to be detected: T4T MiFare Classic 32 byte, T3T F
elica Lite, T2T Kovio, NFC Forum Type 2 Tag, Tag-it Pro (256 bit), T2 MUL 64, T2
MUL 192.
- Following NFC tags currently do not work: Topaz 512K
- Following RFID tags are known to be detected: iClass Clamshell, iClass GP, iCl
ass Px G8L.
- Following RFID tags currently do not work: DesFire D8H, 1430IL, iClass SEOS Px
JAH.
- Restarting PC causes yellow bang on both smartcard drivers. Disabling/enabling
the smartcard makes things work again. This issue is not observed on cold boot.
Other notes:
- GPIO code for detection of NFC module reads GPIO pins 0/1 which are shared wit
h the UART. Please disconnect the RX line if you have USH console connected for
proper detection of NFC
module.
- After installation the WriteDelayMS registry entry must be set to 50. To do so
, open regedit, and search for StartupSequence . It should take you to the registry
settings for the driver. Please
add two REG_DWORD values for UseSCR and Wr
iteDelayMs . To do this right click on the right hand pane and select New and DWOR
D (32-bit) value. Set UseSCR to 1 and WriteDelayMs to 50 (decimal)
- In certain cases, the 2079x firmware may not be properly updated by the NFC dr
iver. If a yellow bang on the driver is observed after installation, we need the
erase the NVRAM on the 2079x. Separate utility to erase 2079x NVRAM and instru
ctions will be provided..
- The WinPE folder now contains two new subfolders: "nfc" and "nfc_withtracing . T
he subfolder with tracing is for Broadcom internal use only.
- upgradeNFCfirmware.bat should be used to upgrade the NFC firmware to the lates
t version. "wipeNFCfirmware.bat" can be used to wipe the fw.
- The diagnostics commands "Set NFC Max Power" and "Read NFC UUID" should be u
sed from WinPE.
In Release 3.0.00012.30.7.006.0
===============================
Issues addressed:
JIRA (ESPSW-2718) [DCP3.0] CVHCI Can not be installed on Win8 and Win8.1
JIRA (ESPSW-2719) [DCP3.0] Two Drivers Display under Biometric Devices in
Win 7 Device Manager
JIRA (ESPSW-2711) [DCP3.0] FW can not Upgade under WinPE condition
- Known issues:
o FID cards. Only iclass RFID tags are supported. RFID 14443A/14443B tags
causes 2079x chip lockup.
o NFC cards. Mifare classic 320 byte T4T card tested successfully.
Topaz512 cards do not work and lockup the firmware.
o Restarting PC causes yellow bang on both smartcard drivers.
Disabling/enabling the smartcard drivers makes things work again. This
issues is not observed on cold-boot.
o Driver signature enforcement should be disabled before installation on
64-bit platforms otherwise installation will fail.
- Other notes:
o GPIO code for detection of NFC module reads GPIO pins 0/1 which are

shared with the UART. Please disconnect the RX line if you have USH
console connected for proper detection of NFC module.
o After installation the WriteDelayMS registry entry must be set to 50. To
do so, open regedit, and search for StartupSequence . It should take you
to the registry settings for the driver. Please add two REG_DWORD values
for UseSCR and
WriteDelayMs . To do this right click on the right
hand pane and select New and DWORD (32-bit) value.
o Set UseSCR to 1 and WriteDelayMs to 50 (decimal)
o In certain cases, the 2079x firmware may not be properly updated by the
NFC driver. If a yellow bang on the driver is observed after
installation, we need the erase the NVRAM on the 2079x. Separate utility
to erase 2079x NVRAM and instructions will be provided.
In Release 3.0.00002.30.7.001.0
===============================
- Firmware, Host Components:
- Added support for NFC factory diags to Windows ushdiag and WinPE ushdiag.