Topic: problem PN533 NFC_DISCONNECT

hello everyone

I encounter a problem with libnfc.

I can not make a "nfc_disconnect" correctly.

Windows says the device is not recognized when I do a disconnect.

I then disconnect and reconnect every time I allow myself to PN533 APIs that I made.

someone an idea?

thank you

Re: problem PN533 NFC_DISCONNECT

GGelec wrote:

I encounter a problem with libnfc.

Please, add the required information : which OS version ? which libnfc version ? how to reporoduce your problem ? what happend, what is the attempted result ? etc.

Please be smart : think about "how other people can help me with this problem description ?" at the end of EACH post writing...

Romuald Conty

Re: problem PN533 NFC_DISCONNECT

rconty wrote:
GGelec wrote:

I encounter a problem with libnfc.

Please, add the required information : which OS version ? which libnfc version ? how to reporoduce your problem ? what happend, what is the attempted result ? etc.

Please be smart : think about "how other people can help me with this problem description ?" at the end of EACH post writing...

Hello

I work under Windows XP. with libnfc 1.3.3.

I worked with an example: NFCIP initiator:
.
.
.

abtRecv[szRecvBits] = 0;
  printf("Received: %s\n", abtRecv);

  nfc_initiator_deselect_tag(pnd);
  nfc_disconnect(pnd);                               <=== ??? problem
  return 0;
}

==============================================================

I am running the example without problem. I get out the "hello world" on my mobile.

If I try to restart the example, it does not work, Windows tells me: device not recognized.

I think it is a problem with the disconnect, but I'm not sure.

Anyway, I am forced to reset my NFC module to restart the NFCip-initiator example.

I hope it is detailed enough, feel free to ask me for more information.

Thank you very much.

GGelec

Re: problem PN533 NFC_DISCONNECT

GGelec wrote:

. with libnfc 1.3.3.

1.3.3 is deprecated, try with 1.3.4

GGelec wrote:

I work under Windows XP

Windows doesn't have a good libusb support, try the same using a working OS: Linux, FreeBSD, etc.

GGelec wrote:

I am running the example without problem. I get out the "hello world" on my mobile.
If I try to restart the example, it does not work, Windows tells me: device not recognized.

DONT trust Windows messages ! Turn on the libnfc debug mode...

GGelec wrote:

I think it is a problem with the disconnect, but I'm not sure.

How can you tell that's an nfc_disconnect() ? What are the arguments/evidences that point nfc_disconnect() ?

GGelec wrote:

Anyway, I am forced to reset my NFC module to restart the NFCip-initiator example.

How do you reset ?

Romuald Conty

Re: problem PN533 NFC_DISCONNECT

I designed an electronic circuit with a reset button.

When I establish communication with the NFC chip and I run an example (NFCIP-initiator), it works.

But when the example is complete, Windows removes the smart devices and signal to me that the device is not recognized.

So to use my PCB NFC I do a reset.
(Unplug / replug the USB connector or press the reset button)

There have disconnect or not. I do not know if that's the problem ...

I argue just the idea.

Re: problem PN533 NFC_DISCONNECT

cons for Linux I had the same problem but I solved this problem by enabling the administrator right on the Linux.

Under Windows, after calling the function disconnect the first transfer equipment is denied.

I'm looking ...

Re: problem PN533 NFC_DISCONNECT

I don't understand. Make it disconnect or fix it ???

Re: problem PN533 NFC_DISCONNECT

addniim wrote:

I don't understand. Make it disconnect or fix it ???

hum.

I'll try to explain my problem further.

in libnfc, there is a disconnect function.

If I run the example NFCIP-initiator, it works with my NFC controller.

But once the function disconnect runs, I do not just looped the example. For Windows, signal that the controller connected NFC is not a recognized device. So it just use it.

I am forced to disconnect and reconnect my controller (NFC on the same USB port) for windows recognizes it again.

I admit it's weird.