NTAG5 Link: Single SRAM Block Write Not Triggering I2C Master Read - Full SRAM Write Works

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NTAG5 Link: Single SRAM Block Write Not Triggering I2C Master Read - Full SRAM Write Works

Jump to solution
1,202 Views
kavya_ap
Contributor I

I'm implementing  pass-through application using NTAG5 Link (NTP53x2). The system writes small configuration data blocks to SRAM via NFC and reads them via I2C on an embedded MCU.

Current Findings:

  • Single SRAM block write: ED pin does not trigger because it's not the last byte of the 256-byte SRAM

  • Full SRAM write: Works reliably - ED pin triggers and I2C master can read the data

  • Workaround attempted: Configured ED pin with ED_CONFIG = 1100b (trigger on SYNCH_BLOCK write) and set the target data block as the SYNCH_DATA_BLOCK - still no result.

    Is there a configuration method in NTAG5 Link that allows the ED pin to reliably trigger on a single SRAM block write without requiring the entire SRAM to be written? If not, what is the recommended approach for efficient small-data transfers in pass-through mode?

 

0 Kudos
Reply
1 Solution
1,177 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello @kavya_ap

Hope you are doing well.

There may not be a direct implementation to trigger ED pin on single SRAM block write. As you mention, pass-through mode expects SRAM write from 00h to 3Fh in order to trigger ED pin, as depicted in NTAG 5 - Bidirectional data exchange, Figure 1.

For proper pass-through implementation, please stick to the procedures and recommendations described in NTAG 5 - Bidirectional data exchange.

Regards,
Eduardo.

View solution in original post

2 Replies
1,178 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello @kavya_ap

Hope you are doing well.

There may not be a direct implementation to trigger ED pin on single SRAM block write. As you mention, pass-through mode expects SRAM write from 00h to 3Fh in order to trigger ED pin, as depicted in NTAG 5 - Bidirectional data exchange, Figure 1.

For proper pass-through implementation, please stick to the procedures and recommendations described in NTAG 5 - Bidirectional data exchange.

Regards,
Eduardo.

1,106 Views
kavya_ap
Contributor I
Thank you so much.
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2247386%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ENTAG5%20Link%3A%20Single%20SRAM%20Block%20Write%20Not%20Triggering%20I2C%20Master%20Read%20-%20Full%20SRAM%20Write%20Works%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2247386%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%20class%3D%22%22%3E%3CSPAN%3EI'm%20implementing%26nbsp%3B%20pass-through%20application%20using%20NTAG5%20Link%20(NTP53x2).%20The%20system%20writes%20small%20configuration%20data%20blocks%20to%20SRAM%20via%20NFC%20and%20reads%20them%20via%20I2C%20on%20an%20embedded%20MCU.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22%22%3ECurrent%20Findings%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%20class%3D%22%22%3ESingle%20SRAM%20block%20write%3A%26nbsp%3BED%20pin%20does%20not%20trigger%20because%20it's%20not%20the%20last%20byte%20of%20the%20256-byte%20SRAM%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%20class%3D%22%22%3EFull%20SRAM%20write%3A%26nbsp%3BWorks%20reliably%20-%20ED%20pin%20triggers%20and%20I2C%20master%20can%20read%20the%20data%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%20class%3D%22%22%3EWorkaround%20attempted%3A%26nbsp%3BConfigured%20ED%20pin%20with%26nbsp%3BED_CONFIG%20%3D%201100b%20(trigger%20on%20SYNCH_BLOCK%20write)%20and%20set%20the%20target%20data%20block%20as%20the%20SYNCH_DATA_BLOCK%20-%26nbsp%3Bstill%20no%20result.%3C%2FP%3E%3CP%20class%3D%22%22%3EIs%20there%20a%20configuration%20method%20in%20NTAG5%20Link%20that%20allows%20the%20ED%20pin%20to%20reliably%20trigger%20on%20a%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Esingle%20SRAM%20block%20write%20without%20requiring%20the%20entire%20SRAM%20to%20be%20written%3F%20If%20not%2C%20what%20is%20the%20recommended%20approach%20for%20efficient%20small-data%20transfers%20in%20pass-through%20mode%3F%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2247791%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20NTAG5%20Link%3A%20Single%20SRAM%20Block%20Write%20Not%20Triggering%20I2C%20Master%20Read%20-%20Full%20SRAM%20Write%20Works%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2247791%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F257240%22%20target%3D%22_blank%22%3E%40kavya_ap%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EHope%20you%20are%20doing%20well.%3C%2FP%3E%0A%3CP%3EThere%20may%20not%20be%20a%20direct%20implementation%20to%20trigger%20ED%20pin%20on%20single%20SRAM%20block%20write.%20As%20you%20mention%2C%20pass-through%20mode%20expects%20SRAM%20write%20from%2000h%20to%203Fh%20in%20order%20to%20trigger%20ED%20pin%2C%20as%20depicted%20in%20%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fapplication-note%2FAN12364.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ENTAG%205%20-%20Bidirectional%20data%20exchange%3C%2FA%3E%2C%20Figure%201.%3C%2FP%3E%0A%3CP%3EFor%20proper%20pass-through%20implementation%2C%20please%20stick%20to%20the%20procedures%20and%20recommendations%20described%20in%20%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fapplication-note%2FAN12364.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ENTAG%205%20-%20Bidirectional%20data%20exchange%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3ERegards%2C%3CBR%20%2F%3EEduardo.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2253016%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20NTAG5%20Link%3A%20Single%20SRAM%20Block%20Write%20Not%20Triggering%20I2C%20Master%20Read%20-%20Full%20SRAM%20Write%20Works%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2253016%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EThank%20you%20so%20much.%3C%2FLINGO-BODY%3E