Errata
SLAZ540D – June 2013 – Revised January 2014
RF430CL330H Device Erratasheet
1
Silicon Revision D
See Section 4 for prior silicon revisions.
2
Device
Rev:
DID
RF_Lock
✓ The checkmark means that the issue is present in the specified revision.
RF430CL330H
D
✓
✓
Package Marking
PW14
TSSOP (PW), 14 Pin
CL330H
YMSG4
LLLL #
YM
S
LLLL
#
= Year and Month Date Code
= Assembly Site Code (Per QSS 005-120)
= Lot Trace Code
= Die Revision
= Pin 1
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
RF430CL330H Device Erratasheet
1
Detailed Bug Description
3
www.ti.com
Detailed Bug Description
DID
DID – Bug description
Description
RF430CL330H does not respond to PCD commands issued using a DID value other
than 0x00.
Workaround
PCD must issue commands with DID value of 0x00 or no DID present.
RF_Lock
RF_Lock – Bug description
Description
The RF430CL330H might become unresponsive in RF Enable Mode in a very small
percentage of RF interactions between the RF430CL330H and the reader.
Workaround
To ensure that this behavior does not happen in any case, an additional initialization
sequence needs to be added. The following code snippet shows this initialization
sequence.
This sequence has to be applied only once after every power-on and reset.
/****************************************************************************/
/* Errata Fix : Unresponsive RF - recommended firmware
*/
// Write_Register (address_16_bit, data_16_bit);
// data_16_bit Read_Register (address_16_bit);
/****************************************************************************/
{
//Please implement this fix as given in this block. It is important that
//no line be removed or changed.
unsigned int version;
version = Read_Register(VERSION_REG); // read the version register.
// The fix changes based on what version of the RF430
// is being used. Version C and D have the issue.
// Next versions are expected to have this issue corrected.
// Ver C = 0x0101, Ver D = 0x0201
if (version == 0x0101 || version == 0x0201)
{
// the issue exists in these two versions
Write_Register(0xFFE0, 0x004E);
Write_Register(0xFFFE, 0x0080);
if (version == 0x0101)
{ // Ver C
Write_Register(0x2a98, 0x0650);
}
else
{
// Ver D
Write_Register(0x2a6e, 0x0650);
}
Write_Register(0x2814, 0);
Write_Register(0xFFE0, 0);
}
//Upon exit of this block, the control register is set to 0x0
2
RF430CL330H Device Erratasheet
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
Prior Silicon Revisions
www.ti.com
4
Prior Silicon Revisions
4.1
Silicon Revision C
Device
Rev:
BIP-8
ATQB_1
ATQB_2
ATTRIB_1
ATTRIB_2
INV_CMD
RF_Lock
RFU_BLK
ATQB_3
LAYER4_2
✓ The checkmark means that the issue is present in the specified revision.
RF430CL330H
C
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
RF430CL330H Device Erratasheet
3
Prior Silicon Revisions
4.2
www.ti.com
Detailed Bug Description
BIP-8
BIP-8 - Bug description
Description
Addressing a device other than RF430CL330H on the same I2C bus results in incorrect
data returned when BIP-8 is enabled on a multi-device I2C system.
Workaround
BIP-8 must not be used on multi device I2C systems.
ATQB_1
ATQB_1 - Bug description
Description
NFC Forum specifies that tag must respond with '00' in bits 2 and 3 of the protocol_type
field, but RF430CL330H responds with '10'.
Figure 1. ATQB Response
Workaround
The ATQB response is hard coded and cannot be changed. A fix is scheduled for silicon
revision D.
ATQB_2
ATQB_2 - Bug description
Description
NFC Forum specifies that FWI (frame waiting time integer) must be between 0 and 8.
RF430CL330H responds with FWI of 10, which is allowed per ISO 14443-3.
Figure 2. ATQB Response
Workaround
4
The ATQB response is hard coded and cannot be changed. A fix is scheduled for silicon
revision D.
RF430CL330H Device Erratasheet
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
Prior Silicon Revisions
www.ti.com
ATTRIB_1
ATTRIB_1 – Bug description
Description
NFC Forum requires accepting a Higher Layer INF command with ATTRIB, but does not
require supporting its functionality (must respond to only the base message).
RF430CL330H does not respond to commands containing the Higher Layer INF field
included.
Figure 3. ATTRIB Command
Workaround
No workaround for revision C. A fix is scheduled for silicon revision D.
ATTRIB_2
ATTRIB_2 – Bug description
Description
NFC Forum specifies that the answer to ATTRIB must be '0h'. RF430CL330H responds
with '8h' to indicate the MBLI (maximum buffer length index).
Figure 4. Answer to ATTRIB
Workaround
The answer to ATTRIB is hard coded and cannot be changed. A fix is scheduled for
silicon revision D.
INV_CMD
INV_CMD – Bug description
Description
RF430CL330H responds to invalid ATTRIB commands. NFC Forum specifies that the
tag should not respond to invalid commands.
Invalid ATTRIB Commands:
1D + NFCID0 + '00 F8 01 00' (indicates 848kbps when 106kbps should be used)
1D + NFCID0 + '00 08 00 00' (indicates PICC not compliant to 14443-4)
1D + NFCID0 + '00 08 0F 00' (RFU bits must be set to '0' in PARAM3)
Workaround
No workaround available in revision C. A fix is scheduled for silicon revision D.
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
RF430CL330H Device Erratasheet
5
Prior Silicon Revisions
www.ti.com
RFU_BLK
RFU_BLK – Bug description
Description
RF430CL330H does not respond to I-, R-, and S-Block commands with RFU bits set.
NFC Forum specifies that the tag must ignore these bits and respond to the base
message.
Workaround
No workaround available in revision C. A fix is scheduled for silicon revision D.
ATQB_3
ATQB_3 – Bug description
Description
REQB command with b5 set (Extended SENSB_RES supported) is responded with
standard ATQB.
Workaround
No workaround available in revision C. A fix is scheduled for revision D.
LAYER4_2
LAYER4_2 – Bug description
Description
Upon receiving an unsupported C-APDU select command, RF430Cl330H responds with
a PCB byte and it’s PUPI. The response should be PCB byte and an error code.
Workaround
No workaround available in revision C. A fix is scheduled for revision D.
6
RF430CL330H Device Erratasheet
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
Document Revision History
www.ti.com
Document Revision History
Changes from C Revision (September 2013) to D Revision .......................................................................................... Page
•
•
•
•
•
Changed current silicon revision from C to D .........................................................................................
Updated bug list applicable to silicon revision D .....................................................................................
Added Section 2 ..........................................................................................................................
Added DID description ...................................................................................................................
Moved silicon revision C information and all bug descriptions that do not apply to silicon revision D to Section 4 .........
1
1
1
2
3
NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
SLAZ540D – June 2013 – Revised January 2014
Submit Documentation Feedback
Copyright © 2013–2014, Texas Instruments Incorporated
Revision History
7
IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other
changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest
issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and
complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s terms and conditions of sale
supplied at the time of order acknowledgment.
TI warrants performance of its components to the specifications applicable at the time of sale, in accordance with the warranty in TI’s terms
and conditions of sale of semiconductor products. Testing and other quality control techniques are used to the extent TI deems necessary
to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not necessarily
performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their products and
applications using TI components. To minimize the risks associated with Buyers’ products and applications, Buyers should provide
adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work right, or
other intellectual property right relating to any combination, machine, or process in which TI components or services are used. Information
published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or
endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property of the
third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration
and is accompanied by all associated warranties, conditions, limitations, and notices. TI is not responsible or liable for such altered
documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service
voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice.
TI is not responsible or liable for any such statements.
Buyer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or support
that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which
anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of failures that might cause
harm and take appropriate remedial actions. Buyer will fully indemnify TI and its representatives against any damages arising out of the use
of any TI components in safety-critical applications.
In some cases, TI components may be promoted specifically to facilitate safety-related applications. With such components, TI’s goal is to
help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and
requirements. Nonetheless, such components are subject to these terms.
No TI components are authorized for use in FDA Class III (or similar life-critical medical equipment) unless authorized officers of the parties
have executed a special agreement specifically governing such use.
Only those TI components which TI has specifically designated as military grade or “enhanced plastic” are designed and intended for use in
military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI components
which have not been so designated is solely at the Buyer's risk, and that Buyer is solely responsible for compliance with all legal and
regulatory requirements in connection with such use.
TI has specifically designated certain components as meeting ISO/TS16949 requirements, mainly for automotive use. In any case of use of
non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
Products
Applications
Audio
www.ti.com/audio
Automotive and Transportation
www.ti.com/automotive
Amplifiers
amplifier.ti.com
Communications and Telecom
www.ti.com/communications
Data Converters
dataconverter.ti.com
Computers and Peripherals
www.ti.com/computers
DLP® Products
www.dlp.com
Consumer Electronics
www.ti.com/consumer-apps
DSP
dsp.ti.com
Energy and Lighting
www.ti.com/energy
Clocks and Timers
www.ti.com/clocks
Industrial
www.ti.com/industrial
Interface
interface.ti.com
Medical
www.ti.com/medical
Logic
logic.ti.com
Security
www.ti.com/security
Power Mgmt
power.ti.com
Space, Avionics and Defense
www.ti.com/space-avionics-defense
Microcontrollers
microcontroller.ti.com
Video and Imaging
www.ti.com/video
RFID
www.ti-rfid.com
OMAP Applications Processors
www.ti.com/omap
TI E2E Community
e2e.ti.com
Wireless Connectivity
www.ti.com/wirelessconnectivity
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2014, Texas Instruments Incorporated
