• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 17 subscribers
  • Views 705 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Is there any encryption algorithm for rf430frl152?

erik lee2
Genius 3060 points
Other Parts Discussed in Thread: TRF7970A

hi

my customer wants to use the NFC to do the ID confirmation,  the host end will design in TRF7970A, the tag end will design in RF430FRL152,

TRF7970A reads the content in RF430FRL152 when the tag end approching, the question is that, customer don't want any other NFC device to read the content from their RF430FRL152, is there any encryption algorithm can bundle in RF430FRL152? or any good way to do that?

another question, does the RF430FRL152 have its own ID number inside? 

 

  • 0
    TI__Guru*** 135355 points
    Hi Erik,

    The RF430FRL15xH does not contain any built in encryption abilities. It also has limited memory size, only runs at 2MHz max speed, and does not include a multiplier, so it would be hard to do anything beyond very basic encryption (such as only using logic operations) within it.

    Off the top of my head the only idea I could think of would be to have some sort of external encryption handler such as an additional microcontroller to encrypt the data and then communicate with the FRL using the eUSCI interface.

    Yes, the RF430FRL15xH tags all some with a unique ID number. This number can be read with the Inventory command by any NFC reader.
  • 0
    Prodigy 30 points

    Hi Erik,

    does the RF430FRL152 need to understand the data it stores?

    If not, the host driving the TRF7970A may encrypt itself the data and write the encrypted data to the tag. Although this data is readable by anyone, no one will actually understand it.

    If yes, than you could use the FRAMAccessLimit register. You can prohibit reading the upper part of the FRAM, where you can store the data sensitive data. To actually read this data somehow, a developed user code can check for a byte pattern written to a specific block (or several bytes written to the same location after each other). If the pattern is correct, it copies the sensitive data to a block in 4-byte chunks.

    Best regards,

    Andras