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.

TRF7960 Evaluation Module ISO 15693 Host Commands

Other Parts Discussed in Thread: TRF7960, RF430FRL152H, TRF7970A

1.TRF7960 Evaluation Module ISO 15693 Host Commands slou312a 2.3.2 in accordance with the instructions issued command 0x21 write single block, the results can not be written, Response Codes []

2.TRF7960 Evaluation Module for me to do PCB circuit reference solu 202a

3.What would a message to [],

It is caused by board design problems, or other reasons.

  • Hello,

    If you are using Write Single Block with a TI Tag-It HF-I Transponder, please select the Option Flag as well.

    See datasheet for Pro tags: www.ti.com.cn/.../scbu009b.pdf - Page 12 Section 1.6 shows commands supported and which need the Option Flag - try again with Option Flag set for Write Single Block

    Also for reference, Plus tags have extra commands supported but also require Write Single Block to have Option Flag: www.ti.com/.../scbu004b.pdf (Page 13, Section 1.6)
  • TRF7970 EVM Operation Write Single Block when to FR430FRL152H EVM, the results can not be written

    13:58:39.911 --> 010F000304184221f2aaaaaaaa0000
    13:58:40.391 <-- Request mode.
    []

    I do not know why, who can help answer
  • Hello,

    For the RF430FRL152H EVM you will need to modify the EVM configuration.

    Please see the following posts for reference on how this is done on the TRF7970AEVM

    e2e.ti.com/.../1767003

    You should be able to do the same for the 60AEVM.
  • 1.FRAM ISO 8-Byte Blk 9-236 freeze in that position can do it? DATA will not be made any modifications?
    2.TRF7970A  EVM can do gymnastics instruction command freeze command is what ??

    Who can help answer my questions?

  • Yes, you can lock blocks 9-236 using the ISO15693 lock block command. This will prevent them from being changed over RF.
    However, if you are running a sampling process, these FRAM locations will be changed by the internal processor when it logs the SD14 conversion results.
  • Discover SPEC has no explanation can be found FRAM as any change or lock.

    What can be done at any location FRAM Lock??

    How to change the position of the processor can be locked inside their own external storage configuration data can not be modified???

    The main question was intended to let the phone APP program can use RF to the processor internal data store location, which is a dedicated store and read, will not affect the SD14 conversion results.

    Who can help me solve my problem?

  • GUI using TRF7970EVM to interface to RF430FRL15XH software read logging data, why so far only read FAC0 not Expand all it?

    There are ways DATA read it all?

    Who can help me solve my problem??

  • Please see response for this on this thread:
    e2e.ti.com/.../1907591
  • user4708850 said:

    Discover SPEC has no explanation can be found FRAM as any change or lock.

    What can be done at any location FRAM Lock??

    How to change the position of the processor can be locked inside their own external storage configuration data can not be modified???

    The main question was intended to let the phone APP program can use RF to the processor internal data store location, which is a dedicated store and read, will not affect the SD14 conversion results.

    In 8-byte block mode, the RF block locking follows the standard as defined in ISO/IEC 15693 standard.

    Once the block is locked it cannot be unlocked again from the RF interface.

    Even if a block is locked using RF, the memory that is locked can still be modified internally.  For example, if you lock block 9... and run a sampling process, the ROM firmware will update block 9 with the data from the conversion.

    If you need to use the FRAM memory, yes you need to make sure that your SD14 results, which will be logged starting at block 9 (with 8 byte block mode) do not eventually overrun your FRAM data.  The best way to protect your data farther in FRAM, is to use the "Logging Memory Size Register".  Setting it a value like 100 (or more), will prevent the ROM firmware from storing more that 100 samples.  You then could safely keep you needed data farther down in the FRAM memory.  

    If this threshold is exceeded, for example on the 101st conversion, the ROM firmware will not log the 101st conversion, terminate the remaining conversions and update the status register (State field) to indicate an error (status of 0x3).