java - "Time Out, the target has not answered"来自带有 Jewel/Topaz512 NFC 标签的 ACR122U 读卡器-6ren

java - "Time Out, the target has not answered"来自带有 Jewel/Topaz512 NFC 标签的 ACR122U 读卡器

转载作者：行者123 更新时间：2023-12-02 08:42:41

我正在构建一个 Windows/Java 程序(使用 javax.smartcardio)，以使用 ACR122U 设备(内部带有 PN532 NFC Controller 芯片)与 Jewel/Topaz512 标签(来自 Innovision/Broadcom)进行通信.

我实现了 Topaz512 协议(protocol)(来自 this data sheet )，但只有一半的命令有效。

一些有效的命令:RID、RALL、READ、WRITE-NE、RSEG
一些不起作用的命令:WRITE-E、READ8、WRITE-E8、WRITE-NE8

WRITE-NO-ERASE 命令示例

例如，以下是我发送 WRITE-NO-ERASE 命令时得到的结果:

命令:FF:00:00:00:0C:D4:40:01:1A:7F:42:38:01:9A:00:17:E8

地点:

D4:40:01 是 InDataExchange 命令，
1A:7F:42 是 WRITE-NO-ERASE 命令(值:0x42， block 0x0F，字节 7)，
38:01:9A:00 是 4 字节标签 UID，
17:E8 是 CRC。

响应:D5:41:00:42:90:00

这里的响应是正确的:0x42。状态字节 (0x00) 表明一切顺利。

WRITE-WITH-ERASE 命令示例

这是我发送 WRITE-WITH-ERASE 命令时得到的结果:

命令:FF:00:00:00:0C:D4:40:01:53:7F:42:38:01:9A:00:28:6E

地点:

D4:40:01 是 InDataExchange 命令，
53:7F:42 是 WRITE-WITH-ERASE 命令(值:0x42， block 0x0F，字节 7)，
38:01:9A:00 是 4 字节标签 UID，
28:6E 是 CRC。

响应:D5:41:01:90:00

此处，状态字节 (0x01) 通知 PN532 检测到超时。 (来自 the PN532 documentation (p67):“超时，目标尚未应答 - 0x01”)

此外，当我删除 PN532 超时(使用 FF:00:00:00:06:D4:32:02:00:00:00)时，非工作命令不会响应 D5:41:01:90:00，但等更长时间，然后我没有得到任何回应。

编辑2020-04-20

我只是尝试使用 gscriptor(来自 pcsc-tools 套件)执行命令，并且得到了相同的行为。这是我的结果:

脚本:

FF 00 00 00 06 D4 32 05 02 02 02

# SAMConfiguration
FF 00 00 00 04 D4 14 01 00

# SetParameters
FF 00 00 00 03 D4 12 04

# InListPassiveTarget: Jewel mode
FF 00 00 00 04 D4 4A 01 04

# InDataExchange: RID
FF 00 00 00 04 D4 40 01 78

# InDataExchange: RALL
FF 00 00 00 04 D4 40 01 00

# InDataExchange: RSEG 0-3
FF 00 00 00 05 D4 40 01 10 00
FF 00 00 00 05 D4 40 01 10 20
FF 00 00 00 05 D4 40 01 10 40
FF 00 00 00 05 D4 40 01 10 60

##########

# GetFirmwareVersion
FF 00 00 00 02 D4 02

# GetGeneralStatus
FF 00 00 00 02 D4 04

##########

# RFConfiguration: No timeout
FF 00 00 00 06 D4 32 02 00 00 00

# InDataExchange: READ-1
FF 00 00 00 05 D4 40 01 01 7F

# InDataExchange: READ-8
FF 00 00 00 05 D4 40 01 02 00

# InDataExchange: WRITE-E-1
FF 00 00 00 06 D4 40 01 53 7F 42

# InDataExchange: WRITE-E-8
FF 00 00 00 0C D4 40 01 55 02 01 02 03 04 05 06 07 08

# InDataExchange: WRITE-NE-1
FF 00 00 00 06 D4 40 01 1A 7F 42

# InDataExchange: WRITE-NE-8
FF 00 00 00 0C D4 40 01 1B 02 01 02 03 04 05 06 07 08

结果:


Sending: FF 00 00 00 06 D4 32 05 02 02 02
Received: D5 33 90 00
Normal processing.

Sending: FF 00 00 00 04 D4 14 01 00
Received: D5 15 90 00
Normal processing.

Sending: FF 00 00 00 03 D4 12 04
Received: D5 13 90 00
Normal processing.

Sending: FF 00 00 00 04 D4 4A 01 04
Received: D5 4B 01 01 0C 00 38 01 9A 00 90 00
Normal processing.

Sending: FF 00 00 00 04 D4 40 01 78
Received: D5 41 00 12 4C 38 01 9A 00 90 00
Normal processing.

