Thank you for your answer. I just received NXP Mifare Classic 1K Tags, they worked very well (detected by nfc-poll, nfc-list...), but I have to work on libfreefare before, and Android don't work with it.
What can I do for an antenna problem? I'm not really a boss in electronic , but I tried and independent supply without success (same result, others tags OK, but not NXP MIFARE Ultralight C Tags (NFC Forum Type 2)). I will ask it to the distributor.
I have this result when I apply this command line with the NXP MIFARE Ultralight C Tags (NFC Forum Type 2):
LIBNFC_LOG_LEVEL=3 nfc-list -t 1
info libnfc.config Unable to open file: /etc/nfc/libnfc.conf
debug libnfc.config key: [device.name], value: [PN532 board via UART]
debug libnfc.config key: [device.connstring], value: [pn532_uart:/dev/ttyAMA0]
debug libnfc.config key: [device.allow_intrusive_scan], value: [true]
info libnfc.config Unknown key in config line: device.allow_intrusive_scan = true
debug libnfc.general log_level is set to 3
debug libnfc.general allow_autoscan is set to true
debug libnfc.general allow_intrusive_scan is set to false
debug libnfc.general 1 device(s) defined by user
debug libnfc.general #0 name: "PN532 board via UART", connstring: "pn532_uart:/dev/ttyAMA0"
nfc-list uses libnfc 1.7.0
usage: nfc-list [-v]
-v verbose display
Here is the conf file for the PN532 board driver:
name = "PN532 board via UART"
connstring = pn532_uart:/dev/ttyAMA0
allow_intrusive_scan = true
For the tamashell command, no result at all :
NFC reader: pn532_uart:/dev/ttyAMA0 opened
Tx: 4a 01 00
I will maybe buy new NXP MIFARE Ultralight C Tags (NFC Forum Type 2), they were include on the box of my old Galaxy S2 (NFC version), maybe they are not respected standards.