ushupgrade.txt Driver File Contents (CV_Setup_TJ9CD_A29_ZPE.exe)

**************************************************************************
*                                                                        *
*  Copyright (c) 2007-2009 Broadcom Corporation.                         *
*  This program contains proprietary and confidential information. All   *
*  rights reserved except as may be permitted by prior written consent.  *
*                                                                        *
**************************************************************************


                      Broadcom (R) Corporation
                           USHUPGRADE
             Windows Utility to Upgrade the ControlVault Firmware


                         RELEASE 2.2.2.24
                           (9/02/2010)

                         RELEASE NOTES



=======================================
Description
=======================================

This is a windows based utility that will upgrade the ControlVault firmware.


=======================================
Usage
=======================================

Refer to readme.txt for operating instructions.


=======================================
History
=======================================

ver   date          description
===============================================================================

2.2.2.24: 2010/09/01  * Removed Fingerprint configuration.

2.2.2.22: 2010/07/29  * Added Fingerprint configuration.

2.2.2.21: 2010/07/06  * Stop service "WbioSrvc" ("Windows Biometric Service").

2.2.2.20: 2010/06/28  * Set default chip type to 5882.

2.2.2.19: 2010/06/22  * Now check fwupgrdtool return code to determine if no TPM owner.
                        This will trigger a prompt to turn off TPM and try again.

2.2.2.18: 2010/06/21  * Added TPM fw upgrade check.  If current fw > 200, check for TPM ownership.
                        If no ownership, prompt to turn off TPM and try again.

2.2.2.17: 2010/06/11  * Added "Flash access error" message.

2.2.2.16: 2010/06/10  * Only use version build number to decide to display TPM ownership message.

2.2.2.15: 2010/06/04  * Display error message: "ERROR: TPM ownership is needed to update firmware."

2.2.2.14: 2010/05/28  * When display version (-ver) wait until press Enter to continue.

2.2.2.13: 2010/05/25  * Added -ver command to display cv version and write cv version in file (cv_version.txt).

2.2.2.12: 2009/12/03  * Now always display the current and desired firmware version.  If version not known display ???.
                      * Also kill Dell.ControlPoint and Dell_ControlPoint looks like task shows up differently on different OSs or releases.

2.2.2.11: 2009/10/27  * Was not stopping Dell_ControlPoint.exe, which kept restarting other task.
                      * Also check for CV Admin password just prior to loading PBA, incase started in SBI and didn't ask for CV Admin password.

2.2.2.10: 2009/10/23  * When load SBI, try 5880 first then 5882.

2.2.2.9: 2009/10/13   * Kill off BcmDeviceAndTaskStatusService last.  Since it can be restarted by other tasks.

2.2.2.8: 2009/10/08:  * Catch exception when accessing ushupgrade.log file.

2.2.2.7: 2009/10/06:  * Backed out changes for GNATS5245 (If 5882 and fail update (antihammering, etc) prompt to shutdown rather than restart).

2.2.2.6: 2009/10/05:  * GNATS5192 - If no CV Admin password, don't continue with update.
                      * GNATS5193 - Changed CV Admin password window text color to "windows text" color.
                      * GNATS5245 - If 5882 and fail update (antihammering, etc) prompt to shutdown rather than restart.
                      * When terminate tasks, say Stopped rather than Done.

2.2.2.5  2009/09/24:  * Check that all files necessary exist prior to starting upgrade.
                      * Changed ICON to default on ushcv*.exe and ushbip*.exe files
                      * Changed ICON to default on fwupgrdtool.exe

2.2.2.4  2009/09/17:  * Changes for managed mode:
                        1) If in managed mode: ask for CV Admin password.
                        2) Changed PBA Auth error message.
                        3) Added -cvp <password> command to enter CV Admin password.
                      * If 5882 then use rfiddfl2.bin as default rfid config file.
                      * Log which files are uploaded to USH.
                      * If 5880 and vR is 7 then dec to 6.

2.2.2.3  2009/09/11   * Changes for PBA Auth failure:
                        1) If get PBA Auth failure, Use Physical presence, clear CV Admin, set CV Admin, update PBA.
                        2) If we set CV Admin, then clear it.

2.2.2.2  2009/09/10:  * added -q cmdline parameter to run in silent mode

2.2.2.1  2009/09/02:  * Only inc vR when 5882 and vR==6.  Also kill ComputerManagementLauncher.

2.2.2.0  2009/08/20:  * Added support to load either pbaapp.bin(5880) or pbaapp2.bin(5882)

2.2.1.0  2009/07/23:  * Added support for 5882A0(CID0 & CIDFF) and 5882B0(CID0, CID1, CID7 and CIDFF)

2.2.0.1  2009/07/07:  * If clear cv_admin in PBA then set cv_admin prior to retrying PBA upload.

2.2.0.0  2009/07/06:  * Now use BIP Lib rather than CV Lib.  If fw returns Version error, set host cv version to 1.0.
                        Use new BIP auth flags for PBA load.

2.1.0.4  2009/05/28:  * When load SBI, if file does not exit try remaining files rather than exit.

2.1.0.3  2009/04/30:  * Fixed exit mechanism when called via command line.

2.1.0.2  2009/04/29:  Synched up to 2.1.0.2:
                    * Modified Broadcom/CV/USH text to Dell/ControlVault. Display current USH version and version loading. Log the rfid config file being loaded.
                    * Added error\return code check that was missed when ported RFID changes.
                    * Improved GUI.  No longer use system commands to terminate tasks.
                    * Now when looking for chip ID look for "USH_CHIPID:58800x00" rather than just "58800x00".

