Skip to content

Question: how to name new firmware in the code #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
clanganke opened this issue Apr 3, 2025 · 1 comment
Open

Question: how to name new firmware in the code #59

clanganke opened this issue Apr 3, 2025 · 1 comment
Labels

Comments

@clanganke
Copy link

1st of all: thanx for a great library!

I just buyed a version similar to other RFID boards at

https://www.amazon.de/dp/B0DLGVNX93

however the photo there does not match, so I attach one.

The board works well with the extra SPI mode/timing configuration. as show in the comment of the examples. However, the firmware reports version byte 0x82, and, of course, the firmware program data is different.

Just for info: the cards/chips get reported as
Card SAK: 08
PICC type: MIFARE 1KB

As a temporary patch I added respective symbols and data so that communication and self test works just fine. Certainly I would provide a pull request. However, as the chip has got no type info printed on it, I have got no clue how to name the symbols or provide literals (where I put ???? here in pseudo code):

src\MFRC522Constants.h:

   symbol PCD_Version::Version_????

src\MFRC522Debug.cpp

  MFRC522Debug::PCD_DumpVersionToSerial
    switch(version) 
      case 0x82:
      logPrint.println(F(" = ????"));
      break;

src\MFRC522v2.h

  const byte Private_????_firmware_reference[]

Moreover, the version information v133 on the board may or may not refer to the chip. What would be the best way to name that firmware? Is there any method to safely identify the chip further?

Image

@github-actions github-actions bot added the Triage label Apr 3, 2025
@clanganke
Copy link
Author

Just noticed that the default SPI timing works with your library and that above MFRC522 board as well, and that my above statement on the special SPI timing was caused by a misconception on my side.

I just tested that successfully with

  • Arduino nano V3
  • Wemos D1 mini
  • Wemos D1 mini ESP32

with their respective package, within Arduino IDE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant