• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 16 subscribers
  • Views 318 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.

RF430FRL152H: problem reading temperature

Jens Tyslik
Intellectual 1610 points
Part Number: RF430FRL152H

Hi team, 

at one of my customers I received the following problem - can you please take a look at it?
Please let me know if anything is unclear or you need more information

thanks,
Jens 

In one of our devices we used the RF430FRL152H to measure the wireless temperature.

At the moment, a problem came in from the field, which I cannot explain.
Using the ISO/IEC 15693 standard we write a component ID to blocks 0x87 and 0x88 . The two blocks 0xAD and 0xEC are described with their fix. All four blocks are writable and readable.

For the problem the device has been transcoding block 0x87, even though we only read the sensor temperature and the data from the 0x87 and 0x88 blocks.

At the Start

Block 0x87:

0x01016C4B00000000

Block 0x88:

0x0000000000000000

Block 0xAD:

0xB24040A520013041

Block 0xEC:

0xCECED0FD0028CECE

 

After Transcoding:

Block 0x87:

0x0206FEEA00000000

Block 0x88:

0x0000000000000000

Block 0xAD:

0xB24040A520013041

Block 0xEC:

0xCECED0FD0028CECE

What happens at Block 0x87?

  • +1
    TI__Mastermind 22710 points

    Hi Jens,

    I don't get the point. Is the customer writing something to these blocks and is expecting to stay constant or is this the read-back location of the sensor temperature result and it is getting overwritten after a while?

    Which firmware is used? The ROM firmware or some customer firmware?

    If it is the ROM firmware then block 0x87 belongs to the Logging FRAM Memory location. This is the location where the sampling data is stored by the ROM firmware. If the customer places data here it might get overwritten with sampling data. If this is already sampling data, then it might get overwritten due to sensing was repeated but not finished before readout.

    Btw.: The ROM firmware functionality is described in the "RF430FRL15xH Firmware User's Guide (Rev. B)".

    Let me know if this can answer the question. If not then please provide more details on the firmware and the conditions before and after the issue.

    Best regards,

    Andreas.