2.2 BSP Rel. 1.0 for PPMC-275 Programmer's Guide

List of APIs API Call Reference
OUTPUT Not Applicable
RETURNS Not Applicable
GLOBAL STATUS frcBibAttach(UINT32 handle )
The file that contains BIB information can be defined using the
The BIB description language section in the BIB specifications.
Then the definition file which has an extension .bib and the
frcBib.h file are provided as input to the mk_bib tool .The output
of which is fed along with the product specific information in the
SAP file to the upd_bib which gives the final bib image that should
be stored on the network.
The tool chain is as follows.
+ Tool Chain
file.bib, frcBIB.h -> mk_bib : rawBIB.x -> upd_bib :
finalBIB.x
^
BarCode -> SerialNum -> SAP : sap_info.dat ____|
The tools in detail
mk_bib : BIB Compiler, generates a "raw" BIB Srecord
file.
upd_bib : Updates the "raw" BIB with board-specific data
(from file "sap_info.dat") and recalculates the checksum.
Generates
a "final" BIB image (S-record file).
DESCRIPTION This routine must be called once to attach a handle to a BIB device,
usually an I 2 C-bus EEPROM (ID-ROM). The handle is used as a
unique identifier for the internal driver structures, and it is passed
to the interface routines bibReadIntfRtn() and bib-
WriteIntfRtn(), which are specified in the structure
BIB_INTF, referred by pIntf. As described in section "3.1 Data
Block Structure" of The Board Information Block (BIB) Version 2.0
document by Force Computers, more than one data block can be
stored in the same IDROM by building a linked list. The driver
searches this linked list of data blocks for a valid BIB image, verifies
its checksum and copies the BIB image into an internal memory
buffer. The routine returns ERROR in case of insufficient
memory, if the device cannot be read, no BIB is found, or the BIB
image is not valid.
INPUT The address of the EEPROM device that has to be attached.
5 - 112 VxWorks 5.5/Tornado 2.2 BSP Rel. 1.0 for PPMC-275