• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 16 subscribers
  • Views 428 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.

RF-HDT-AJLC: The write lock of the specific memory block on RF-HDT-AJLC-G0

Nomo
Guru 16800 points
Part Number: RF-HDT-AJLC

Hello,

We have some queries for RF-HDT-AJLC-G0.

1.Do you know cases that malfunction occurs during a write sequence?

2.What operation does cause the lock of the specific memory area (in our case, block 16)?

Background is following.

On our customer's side, they've tried to write data into RF-HDT-AJLC-G0 in their custom RFID tag.
However, 0.9% (114/12320) tags fails to be written and they find block 16 of all RF-HDT-AJLC-G0 is locked.
We cannot find the root cause of the issue, so we want to know whether RF-HDT-AJLC-G0 has malfunctions.

Best Regards,
Nomo

  • 0
    TI__Mastermind 18265 points

    Hello Nomo,

    I am not aware of any fails like that regarding the RF-HDT-AJLC. I will check in addition with a colleague if he has more information and will come back to you the next days.

    Best regards,

    Helfried

  • 0 in reply to Helfried Vollbrecht
    TI__Mastermind 18265 points

    Hello Nomo,

    I have checked that, but we have no information about a fail like that. This product is running for a very long time without issues.

    Is this a problem that came up only with a specific wafer lot? Has the customer used these devices in the past without problems?

    Best regards,

    Helfried

  • 0 in reply to Helfried Vollbrecht
    Guru 16800 points

    Hello Helfried-san,

    Thank you for your support.
    And, we could understand that you don't have the information about a fail like that.

    This issue came up with several wafer lots.
    Also, they used these devices in the past without problems.

    So, there is a probability that there is a change which causes the issue in customer's side.
    We'll ask them that, and if I get more information about that, I'll make a new post.

    Best Regards,
    Nomo