Some T5577 help please

I’ve been following this guide to get started with T5577 before getting my implant done.

I have a KSEC T5577 Emulator card but the lf t55xx detect command doesn’t work.

Please see my efforts below.

When trying to write and read I’m not seeing the results expected in the guide.

Please can somebody point me in the right direction direction?

[usb] pm3 → lf t55xx detect
[!] :warning: command execution time out
[!] :warning: command execution time out
[!] :warning: command execution time out
[!] :warning: command execution time out
[!] :warning: Could not detect modulation automatically. Try setting it manually with ‘lf t55xx config’

[usb] pm3 → lf t55xx dump

[+] Page 0
[+] blk | hex data | binary | ascii
[+] ----±---------±---------------------------------±------
[+] 00 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 01 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 02 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 03 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 04 | 80000000 | .0000000000000000000000000000000 | …
[+] 05 | 80000000 | .0000000000000000000000000000000 | …
[+] 06 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 07 | FFFFFFFF | .1111111111111111111111111111111 | …

[+] Page 1
[+] blk | hex data | binary | ascii
[+] ----±---------±---------------------------------±------
[+] 00 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 01 | 80000000 | .0000000000000000000000000000000 | …
[+] 02 | FFFFFFFF | .1111111111111111111111111111111 | …
[+] 03 | 80000000 | .0000000000000000000000000000000 | …
[+] saved to json file /Users/ashscott/lf-t55xx-dump.json
[+] saved 12 blocks to text file /Users/ashscott/lf-t55xx-dump.eml
[+] saved 48 bytes to binary file /Users/ashscott/lf-t55xx-dump.bin
[usb] pm3 → lf t55xx read -b 1

[+] Page 0
[+] blk | hex data | binary | ascii
[+] ----±---------±---------------------------------±------
[+] 01 | 80000000 | .0000000000000000000000000000000 | …
[usb] pm3 → lf t55xx write -b 1 -d 12345678
[=] Writing page 0 block: 01 data: 0x12345678
[usb] pm3 → lf t55xx read -b 1

[+] Page 0
[+] blk | hex data | binary | ascii
[+] ----±---------±---------------------------------±------
[+] 01 | 80000000 | .0000000000000000000000000000000 | …
[usb] pm3 → lf t55xx read -b 1

[+] Page 0
[+] blk | hex data | binary | ascii
[+] ----±---------±---------------------------------±------
[+] 01 | FFFFFFFF | .1111111111111111111111111111111 | …
[usb] pm3

Command timeout would seem to indicate a mismatch between firmware and client.

When you first start the PM3 client It outputs this information. Post that please :slight_smile:

Thanks, Amal. I reckon it’s 15 years since we last communicated. Things have come a long way since then!.

Is this what you want?

  8888888b.  888b     d888  .d8888b.   
  888   Y88b 8888b   d8888 d88P  Y88b  
  888    888 88888b.d88888      .d88P  
  888   d88P 888Y88888P888     8888"  
  8888888P"  888 Y888P 888      "Y8b.  
  888        888  Y8P  888 888    888  
  888        888   "   888 Y88b  d88P 
  888        888       888  "Y8888P"    [ ☕ ]

Release v4.17140 - Raccoon
  [ Proxmark3 RFID instrument ]

    MCU....... AT91SAM7S512 Rev B
    Memory.... 512 KB ( 67% used )

    Client.... Iceman/master/v4.17140 2023-09-09 11:00:00
    Bootrom... Iceman/master/v4.17140-suspect 2023-09-09 11:00:00 
    OS........ Iceman/master/v4.17140-suspect 2023-09-09 11:00:00 
    Target.... device / fw mismatch

[usb] pm3 --> lf t55xx detect
[!] ⚠️  command execution time out
[!] ⚠️  command execution time out
[!] ⚠️  command execution time out
[!] ⚠️  command execution time out

Screenshot from 2023-09-30 02-21-39

Yeah, looks like you have a firmware mismatch. I haven’t seen it say “suspect” before…that’s a little…dare I say suspect? O.o
I’m a little more than exhausted, so grain of salt, but I’d recommend pulling the latest from github and reflashing.

Thank you.

Please could you point me to a set of instructions to follow for doing this?

