Reference Manual Preliminary
Prox–DU & Prox–SU
www.gemalto.com Release for first samples Do not use for final design
DOC118569A Public Use Page 35/134
These parameters are used only for tuning purpose to communicate with an ISO14443-A
card.
RxThreshold, RFCfg, TypeB parameters are considered only when RF Parameters Use =
01h.
GsN, CWGsP and ModGsP parameters are considered only when RF Power Attenuation =
0Fh.
To configure these parameters refer to the MFRC523 contactless controller IC
documentation.
RF parameters for ISO14443-B cards
These parameters are used only for tuning purpose to communicate with an ISO14443-B
card.
RxThreshold, RFCfg, TypeB parameters are considered only when RF Parameters Use =
01h.
GsN, CWGsP and ModGsP parameters are considered only when RF Power Attenuation =
0Fh.
To configure these parameters refer to the MFRC523 contactless controller IC
documentation
EEPROM Parameters Validity
CRC control
This byte controls the EEPROM parameters validity:
MAD CRC algorithm is used to compute the CRC value from offset 0 to 64.
At startup, if the EEPROM parameters validity is not correct, all the parameters are set to
their default value.
That CRC should be updated at each modification into the EEPROM.
MAD CRC calculation program
The following lines are an example of MAD CRC calculation program:
/**************************************************************************
* Prototype : unsigned char ucMadCrc( unsigned char _uc_len,
* unsigned char *_puc_in,
* unsigned char *_puc_out );
* Description : This is the function to calculate the CRC
* If the last byte on input is the supposed CRC of the preceding bytes :
* the result will be 0 if this CRC is correct.
* Parameters :
* unsigned char _uc_len - number of bytes to compute CRC
* unsigned char *_puc_in - pointer to first byte
* unsigned char *_puc_out - pointer to store CRC computed
* Response :
* ERR_OK compute CRC is OK
* ERR_MAD_CRC compute CRC is not OK
* (last byte on input must be the supposed CRC of the preceding bytes)