Skip to content
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

Mifare Ultralight EV1 support #104

Open
ogsts opened this issue Mar 28, 2017 · 6 comments
Open

Mifare Ultralight EV1 support #104

ogsts opened this issue Mar 28, 2017 · 6 comments
Assignees

Comments

@ogsts
Copy link

ogsts commented Mar 28, 2017

Is it possible to emulate Mifare Ultralight EV1 using Chameleon Mini ?

http://www.nxp.com/products/identification-and-security/mifare-ics/mifare-ultralight/mifare-ultralight-ev1-contactless-ticket-ic:MF0UL1101DUD?tab=Documentation_Tab

@doegox
Copy link
Contributor

doegox commented Mar 28, 2017

I'm afraid not currently. Feel free to propose a patch ;)

@geo-rg geo-rg self-assigned this Apr 5, 2017
@geo-rg
Copy link
Collaborator

geo-rg commented Apr 5, 2017

@ogsts If you feel confident with C, I would encourage you to start a development on Mifare Ultralight EV1 emulation. AFAIK it uses ISO14443 only with low data rates, so you can use the codecs, which are already on the Chameleon right now. The only thing you have to do is implementing the Application layer.

You could start with a look at Firmware/Chameleon-Mini/Application/MifareUltralight.c. There you can see, how the application for MifareUltralight is realized. Maybe you copy-paste it to another file, e.g. MfareUltralightEV1.c and then add the EV1 functionality. We would look forward to you contribution! I also think you would get help from others here.

@ogsts
Copy link
Author

ogsts commented Apr 12, 2017

I have created first version of Mifare Ultralight EV1 support on Chameleon-Mini.
I can read it using phone and NXP TagInfo application identifies Chameleon Mini as Mifare Ultralight EV1.
I have turned LOGMODE=memory and I see all expected ISO14443A commands REQA, ATQA, SELECT_CL1, etc. However, target reader where I would like to use emulated EV1 does not read it.
And log contains nothing. So, I believe it is related to antenna matching. Any idea if/how this can be tuned ?

@geo-rg
Copy link
Collaborator

geo-rg commented Jul 12, 2017

Hi @ogsts
sorry for the late response. Have you solved this?

If not: the log shows really nothing? Not even receiving the REQA? Then I would think that the log function was deactivated at that time ;) But also, there has been a fix within the codec, but the bug which was fixed would not cause receiving nothing.

@arne182
Copy link

arne182 commented Oct 27, 2017

Hi @ogsts
I would also be interested in testing and help integrating this feature.

@dev-zzo
Copy link
Contributor

dev-zzo commented Nov 16, 2017

@ogsts Ping. :-) If you don't mind sharing your implementation as a pull request, I am sure it will be greatly appreciated by the community here.

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

No branches or pull requests

5 participants