Difference between revisions of "NFC:StartOtherTagScanning"
Jump to navigation
Jump to search
m |
|||
| Line 16: | Line 16: | ||
=Description= | =Description= | ||
| − | This can only be used when [[NFC:Initialize|initialized]] with type3. Only bitmask 0xF from unk1 is used, it's written into state then loaded later. That value is also compared with 1, depending on whether it matches different sets of data for 3 fields are loaded into state. | + | This can only be used when [[NFC:Initialize|initialized]] with type3. Only bitmask 0xF from unk1 is used, it's written into state then loaded later. That value is also compared with 1, depending on whether it matches different sets of data for 3 fields are loaded into state. [[NFC:StartTagScanning]] does this as well except it loads a value from state instead of from the cmdreq(where that state field is set to 0xF by [[NFC:Initialize]] with type2). |
| + | |||
| + | This is somewhat similar to [[NFC:StartTagScanning]]. | ||
Revision as of 00:35, 17 February 2017
Request
| Index Word | Description |
|---|---|
| 0 | Header code [0x001F0080] |
| 1 | u16 unk0 |
| 2 | u32 unk1 |
Response
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Result code |
Description
This can only be used when initialized with type3. Only bitmask 0xF from unk1 is used, it's written into state then loaded later. That value is also compared with 1, depending on whether it matches different sets of data for 3 fields are loaded into state. NFC:StartTagScanning does this as well except it loads a value from state instead of from the cmdreq(where that state field is set to 0xF by NFC:Initialize with type2).
This is somewhat similar to NFC:StartTagScanning.