Skip to content

Update ex_14_Wait_For_NDEF_Write.md #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 15, 2022
Merged

Update ex_14_Wait_For_NDEF_Write.md #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions examples/docs/ex_14_Wait_For_NDEF_Write.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,8 @@ This prevents _most_ App confusion. You may still see occasions where the App th
a new RF transaction is attempted while the tag is already performing an I2C transaction (memory read). Once the RF read-modify-write is underway, the two second
timer prevents the next I2C transaction from interfering with it.

**It also helps a lot if you bring your phone near the tag first _and then_ press the "Write to Tag" button.** Bringing your phone near the tag generates a field.
The code then goes into its two second timeout and isn't accessing I2C when the RF write starts.
**It also helps a lot if you bring your phone near the tag first _and then_ press the "Write to Tag" button.** Bringing your phone near the tag generates a field
which causes the tag to go into RF mode early. This locks out I2C, ahead of you pushing the button to start the actual RF write.

## Writing an Empty NDEF Record

Expand Down