topic Re: NT3H2111 Can't write capability container in Other NXP Products

NT3H2111 Can't write capability container

Frzn_Solid — Wed, 19 Jun 2024 18:12:46 GMT

I'm using an NT3H2111 IC interfacing with a nRF52840 MCU. I'm trying to talk to the NT3H2111 via I2C. I'm able to read EEPROM just fine, but am unable to set the capability container of the EEPROM. My issue is very similar to this post that was never solved. I am able to read the entirety of sector 0. Here's the logic analyzer output to prove it. I realize that it shows the slave address as 0x00, this is another issue I'm having where changing the slave address doesn't seem to carry over through power cycles. I have no idea how to set it back to the default (0x55) and make it stick.

Regarding the main issue, if I later try to write an updated CC to sector 0, I am able to get an ACK for the slave address, an ACK for the MEMA, but the first data byte is NACK'd and therefore it is not updated. I've checked the static lock bytes and everything is unlocked. I've checked the dynamic lock bytes and everything is unlocked. I've checked the configuration registers and everything is 0x00. I've checked the session registers and every byte is 0x00 except for byte 6, which is 0x04. This corresponds to How do I fix this?

Re: NT3H2111 Can't write capability container

Fabian_R — Thu, 20 Jun 2024 21:43:15 GMT

Hello sir,

Thank you very much for using our products.

Is it possible that you have changed the NTAG I2C configuration registers?

As mentioned in section 8.3.8 it is possible that the address was changed when changing CC. I believe that this issue is linked to the problem of the slave address being changed to 0x00.

Could you please also share a screenshot of the full memory from the NFC perspective using TagInfo please?

This will help us get a better understanding of the memory configuration.

Re: NT3H2111 Can't write capability container

Frzn_Solid — Thu, 27 Jun 2024 13:46:27 GMT

Hello Fabian,

I don't believe it's possible to have changed the NTAG I2C configuration registers. What I did find was that my writes were causing EEPROM_WR_ERR to be set to 1b, meaning a HV voltage error during EEPROM write or erase cycle. I'm pretty sure that this is a hardware issue I haven't debugged yet, as other boards that I have work without this issue.

I'm unable to use the NFC TagInfo as it fails to recognize my NFC device

Re: NT3H2111 Can't write capability container

Fabian_R — Thu, 27 Jun 2024 20:03:46 GMT

Hello sir,

I understand, there is another app called TagWriter you should be able to format the ntag into an NDEF.

In the main screen go to Erase -> Erase and format it to NDEF.

If the NFC interface isn't disabled or any other configuration that could lock the interface, you may be able to reformat your tag and, use it as intended.