• Menu
  • Product
  • Email
  • PDF
  • Order now
  • Frequently asked questions for RF430CL33xH devices

    • SLOA244B May   2017  – March 2019 RF430CL330H , RF430CL331H

       

  • CONTENTS
  • SEARCH
  • Frequently asked questions for RF430CL33xH devices
  1.   Frequently asked questions for RF430CL33xH devices
    1.     Trademarks
    2. 1 General Questions
      1. 1.1 What protocols do the RF430CL33xH devices support?
      2. 1.2 Are the RF430CL33xH devices NFC Forum compliant?
      3. 1.3 What is the NDEF message format?
      4. 1.4 What evaluation hardware should i get to evaluate the RF430CL33xH Devices?
        1. 1.4.1 RF430CL330H evaluation hardware
        2. 1.4.2 RF430CL331H evaluation hardware
      5. 1.5 What TI NFC reader/writer hardware and software is required to communicate with the RF430CL33xH?
      6. 1.6 How do i read data from the RF430CL33xH?
      7. 1.7 How do I format or change data that is stored on the RF430CL33xH?
    3. 2 Differences Between the RF430CL330H and RF430CL331H Devices
      1. 2.1 Size for over-the-air data transmission
      2. 2.2 Required microcontroller management
      3. 2.3 Serial communication options
      4. 2.4 Recommend applications
    4. 3 Hardware and Design Questions
      1. 3.1 Where can I get schematics and layout files for the RF430CL33xH?
      2. 3.2 How do I design and tune an antenna to 13.56 MHz for the RF430CL33xH devices?
      3. 3.3 What reference designs are available for the RF430CL33xH devices?
      4. 3.4 What memory technology do the RF430CL33xH devices use?
    5. 4 Software Questions
      1. 4.1 What software examples are available for the RF430CL33xH devices?
        1. 4.1.1 RF430CL330H firmware examples
        2. 4.1.2 RF430CL331H firmware examples
      2. 4.2 Is there a software example for Wi-Fi® pairing and handover?
      3. 4.3 Is there a software example for RTOS?
    6. 5 Miscellaneous Questions
      1. 5.1 Why does a passively powered RF430CL33xH device not work with Android phones, but it does work with TI NFC reader kits?
    7. 6 References
  2.   Revision History
  3. IMPORTANT NOTICE
search No matches found.
  • Full reading width
    • Full reading width
    • Comfortable reading width
    • Expanded reading width
  • Card for each section
  • Card with all content

 

APPLICATION NOTE

Frequently asked questions for RF430CL33xH devices

Frequently asked questions for RF430CL33xH devices

This guide contains a compilation of frequently asked questions concerning the RF430CL33xH series of devices. It serves as a central resource for anyone evaluating or designing with the RF430CL33xH devices. This guide includes links to recommended evaluation modules, reference designs, firmware examples, and other collateral that is relevant for the RF430CL33xH family.

Trademarks

BoosterPack, MSP430, LaunchPad are registered trademarks of Texas Instruments.

Bluetooth is a registered trademark of Bluetooth SIG.

Android is a registered trademark of Google Inc.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

All other trademarks are the property of their respective owners.

1 General Questions

1.1 What protocols do the RF430CL33xH devices support?

ISO/IEC 14443 Type B and NFC Forum Type 4B

1.2 Are the RF430CL33xH devices NFC Forum compliant?

Yes, the RF430CL33xH devices are designed to use NFC Forum standards, including the NDEF record standards.

1.3 What is the NDEF message format?

NFC tags use the NFC Data Exchange Format (NDEF) to store data within tags according to the NDEF standards. This allows any NFC-enabled devices to read the data from any NFC tag and interpret it. Most applications on NFC-enabled smartphones use NDEF when reading or writing data to NFC tags.

1.4 What evaluation hardware should i get to evaluate the RF430CL33xH Devices?

1.4.1 RF430CL330H evaluation hardware

The recommended hardware for evaluation is the Dynamic Dual Interface NFC Transponder BoosterPack™ Plug-in Module.

1.4.2 RF430CL331H evaluation hardware

No BoosterPack plug-in module with the RF430CL331H is available from TI as of this writing, but there are two methods to get the RF430CL331H on a BoosterPack plug-in module:

  • Purchase the RF430CL331H BoosterPack plug-in module by DLP Design Inc. from Digi-Key, part number DLP‑RF430CL331BP.
  • Purchase a Dynamic Dual Interface NFC Transponder BoosterPack Plug-in Module from the TI store, sample an RF430CL331H device, and replace the RF430CL330H device in the DLP-RF430BP with the RF430CL331H device. These devices are fully pin compatible, so no other changes need to be made.

1.5 What TI NFC reader/writer hardware and software is required to communicate with the RF430CL33xH?

Use the TI NFCLink Standalone software solution:

  • Purchase hardware in TI store.
  • Download firmware.
  • For details, see NFC/HF RFID Reader/Writer Using the TRF7970A.

1.6 How do i read data from the RF430CL33xH?

See TI example firmware projects in Section 4 and program the device with a firmware example that includes a predefined NDEF Text RTD message.

1.7 How do I format or change data that is stored on the RF430CL33xH?

TI example firmware projects contain examples of different NDEF record types. For a general reference that can be applied for the RF430CL33xH devices, see the NFCLink Standalone firmware for card emulation. The NFC card emulation using the TRF7970A application report includes a link to the firmware. The header file containing the NDEF record examples is located at [installed path]/nfclink/source/headers/ndef_image.h.

For technical details or information about message types not demonstrated in TI example firmware, see the following NFC Forum specifications: Type 4 Tag Operation, NFC Data Exchange Format (NDEF), and Record Type Definition (RTD) for details about how format the capability container and payload data per the NFC Forum standards.

2 Differences Between the RF430CL330H and RF430CL331H Devices

 

Texas Instruments

© Copyright 1995-2025 Texas Instruments Incorporated. All rights reserved.
Submit documentation feedback | IMPORTANT NOTICE | Trademarks | Privacy policy | Cookie policy | Terms of use | Terms of sale