-
Notifications
You must be signed in to change notification settings - Fork 166
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
Lf read From merlokk #216
base: main
Are you sure you want to change the base?
Lf read From merlokk #216
Conversation
You are welcome to add an entry to the CHANGELOG.md as well |
@@ -72,6 +72,7 @@ class Command(enum.IntEnum): | |||
|
|||
EM410X_SCAN = 3000 | |||
EM410X_WRITE_TO_T55XX = 3001 | |||
DATA_CMD_LF_READ = 3010 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe rename to LF_READ
?
@@ -116,6 +117,8 @@ class Status(enum.IntEnum): | |||
LF_TAG_OK = 0x40 | |||
# Unable to search for a valid EM410X label | |||
EM410X_TAG_NO_FOUND = 0x41 | |||
# Unable to search for a valid LF tag | |||
LF_TAG_NO_FOUND = 0x42 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe rename EM410X_TAG_NO_FOUND
to LF_TAG_NO_FOUND
and reuse 0x41
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe rename
EM410X_TAG_NO_FOUND
toLF_TAG_NO_FOUND
and reuse0x41
?
At present, this PR is in the testing phase, and all code formats and naming conventions will be corrected before merging.
A notice should probably be added stating that this code is at least partly based on the Flipper lfrfid library |
can we start working on HID26 protocol emulation. It's by far the most common LF protocol. I'm not as familiar with the chameleon ultra codebase. If you tell me what are the files that are need I'd be happy to contribute |
I will confirm some copyright related issues with the author, which is indeed very important. |
Within the "firmware/application/src/rfid", you can see the 'nfctag' and 'reader' dir, if you are want to implement a tag, you can view the nfctag dir's file. |
Built artifacts for commit 8dab924FirmwareClient |
yes, it GPL3. license will be added later. |
What is the status of this PR? We are waiting for a new code base to support more LF protocols. Thanks. |
im working on it. i think in several weeks I will publish it |
Thanks for your work! |
Hello, here is my feedback: git clone https://github.com/merlokk/ChameleonUltra.git
cd ChameleonUltra
git remote add upstream https://github.com/RfidResearchGroup/ChameleonUltra.git
git fetch upstream
git checkout lf_read
git rebase upstream/main
docker run --rm --platform=linux/amd64 -v "$(pwd)":/workdir -w /workdir ghcr.io/rfidresearchgroup/chameleonultra-fw-builder:pr-233 bash -c "./firmware/build.sh" For the curious, the builds will be in I therefore think about downgrading the FW to 1.0 to start testing my Chameleons with a firmware from scratch. But having no XXXLink (based on the only artefact available for 1.0) I just don't know how to load or pack this ultra.hex to load it into my chameleon. I will open a ticket to ask for help. To summarize: My issue has not been fixed (yet?) by this branch's code. I will continue digging on my side to see if my device is "corrupted" and if so, why. |
If you have the issues below, it can be the antenna issues. |
Strengthen low-frequency related functions