BlueCore Utilities in BlueSuite
bc01-an-100Pd
© Copyright Cambridge Silicon Radio Limited 2001-2004
This material is subject to CSR’s non-disclosure agreement.
Page 13 of 33
_äìÉ`çêÉ
™
Casira User
Guide
5.1.2 BlueFlash
Firmware
Refer to section 4.5, Back Up New Casira Units, and section 6.2, Install the Latest Tools, for the steps to upload
and download BlueCore firmware.
There are four possible components in a firmware file:
Stack
: This is the main runtime code for BlueCore. There are two versions of stack, one contains all
stack layers up to HCI, plus an HCI version of the Virtual Machine (VM); the other contains stack layers
up to HCI, plus L2CAP, RFCOMM, SDP and the Virtual Machine (an RFCOMM version). Both stack
versions uses both program and data space.
DFU
Driver
: Device Firmware Upgrade allows for updating the stack, Persistent Store and VM
application over the HCI transport. You cannot use a DFU operation to upgrade the DFU driver.
Persistent
Store
: The Persistent Store holds all the setup and calibration information for BlueCore.
Most settings are design-specific, but some are module specific. The Persistent Store resides entirely in
the data space.
Virtual
Machine
Application
: BlueCore allows small applications to be run on-chip using CSR’s
BlueLab. These applications reside in a special area of the data space. Refer to section 7, Other
Applications, or to the CSR support website for more information about BlueLab.
BlueFlash firmware is held in *.xpv files (which correspond to the program space) and *.xdv files (which
correspond to the data space). There is a single *.dfu file for DFU. Not all files contain all firmware components.
Downloading a firmware file only to flash memory overwrites the components contained in the file; all others
remain intact. This affects only the calibration information in the Persistent Store. Downloading to flash memory
ensures that you can return the module to a known calibrated state if the Persistent Store becomes corrupted
beyond repair.
If firmware with no Persistent Store component is downloaded onto a blank flash, the stack code will create a
new Persistent Store using default values suitable for use on a Casira module. However, some keys will require
calibration per module for optimal performance.
For more information, refer to CSR documentation on PS Key Settings.
The
Verify
function compares the contents of a firmware file to the contents of flash memory and reports any
differences (comparing only components contained in the file).
5.1.3 Troubleshooting BlueFlash
Problem:
BlueFlash cannot identify flash type
BlueFlash fails to stop processor
BlueFlash times out trying to make a connection to BlueCore
Solution:
Ensure that the following actions have been completed:
Run InstParSpi.bat (
C:\Program Files\CSR\BlueSuite
) to copy and register the parspi.sys device driver.
You need administrative rights to install the device driver on a Windows NT or Windows 2000 system. Reboot
your PC.
Ensure that the driver has been installed in the registry by looking for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Parspi.
Ensure that the SPI cable is correctly connected.