Sending: FF 00 00 00 04 D4 40 01 00
Received: D5 41 00 12 4C 38 01 9A 00 00 10 25 00 00 10 3F
00 01 03 F2 30 33 02 03 F0 02 03 03 E3 D1 01 DF
54 02 65 6E 30 31 32 33 34 35 36 37 38 39 30 30
31 32 33 34 35 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 55 55 AA
AA 12 4C 06 00 01 E0 00 00 00 00 00 00 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 10 00
Received: D5 41 00 38 01 9A 00 00 10 25 00 00 10 3F 00 01
03 F2 30 33 02 03 F0 02 03 03 E3 D1 01 DF 54 02
65 6E 30 31 32 33 34 35 36 37 38 39 30 30 31 32
33 34 35 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 55 55 AA AA 12
4C 06 00 01 E0 00 00 00 00 00 00 00 00 00 00 00
00 00 47 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 10 20
Received: D5 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 10 40
Received: D5 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 10 60
Received: D5 41 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 90 00
Normal processing.

Sending: FF 00 00 00 02 D4 02
Received: D5 03 32 01 06 07 90 00
Normal processing.

Sending: FF 00 00 00 02 D4 04
Received: D5 05 01 00 01 01 00 00 02 80 90 00
Normal processing.

Sending: FF 00 00 00 06 D4 32 02 00 00 00
Received: D5 33 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 01 7F
Received: D5 41 00 47 90 00
Normal processing.

Sending: FF 00 00 00 05 D4 40 01 02 00
Received:
wrong SW size for:

Sending: FF 00 00 00 06 D4 40 01 53 7F 42
Received:
wrong SW size for:

Sending: FF 00 00 00 0C D4 40 01 55 02 01 02 03 04 05 06
07 08
Received:
wrong SW size for:

Sending: FF 00 00 00 06 D4 40 01 1A 7F 42
Received: D5 41 00 47 90 00
Normal processing.

Sending: FF 00 00 00 0C D4 40 01 1B 02 01 02 03 04 05 06
07 08
Received:
wrong SW size for:

Script was executed without error...

最佳答案

不久前，我对此进行了详细研究，得出的结论是，NXP 的 PN532 NFC Controller 芯片的固件存在问题，导致其无法成功地通过 NFC Forum Type 1 标签(Topaz/Jewel 品牌)收发一些命令。如前所述，ACR122U 基于该芯片。

当我尝试使用WRITE-E8 (0x54)命令一次写入8字节 block 时，收到的响应是0x01，等待标签超时回复。

我尝试过但不起作用的事情:

包括 InDataExchange 中的 UID 回显，我什至使用了 UID 回显的字节顺序，结果仍然相同。

使用 inCommunicateThru 命令而不是 InDataExchange 并在应用程序级别计算 CRC1 和 CRC2 值(相同的结果)

我得出的最终结论是:

PN532 无法写入 1 型标签上的 0x10 及更高页面，这使得无法写入 Topaz 512 等流行型号的全部内存范围。

建议:

这个问题与 2012 年相关，当时 Topaz 512 是一款出色的低成本但高内存的 NFC 标签。现在有了 NAG215 和 NTAG216 型号，我建议使用那些具有高内存和与 NFC 读卡器通用兼容性的型号。

关于java - "Time Out, the target has not answered"来自带有 Jewel/Topaz512 NFC 标签的 ACR122U 读卡器，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/61275660/

文章推荐： java - 需要正则表达式来删除多个换行符之间的空格

文章推荐： sql - 根据表列动态合并两个或多个列？

文章推荐： asp.net-mvc - Durandal KO 绑定(bind) View 问题

文章推荐： java - 了解如何设置 Cloud Firestore 数据库

Centos7.0安装ceph(JEWEL)及以上版本的实例解析
背景　　由于docker的Ceph插件rexray对Ceph版本有一定的要求，当Ceph版本为hammer (0.94.10)时，rexray无法成功创建rbd设备。CentOS 7及以上版本，
ruby - 将 Jeweler 的 gem 版本与程序本身的版本字符串同步
所以我正在使用 Jeweler维护 little gem of mine ，它提供了一组方便的 rake version:* 任务来管理版本号。 Jeweler 显然将版本号存储在名为 VERSION
ruby - Gemfile 中的 jeweler 和 gemspec 是否一起工作？
在我的 Gemfile 中使用 gemspec 并使用 jeweler 时遇到问题: sudo gem install pkg/revertible_paper_trail-0.3.0.gem Fet
facebook - "?fref=jewel"在 facebook 的 url 中是什么意思？
我在 facebook 中收到了几个链接以“?fref=jewel”结尾的配置文件的好友请求。所有链接在 url 中都有这个结束词。有些个人资料可能是假的。谁能告诉我“?fref=jewel”是什么意
ruby-on-rails - gem.add_dependency Jeweler 如何格式化 git 源代码？
我正在尝试在我的 Jeweler Rake 文件中指定一个 git 源: gem.add_dependency 'myapp', :git => "git@github.com:myaddres
ruby - 编写一个 Jeweler Rakefile，根据 RUBY_ENGINE(ruby 或 jruby)添加依赖项
我有一个包含以下内容的 Rakefile: Jeweler::Tasks.new do |gem| # ... gem.add_dependency('json') end 此生成的 gems
java - "Time Out, the target has not answered"来自带有 Jewel/Topaz512 NFC 标签的 ACR122U 读卡器
我正在构建一个 Windows/Java 程序(使用 javax.smartcardio)，以使用 ACR122U 设备(内部带有 PN532 NFC Controller 芯片)与 Jewel/To

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城