Blocking occurs when nfc-emulate using ACR122 device

Roverok / libnfc

Automatically exported from code.google.com/p/libnfc

GNU Lesser General Public License v3.0

0 stars 0 forks source link

Blocking occurs when nfc-emulate using ACR122 device #55

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Plug ACR122 device
2. Ensure that works fine using nfc-list
3. Launch nfc-emulate
4. Ctrl+C once should kill program but doesn't

acr122_tranceive is an blocking function (it use PC/SC SCardTransmit).

Original issue reported on code.google.com by romu...@libnfc.org on 15 Jan 2010 at 1:10

GoogleCodeExporter commented 9 years ago

Original comment by romu...@libnfc.org on 19 Aug 2010 at 2:44

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter commented 9 years ago

To emulate a target we use an PN53x blocking function. Usually, a PN53x command 
can be cancelled using a dedicated frame but in this case we couldn't reach 
PN53x while another command is running.
As conclusion, we can say that with ACR122 devices the emulation will not be 
rock-solid.
See Issue 117 for more technical information.

Original comment by romu...@libnfc.org on 6 Oct 2010 at 8:32

Changed state: WontFix