Since commit nfc-tools/libnfc@ddde2dd8f2749e2c2a9302f60e9dd747f0da46e9, 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:
https://github.com/nfc-tools/libfreefare/blob/5459806659d5f6aa0e7705b88c48775ea6c861a6/libfreefare/mifare_desfire.c#L287-L297
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@ddde2dd8f2749e2c2a9302f60e9dd747f0da46e9, 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: https://github.com/nfc-tools/libfreefare/blob/5459806659d5f6aa0e7705b88c48775ea6c861a6/libfreefare/mifare_desfire.c#L287-L297 In the case of Android HCE, changing the baud rate is not necessarily supported, thus resulting in error code01 (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?