Skip to content

Xerox write reset and remap [idea] #3315

@JeroenSteen

Description

@JeroenSteen

How can we proceed with Xerox writing of HF-chips? I shared a write trace earlier in Discord, and noticed:
different WUP's, write-commando and likely a write status.

0D 00 00 B3 39	ok	XEROX WUP1
5D 00 00 50 BA	ok	XEROX WUP1
0D 37 21 92 F2	ok	XEROX WUP1
5D 37 21 71 71	ok	XEROX WUP1
0D 00 00 B3 39	ok	XEROX WUP1
0D 37 21 92 F2	ok	XEROX WUP1
5D 37 21 71 71	ok	XEROX WUP1

Reader command: 0x31 - Write-commando
Full example: 02 31 80 FE 09 2F 46 03 00 E0 31 00 00 00 00 68 D0
Tag response: 02 00 F7 3C - Maybe write-status (ok or busy)
Only some tag responses doesn't make sense yet, like: F6, FF, 3C.

  • Can we use the WUP commands for when we want to write; Can different WUP commands influence the ATTRIB command?
  • Is the Reader command: 0x31 a standard "write" command for all Xerox HF chips?
  • Does the Tag response: 02 00 F7 3C universally mean "write-ok", and how can we implement that?
  • How could we combine a reset (erase) and remap (write new data, or example given partnumber and write corresponding metered/sold-pattern) operation? Should we use data templates or something else?

What I've tried:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions