ACR122U-A9 Read Issues on Chrome OS

Question

ACR122U-A9 Read Issues on Chrome OS

yurikoex opened this issue 8 years ago · comments

Write seems to work. here is the example of the write:
chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1891 18:15:29.120 >6B050000000000000000FF0041FF00
chrome-nfc.js:1843 18:15:29.164 <830200000000000081009000
chrome-nfc.js:1891 18:15:29.183 >6B090000000000000000FF00000004D44A0100
chrome-nfc.js:1843 18:15:29.228 <83110000000000008100D54B01010044000704F1D32A9433809000
chrome-nfc.js:1033 DEBUG: InListPassiveTarget SENS_REQ(ATQA)=0x44, SEL_RES(SAK)=0x0
chrome-nfc.js:1036 DEBUG: tag_id: 04F1D32A943380
chrome-nfc.js:1038 DEBUG: found Mifare Ultralight (106k type A)
chrome-nfc.js:610 [DEBUG] nfc.wait_for_passive_target: tt2 with ID: 04F1D32A943380
chrome-nfc.js:1891 18:15:29.251 >6B0E0000000000000000FF00000009D44001A203E1100600
chrome-nfc.js:1843 18:15:29.270 <83050000000000008100D541009000
chrome-nfc.js:1891 18:15:29.277 >6B0E0000000000000000FF00000009D44001A204030BD101
chrome-nfc.js:1843 18:15:29.298 <83050000000000008100D541009000
chrome-nfc.js:1891 18:15:29.306 >6B0E0000000000000000FF00000009D44001A20507540265
chrome-nfc.js:1843 18:15:29.329 <83050000000000008100D541009000
chrome-nfc.js:1891 18:15:29.336 >6B0E0000000000000000FF00000009D44001A2066E746573
chrome-nfc.js:1843 18:15:29.360 <83050000000000008100D541009000
chrome-nfc.js:1891 18:15:29.366 >6B0E0000000000000000FF00000009D44001A20774FE0000
chrome-nfc.js:1843 18:15:29.394 <83050000000000008100D541009000

Version 47.0.2526.110 (64-bit)
Platform 7520.67.0 (Official Build) stable-channel squawks
Firmware Google_Squawks.5216.152.28

Read looks like this:
chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1891 17:56:09.887 >6B050000000000000000FF0041FF00
chrome-nfc.js:1843 17:56:09.924 <830200000000000081009000
chrome-nfc.js:1891 17:56:09.931 >6B090000000000000000FF00000004D44A0100
chrome-nfc.js:1843 17:56:09.975 <83110000000000008100D54B01010044000704C7D32A9433809000
chrome-nfc.js:1033 DEBUG: InListPassiveTarget SENS_REQ(ATQA)=0x44, SEL_RES(SAK)=0x0
chrome-nfc.js:1036 DEBUG: tag_id: 04C7D32A943380
chrome-nfc.js:1038 DEBUG: found Mifare Ultralight (106k type A)
chrome-nfc.js:610 [DEBUG] nfc.wait_for_passive_target: tt2 with ID: 04C7D32A943380
chrome-nfc.js:1891 17:56:09.995 >6B0A0000000000000000FF00000005D440013000
chrome-nfc.js:1843 17:56:10.012 <83150000000000008100D5410004C7D3982A9433800D480000E11016009000
chrome-nfc.js:1665 [DEBUG] poll_n: 11
chrome-nfc.js:1891 17:56:10.020 >6B0A0000000000000000FF00000005D440013004
chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1843 17:56:10.049 <83150000000000008100D54100030BD101075402656E74657374FE00009000
chrome-nfc.js:1891 17:56:10.065 >6B050000000000000000FF0041FF00
chrome-nfc.js:1891 17:56:10.075 >6B090000000000000000FF00000004D44A0100
chrome-nfc.js:1843 17:56:10.085 <830200000000000081009000
chrome-nfc.js:610 [DEBUG] nfc.wait_for_passive_target: [object ArrayBuffer] with ID:
chrome-nfc.js:1843 17:56:10.128 <83110000000000008100D54B01010044000704C7D32A9433809000
chrome-nfc.js:966 17:56:13.028 [1000001] timeout!

Joshua Lunsford · Answer 1 · Sun Jan 24 2016 07:17:32 GMT+0800 (China Standard Time)

Also, with a whiztag it doesn't read or write.

read:
chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1891 18:06:08.146 >6B050000000000000000FF0041FF00
chrome-nfc.js:1843 18:06:08.168 <830200000000000081009000
chrome-nfc.js:1891 18:06:08.171 >6B090000000000000000FF00000004D44A0100
chrome-nfc.js:610 [DEBUG] nfc.wait_for_passive_target: [object ArrayBuffer] with ID:
chrome-nfc.js:1843 18:06:08.209 <83050000000000008100D54B009000

write:
chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1891 18:12:14.152 >6B050000000000000000FF0041FF00
chrome-nfc.js:1843 18:12:14.195 <830200000000000081009000
chrome-nfc.js:1891 18:12:14.202 >6B090000000000000000FF00000004D44A0100
chrome-nfc.js:610 [DEBUG] nfc.wait_for_passive_target: [object ArrayBuffer] with ID:
chrome-nfc.js:1843 18:12:14.236 <83050000000000008100D54B009000

chrome-nfc.js:1232 [DEBUG] acr122_set_timeout(round up to 1275 secs)
chrome-nfc.js:1891 18:13:24.525 >6B050000000000000000FF0041FF00
chrome-nfc.js:1843 18:13:24.551 <830200000000000081009000
chrome-nfc.js:1055 DEBUG: found 0 target, tg=144
chrome-nfc.js:966 18:13:25.538 [1000001] timeout!