Go into the ProxSpace environment, then run cd proxmark to change directory to where the proxmark files should be located, then git pull to pull the latest release, then make clean && make all to compile, ./pm3-flash-bootrom to flash the bootrom, and finally ./pm3-flash-fullimage to flash the full image.

Pulling this from:

The only difference is you already have the files from the Proxmark GitHub, so you want to do git pull instead of git clone to update the files.
And I changed make clean && make -j8 all because iirc that was messing with some people. The -j8 tells it to run multiple threads during compiling which should make it faster but taking that out doesn’t hurt the process.



Thank you for that, but I’m no further forward.

I only seem to have .proxmark3 directory and no proxspace.

All I’m seeing is this:

ashscott@espresense-lounge .proxmark3 % ls
history.txt		logs			preferences.json
ashscott@espresense-lounge .proxmark3 % git pull
fatal: not a git repository (or any of the parent directories): .git
1 Like

Yes, you’ll not remember - barely do. I found you on a blog or forum and you sent me 2 RFID tags. No implanters at the time though or you couldn’t send them outside the US or somesuch. I never forgot your name though!

Anyway, I’m only now getting started with this. Guess it’s all just about priorities. I now have the time and a need.

Sorry, I made an ass out of myself and ass-umed you were on windows. No proxspace then, but you should have a proxmark3 directory as well as a .proxmark3 directory. We want the non hidden proxmark3 directory.

1 Like

I’m not really any further forward with this.

I’m now seeing:

It says Target.... device / fw mismatch which isn’t helping me much as I don’t know which is out of date.

What I don’t understand is how it got like this.

It was all fine at one point. Does it auto update?

When I try this I get:

It does not. To update you need to pull the latest release and flash it, which is what we’re trying to do to fix the firmware mismatch.

My next step would be deleting the proxmark3 directories and starting again following this guide. proxmark3 should be a git directory if properly installed.

Have we ruled out your platform setup?

Are you running a PM3 Easy or RDV4

Have you chosen the correct one in the makefile.platform

notepad makefile.platform

(totally my screenshot, and not Amals :wink:)
If you have an Easy, do this

Change this ( just move the # )

to this

File - Save - Close

1 Like

As a note. Don’t use brew install. If you used it in the past make sure you uninstall that instance.

You’re thinking re-install from scratch, I hate to say it, but I’m thinking (given the 15 year comment) it may be that the PM isn’t in bootloader mode. Do the lights on the PM indicate that it’s in bootloader mode.

It can’t hurt to try the flashing/initial setup.

Being that the PM3RDV4.01 setup/use was the easiest part of my implant research journey, I’d also look at interference. (PM3 in a SLNT bag and/or making sure you’re in an area without interference.)

@ashs Can you disclose what OS/hardware you’re using? Mac/Ubuntu/Linux/other? (not needed, but I’m curious given your screenshots.)

Thanks for the help.

I’m using Mac OS Sonoma with a PM3.

I’m not sure if this helps, but this is what is in my proxmark3 folder:

Are you suggesting that I delete this and start again?

If I were you, in the situation/state your PM3 appears to be in, I’d start fresh, in a completely different directory. With the fresh install instructions from…This link. @Pilgrimsmaster had the right idea, but linked to the Linux instructions, and with Macos, it’s a bit different.

This is what I currently think is the issue (not being able to run pm3-flash-all right now.) But doing the above should get you all set.

Feel free to ask more questions if you have them.



Here’s my plan.

  1. Delete the proxmark3 directory. Will that yield the same result as uninstalling?

  2. Follow this guide

The bit I’m unclear on is step 3:

What does the optional step 3 do? Do I need that?

I’m thinking that it ties in with this, as per Pilgrimmaster’s post:

What do I need to do here?

  1. Yes, functionally
  2. step 3 isn’t optional for you this time around. (Sorry for being unclear before.)
  3. Ok, this depends on what hardware you actually have.
    • If you have a Proxmark3 Easy, then you want the PM3GENERIC line without the pound sign.
    • If you have a Proxmark3 RDV4 (not the Easy) then you want the PM3RDV4 line without the pound sign.
    • If you want to be really confused (don’t do this) then type make platform= and you’ll see a WHOLE LOT of options that you don’t need right now. :slight_smile: (I mean you can do it, just don’t choose one. :slight_smile: )

You’re making great progress! Don’t hesitate to ask more questions if you have them.

1 Like