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
Been playing around with a PN532 board from AliExpress, and it reads things just fine. But when I try to use it as a target, reading with a phone, with any of the included utils, it always ends up reading as FeliCa card with ID/etc 00.
Not sure if it's just because of how it's initialized in
Flipper Zero can actually read it, but on first try it causes the program on host to crash with "RF error" and ends up showing on flipper as multi-protocol card. Though manually reading it as FeliCa or type 4 tag works fine without anything weird happening. Showing both the zeroed out NFC-F info, and the emulated info.
I'm connecting to it via HSU, through a https://black-magic.org/ probe firmware running on an STM32F401, if that's of any help.
Is this the limitation of PN532, of HSU, a counterfeit or faulty chip, a faulty board, or what? I'm not even sure where to look for info...
Sadly debug mode of libnfc doesn't help as it does not show the response to TgInitAsTarget command.
The text was updated successfully, but these errors were encountered:
Been playing around with a PN532 board from AliExpress, and it reads things just fine. But when I try to use it as a target, reading with a phone, with any of the included utils, it always ends up reading as FeliCa card with ID/etc 00.
Not sure if it's just because of how it's initialized in
libnfc/libnfc/chips/pn53x.c
Line 2376 in 3379466
Flipper Zero can actually read it, but on first try it causes the program on host to crash with "RF error" and ends up showing on flipper as multi-protocol card. Though manually reading it as FeliCa or type 4 tag works fine without anything weird happening. Showing both the zeroed out NFC-F info, and the emulated info.
I'm connecting to it via HSU, through a https://black-magic.org/ probe firmware running on an STM32F401, if that's of any help.
Is this the limitation of PN532, of HSU, a counterfeit or faulty chip, a faulty board, or what? I'm not even sure where to look for info...
Sadly debug mode of libnfc doesn't help as it does not show the response to
TgInitAsTarget
command.The text was updated successfully, but these errors were encountered: