I2C Registers: Difference between revisions
| Line 498: | Line 498: | ||
| 0x1 | | 0x1 | ||
| 0x1 | | 0x1 | ||
| | | Command source / destination. | ||
|- | |- | ||
| 0x2 | | 0x2 | ||
| Line 510: | Line 510: | ||
Following the above header is the payload data(when payload size is non-zero), with the size specified in the header. The command response payload is usually at least 1-byte, where that byte appears to be normally 0x0. For command requests the payload data is the command parameters. | Following the above header is the payload data(when payload size is non-zero), with the size specified in the header. The command response payload is usually at least 1-byte, where that byte appears to be normally 0x0. For command requests the payload data is the command parameters. | ||
For command requests sent to the NFC tag itself, Cmd[1]=0x0 and CmdID=0x0. The command request payload data here is the actual command request data for the NFC tag, starting with the CmdID u8 at payload+0. | |||
During NFC module startup, a certain command is sent to the controller which eventually(after various cmd-reply headers etc) returns the following the payload after the first byte in the payload: | During NFC module startup, a certain command is sent to the controller which eventually(after various cmd-reply headers etc) returns the following the payload after the first byte in the payload: | ||
| Line 518: | Line 520: | ||
Or that is: "Dec 22 201214:53:50<binary>20791B5". Therefore, this appears to return the part-number of the NFC controller(other command request(s) / response(s) use this part-number value too). | Or that is: "Dec 22 201214:53:50<binary>20791B5". Therefore, this appears to return the part-number of the NFC controller(other command request(s) / response(s) use this part-number value too). | ||
=== | === NFC controller commands === | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
! CmdRequest[1] | ! CmdRequest[1] | ||