-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
improve Hitag S output #2579
improve Hitag S output #2579
Conversation
You are welcome to add an entry to the CHANGELOG.md as well |
@@ -37,28 +37,45 @@ | |||
static int CmdHelp(const char *Cmd); | |||
|
|||
static const char *hts_get_type_str(uint32_t uid) { | |||
// source 1: https://www.scorpio-lk.com/downloads/Tango/HITAG_Classification.pdf | |||
// IDE Mark | |||
// Each HITAG chip contains an unique Device Identifier (IDE ) so called a Serial Number. |
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.
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.
Simply copy/paste from the unofficial HITAG_Classification.pdf. I'm confused about the strange abbreviation "IDE" too. I can't find anything on the internet about the "IDE mark" except in the PDF itself. I don't even know if it's really applicable to Hitag S.
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.
I never heard of IDE mark too.
In NXP official documents its UID.
client/src/cmdlfhitaghts.c
Outdated
return ""; | ||
} | ||
uint8_t pid0 = uid & 0xF; | ||
uint8_t pid1 = (uid >> 4) & 0xF; |
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.
I suggest using defines NIBBLE_HIGH and NIBBLE_LOW
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.
Sweet, I didn't notice that. Handy!
|
||
// access right | ||
if (page_addr == HITAGS_UID_PADR) { | ||
PrintAndLogEx(NORMAL, _RED_("RO ")NOLF); |
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.
RED for read only
might be a bit too harsh. How about we just let it be normal white?
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.
I'm try to following the lf hitag read --ht2
color scheme. Read-only is usually normal for the UID page. However, for other pages, it means they are locked.
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.
We need a better unified color scheme.
Good improvements, this needs to be a bit adjusted to fit into the pm3 client style. |
b927952
to
2ac74e0
Compare
No description provided.