AnsweredAssumed Answered

How do I use the dynamic lock bytes on  OM5560 NT332E?

Question asked by Norman Wiedemeyer on May 20, 2020
Latest reply on May 22, 2020 by Ricardo Zamora

Hi guys,

 

I'm currently configuring my NXP I2C Tag 2k via arduino (I2C). As described in the documentation, I'm using the dynamic lock bytes to lock the pages after page 16. After setting the three first bytes from E0H (sector 1) to FF, Pages are "locked" (marked as ' * ') on the app, but I still can write and read them, from RF aswell as from I2c. Is there something I'm missing? I've also added a picture of the locked stage after setting the 3 Bytes in E0, E1, E2 to FF from sector 1. I also wondered what "rfui" (Byte 1, Bit 7-6) means. I have not found a description of those bits.

 

When locking with the static lock bytes, the symbol also changes to "+", which means "locked", instead of " * " from the dynamic lock bytes, which mean "locked and blocked". Whats the difference there? I've also added a screenshot from the NXP Scanning App, which analyzes the tag.

 

 

 

 

Thank you in advance!

 

Yours sincerly

Outcomes