• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 17 subscribers
  • Views 1805 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TRF7963A errata?

Andrew DeWeerd
Prodigy 100 points
Other Parts Discussed in Thread: TRF7963A, RF430CL330H, TRF7970A

Does this document, TRF7960A Firmware Design Hints, apply also to the TRF7963A?

I'm transmitting fine, but I'm having some odd behavior trying to clear interrupt flags (e.g., tx) and also some trouble reading anything from the FIFO after a packet has been received from an ISO14443B tag (I get an rx flag without any errors, but no data in buffer).  

If that doc does not apply, are there any errata for this part?

  • 0
    TI__Guru* 91086 points

    that doc does apply, however - i would be interested to know which Type B tags you are using, as a great deal of them being marketed are not ISO compliant and require special handling. If you want real Type B tag, you can use our RF430CL330H as a reference, or if you have an American ExpressPay on Blue (clear card), also a known good example.

    and if you want to share any of your settings and logic shots of what you are doing, that would go a long way in us helping you out.

     

  • 0 in reply to Josh Wyatt
    Prodigy 100 points

    I'm using Atmel CryptoRF tags.  They say they're compliant :)

    I'm digging in again today or tomorrow.  If I get equipment re-connected, I'll post screenshots.  At this point the hardware seems to be working correctly and I'm working out the firmware.  

    Thanks

  • 0 in reply to Andrew DeWeerd
    TI__Guru* 91086 points

    Andrew - 

    those tags are most certainly not compliant to ISO14443-3 or ISO14443-4

    they respond with an AFI of 0xFF, which is RFU according to the standard and the Protocol type bit indicating non-compliance with the standard. 

    In the cards i have, they give back PUPI of FFFFFFFF...which is pretty weird and not something i would expect, since there is no way to do any anti-collision arbitration on cards which have same ID #...

    i can also point you at their data sheet

    http://www.atmel.com/Images/Atmel-5276-CryptoRF-AT88SC0808CRF-1616CRF-3216CRF-6416CRF-AT88RF04C-Datasheet.pdf

    which shows them using a "density code" in place of # of applications byte 

    so - proceed at your own risk if you care to - if it was me i would look for a better vendor of tag silicon. 

    if you need security, there are other options.

  • 0 in reply to Josh Wyatt
    Prodigy 100 points

    Argh.  Thanks for the reply.

    I'm using them as a stopgap solution since the tags I want to use from Inside Secure are long lead.  Client needs tags now.  

    I'm on another project atm, but I'll jump back into this one tonight or tomorrow and see if it's fubar or I can work through it.  

  • 0 in reply to Andrew DeWeerd
    TI__Guru* 91086 points

    are you looking for contactless security card? 

    infineon, maxim and nxp all make decent alternatives to this cryptoRF

    or do you just need a contactless card which has some storage on it?

  • 0 in reply to Josh Wyatt
    Intellectual 320 points
    Hey Josh
    I'm using Citibank contactless debit card with MasterCard PayPass (14443-4 compliant) and I'm not able to communicate with it when using TRF7970A EVM and GUI. Do you have any document reference for the command sequence that can be used on the GUI environment. I tried to use standard command sequence defined by EMVco and/or ISO/IEC standards but with no success.
  • 0 in reply to Arian Papajani
    TI__Guru* 91086 points
    after you activate and select the card (could be Type A or Type B with M/C) - then it will be in ISO14443-4 / ISO7816-4 layer.
    then you can send the following and expect responses (doesn't matter the protocol type at this point) - this is just a portion which does not include any payment data, but will show you that you can interact with the cards in this layer, so i would recommend you sign up with M/C to get their spec. (this is the right way ==> )

    PaymentService Received PPSE Select:
    00A404000E325041592E5359532E444446303100

    Response:
    6F 23 84 0E 32 50 41 59 2E 53 59 53 2E 44 44 46
    30 31 A5 11 BF 0C 0E 61 0C 4F 07 A0 00 00 00 04
    10 10 87 01 01 90 00


    Payment Service Received MC-MSD Select:
    00A4040007A000000004101000

    Response:
    6F 17 84 07 A0 00 00 00 04 10 10 A5 0C 50 0A 4D
    61 73 74 65 72 43 61 72 64 90 00

    Payment Service Received GPO-MC:
    80 A8 00 00 02 83 00 00

    Response:
    77 0A 82 02 00 00 94 04 08 01 01 00 90 00

    Payment_Service_Received_Read_Record:
    00B2010C00

    Response:
    70 81 8E 9F 6C 02 00 01 56 3C 42 35 34 31 33 31
    32 33 34 35 36 37 38 34 38 30 38 5E 53 4D 49 54
    48 2F 4A 4F 48 4E 5E 30 35 30 38 31 30 31 33 33
    30 30 30 33 33 33 30 30 30 32 32 32 32 32 30 30
    30 31 31 31 31 30 9F 64 01 03 9F 62 06 00 00 00
    38 00 00 9F 63 06 00 00 00 00 E0 E0 9F 65 02 00
    0E 9F 66 02 0E 70 9F 6B 13 54 13 12 34 56 78 48
    08 D0 50 81 01 90 00 99 00 00 00 0F 9F 67 01 03
    9F 68 0E 00 00 00 00 00 00 00 00 5E 03 42 03 1F
    03 90 00
  • 0 in reply to Josh Wyatt
    Intellectual 320 points

    Josh,
    When I use Send tab to send the PPSE select command, for the 2PAY.SYS.DDF01, I get no response and When I use Send Raw tab the GUI is not responsive (freezes).
    Does GUI sends any specific (constant) bytes before the Select Command bytes?
    In your command frame I did not see the PCB ( Protocol Control Byte)

    P.S. Did you receive my email?

  • 0 in reply to Arian Papajani
    TI__Guru* 91086 points
    good point - i was using NFCLink on -F5529LP + TRF7970A BoosterPack - that setup + GUI adds PCB for you.

    if you are using EVM, you do need to add that (using test tab)

    i can look at making you a docklight script tomorrow if that would be useful for you
  • 0 in reply to Josh Wyatt
    Intellectual 320 points

    Josh,

    Indeed, that will be very useful to me since that my head is to be exploded after going thru all this EMV standards.

    My interest is concentrated on retrieving only the PAN (Application Primary Account Number) of the card for ATM Access Controll  purposes 

    So it can be very helpful if your script will provide a command sequence for retrieving (viewing) the PAN of the card.

    P.S. I'm still waiting for information on the amplifying circuit of the TRF7970A RF output

  • 0 in reply to Josh Wyatt
    Intellectual 320 points
    Any update on the "docklight script" ?