• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 17 subscribers
  • Views 1112 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.

TRF7970 inventory command

John Hite
Expert 1355 points

Other Parts Discussed in Thread: TRF7970A, DLP-7970ABP

In the TRF7970A data sheet (SLOS743K –AUGUST 2011–REVISED APRIL 2014) on page 40, Figure 6-22 mentions an inventory command as well as request flags and a mask. I don't see these listed in any tables. Are these specific to ISO15693?

I suppose the real question is what do I transmit to a 14443A tag to get it to spill its guts?

Thanks,

jh

  • 0
    TI__Guru* 91336 points
    John -
    the Inventory Command is specific to ISO15693.

    the commands needed for activation and selection of a ISO14443A tag are outlined in the ISO14443-3 standard, and depending on the type of tag, will either continue on using ISO14443-4 (commands and framework) & ISO7816-4 commands OR deviate completely from the standard after activation and selection and use card specific commands (i.e. NFC Type 2 tags or proprietary tags)

    which kind are you wanting to use? if you can tell me name brand, then i can give you specific details without boring you with details that apply to tags you don't have.
  • 0
    Expert 1355 points
    Hi Josh,

    Thanks for the post. Looks like we are using NPX Ntag203.

    BTW, where are you located. I spend a few months in the SC building in the last century (78) before moving to Lewisville with HARM.

    Thanks,
    jh

  • 0 in reply to John Hite
    TI__Guru* 91336 points

    cool -

    i used to load codes in HARMs before launching off of CV-62...i was in an E2 squadron, so I had KIK-13's...VAQ (EA-6B) guys did not, so i got to load the codes....then watch the video later...fun stuff and ancient history. :)

    anyway -

    NTAG 203 are using what i have in the attached as a primer (these are NFC Type 2 tags) and code base for -G2553 LP and DLP-7970ABP is attached, too

    6888.NFC Forum Type 2 Tag Platform Operations with TRF7970A_02_18_2014.pdf

    TRF7970ABP_Project_05_2015.zip

  • 0 in reply to Josh Wyatt
    TI__Guru* 91336 points
    and i am also working out of SC bldg, too.
  • 0
    Expert 1355 points
    Sounds like a blast. I started out as an EE working on the HARM CLC. I worked with the TIBSD guys doing the layout for the F18 board my boss, Craig Nash, was designing. As things started ramping up they figured out that they needed some test equipment. So they pulled everyone's resume and found out I fooled with microprocessors and assy language in college. Next thing I knew I was writing ATLAS OS for TI960s. Pretty much stayed in test equipment software except for a stint of material handling automation for the HARM factory. Took a buy out in 93. Now working for Chemring Detection Systems in Charlotte, NC as a software weenie.

    Thanks for the info. I will start looking into it. I finally got my PIC32 processor to talk to the NFC via SPI bus and thought I was almost home. Then I started looking at actually trying to make it read a tag. So maybe I am halfway home. Microchip's PIC32 processors are good hardware but their documentation is terrible, bits and pieces everywhere. I need to dust off my MSP430 Launchpad. I actually got one when they were $4.30.

    Thanks again,

    John

  • 0 in reply to Josh Wyatt
    Expert 1355 points
    I see you set register 9 to 01 which means Sys_clk is disabled. Is it only for external use?
  • 0 in reply to John Hite
    TI__Guru* 91336 points
    SYS_CLK is output which I would disable when not in use system (i.e. not using it to provide a clock source to the MCU) - just to be clean about it.
    in the case of the -G2553, it won't take in an HF clock anyway, so i just use internal DCO.

    the lower bits of that register control the MOD depth. For Type A should be 100%, so 0x01 is correct

    yet another thing we have in common - i am from Winston-Salem, so not too far from where you live now.