1.11.10 2009/03/16:  * Now configure RFID parameters after update PBA.

1.11.9 2009/03/11:  * Now when looking for chip ID look for "USH_CHIPID:58800x00" rather than just "58800x00".

1.11.8 2009/03/03   * Modified antihammering check, If Reset and FlashWrite counts not present no longer prompt user,
                      just continue.

1.11.7 2009/03/02   * Modified antihammering check. If Reset and FlashWrite counts not present in versions string,
                      prompt user to continue or exit.

1.11.6 2009/02/02   * Added support for CID FF.

1.11.5 2009/01/07   * Added logging into ushupgrade.log file.
                    * Adjusted some return codes.

1.11.4 2009/01/06   * Changed "reset" messages to "restart".
                    * Only retry CV BCM update once.
                    * TPM update: Reset to SBI after clear SCD.
                    * When waiting for ControlVault to come back, also check rtc for longer than normal command responses.
                    * Removed initial message about TPM updates.
                    * If BCM fails (only display AH message).

1.11.3 2008/12/31   * Added reset message when CV update completes OK, and changed return code to 1.

1.11.2 2008/12/30   * Retry PBA packet if fail.
                    * Added more error checks when TPM PBA fails.

1.11.1 2008/12/23   * If TPM upgrade generates auth failure, display appropriate message.
                    * If TPM upgrade fails SBI update, display message to try upgrade via CV and steps to disable TPM.

1.11  2008/12/23    * Modified ushupgrade to also be called via the command line.
                    * Now return error code.
                    * Only display message box if batchMode not enabled.
                    * Created KillTask API to kill task from a list.
                    * Get version number from app.rc.

1.10a 2008/12/19    * TPM upgrades: after reset, verify ControlVault comes back before continuing.
                      This requires updated fwupgrdtool.exe (/rsts command).
                    * When upgrade fails, display "Reset and Retry" message.
                    * Only show Exit button when fail update API.

1.10  2008/12/12    * Enabled firmware update via TPM.
                    * TPM: Now update SBI, SCD, SCD1 via TPM.
                    * TPM: Reset to ControlVault via TPM.
                    * TPM: Don't reset when update SCD, SCD1 or BCM

1.9e  2008/12/08    * Don't kill off the following processes\services:
                      Dell.UCM.exe, SMManager.exe & DCPButtonSvc.exe

1.9d  2008/12/07    * The tool was killing off following processes\services:
                      Dell.ControlPoint.exe  HostStorageService.exe  HostControlService.exe  bcmdeviceAndtaskStatusService.exe
                      Now also killing off the following processes\services:
                      DCPSysmgr.exe    TdmService.exe  Dell.UCM.exe      SecureUpgrade.exe
                      WavXDocMgr.exe   SMManager.exe   DCPSysMgrsvc.exe  DCPButtonSvc.exe

1.9c  2008/12/06    * After killing off the tasks, wait 3 seconds before verifying they are removed.
                    * If tasks are not removed, try one more time.
                    * Prior to issuing a reset, issue a cv_open and cv_close (to fix 0x0e error).

1.9b  2008/12/05    * If TPM enabled, do not update firmware.

1.9a  2008/12/05    * If fail flash SBI due to TPM, change ERROR to Warning.
                    * When ControlVault does not comeback from reset, show exit button.
                    * When press start button, kill off host and DCP tasks.
                    * Then verify that the host and DCP tasks are removed.
                      If any are still running display error and exit button.
                    * If get 0x100002 error, show dll mismatch error and show exit button.

1.9   2008/11/26    * When rescan hardware force waiting more.
                    * For Anti-hammering issue, change text from "reset system" to "power cycle system".
                    * Added logic to retry BCM if failed. Added more error checking on bcm update.
                    * Hide Cancel button when start upgrade.
                    * Check if hit anti-hammering on last reset, then say OK.
                    * Moved common strings into defines.

1.8   2008/11/21    * Fixed GUI, so always update GUI window (added background worker).
                    * If ControlVault does not comeback after reset, rescan hardware and wait somemore.
                    * If TPM enabled, update PBA and then use fwupgrdtool.exe to update BCM.
                    * Changed initial message to: "To fully update teh ControlVault firmware, the TPM should be deactivated."

1.7   2008/07/03    * If PBA download fails due to Auth Error, set admin to our, do PBA download then clear CV Admin.

1.6   2008/07/03    * No longer clear CV Objs when init CV Admin for PBA download.

1.5   2008/06/23    * Removed the logic to chagne cust ID.  Support A0, B0, C0 NONOTP, C0 CustID1, and C0 CustID7.

1.3   2008/06/04    * Mods for changing cust ID 1 to 3.

1.2   2008/05/22    * Change cust ID 1 to 3.

1.1   2008/05/21    * Improved reset logic wait to wait up to 15 seconds and poll
                      once a second to see if the device came back up.

1.0   2008/05/09    * Initial release


=======================================
Known issues:
=======================================

1)  During the update process, the ControlVault will reset several times.  When the ControlVault comes back up, it may
    renumerate with a different PID.  There must be a CV USB Driver associated with these PIDs.
    If there is no driver associated with the new PID, this utility will not detect the ControlVault starting
    back up and stop the upgrade process.  When there is no driver associated with the new PID,
    windows will indicate that it found new hardware (Credential Vault Device) and prompt you to
    install a driver for the device.  Select the existing Credential Vault Driver (cvusbdrv.sys)
    for the new hardware found.  Once the driver is loaded rerun this utility.
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 1.27