Query on Table 6. NTAG I2C plus 1k memory organization (I2C) BLOCK 38h

cancel
Showing results for 
Search instead for 
Did you mean: 

Query on Table 6. NTAG I2C plus 1k memory organization (I2C) BLOCK 38h

672 Views
gerrikoio
Contributor III

I am reading through the Product Data Sheet (Rev. 3.3 — 8 August 2018) for NT3H2111_2211 NTAG I2C plus NFC tag.

I am trying to make sense of Block 38h as shown in table 6 (page 20).

As you can see each block is organised into 16bytes and represented in the table as 4 rows with 4 bytes each, if any of the 16 bytes provide different characteristics. For example Block 0.

Now what is shown in the table for Block 38h only represents 12 bytes. What happened to the last 4 bytes, which would normally be represented as another row.

Could someone elaborate/clarify.

Thanks

Tags (1)
0 Kudos
4 Replies

577 Views
Jonathan_Iglesias
NXP TechSupport
NXP TechSupport

Dear Colin Gerrish,

 as you can see this is because in the 1K version the protected user memory is less so this address is  shorter, for example if you see the  2k version  you can see there is the 16 bytes.

1k

pastedImage_1.png

2k

pastedImage_4.png

BR

Jonathan

0 Kudos

577 Views
gerrikoio
Contributor III

Sorry, that does not make sense.

If you look at 1k from NFC perspective, you get:

pastedImage_1.png

And here is 2k from NFC perspective:

pastedImage_2.png

The exact same.

Because what you are saying is that only in I2C is block 56 12 bytes long for 1k while for 2k block 56 is 16 bytes long.

0 Kudos

577 Views
Jonathan_Iglesias
NXP TechSupport
NXP TechSupport

my apologies for my miss understanding, Yes you are correct I think this is an error in the Datasheet I am sending this to the product owner to be analyzed and if this is a mistake  this will be fixed in the next release of the datasheet. since the blocks have to be 16 bytes. 

BR

Jonathan

507 Views
PhilPhixed
Contributor II

Hi,

the same picture is found in the "Rev. 3.5 — 7 May 2019"

So was it an error in the Datasheet?

I'm asking because i have problems to get the password protection to work.

Is the AUTH0 the Byte 15 at address 38h from the i2c perspective?

Thanks

Phil

0 Kudos