You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since commit nfc-tools/libnfc@ddde2dd, any baud rate other than 106 leads to an explicit baud rate change request. In mifare_desfire.c, the baud rate is fixed to 424:
if (nfc_initiator_select_passive_target(tag->device, modulation, tag->info.nti.nai.abtUid, tag->info.nti.nai.szUidLen, &pnti) >= 0) {
In the case of Android HCE, changing the baud rate is not necessarily supported, thus resulting in error code 01 (Timeout) which aborts the operation. Is it possible to infer the baud rate by the passed FreefareTag instead of setting it to the fixed value 424, or make it configurable somehow?
Since commit nfc-tools/libnfc@ddde2dd, any baud rate other than 106 leads to an explicit baud rate change request. In
mifare_desfire.c
, the baud rate is fixed to 424:libfreefare/libfreefare/mifare_desfire.c
Lines 287 to 297 in 5459806
In the case of Android HCE, changing the baud rate is not necessarily supported, thus resulting in error code
01 (Timeout)
which aborts the operation. Is it possible to infer the baud rate by the passed FreefareTag instead of setting it to the fixed value 424, or make it configurable somehow?The text was updated successfully, but these errors were encountered: