Comments on: MFOC improved http://valentijn.sessink.nl/?p=259 ʇıɐɐɹpɯo pɿǝɹǝʍ ǝp ɹɐɐʍ Wed, 10 Apr 2013 20:23:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Valentijn http://valentijn.sessink.nl/?p=259&cpage=1#comment-4772 Valentijn Sun, 06 Mar 2011 20:16:51 +0000 http://valentijn.sessink.nl/?p=259#comment-4772 By: Valentijn http://valentijn.sessink.nl/?p=259&cpage=1#comment-4771 Valentijn Sun, 06 Mar 2011 20:15:38 +0000 http://valentijn.sessink.nl/?p=259#comment-4771 @Whacko: Unfortunately, I don't have the slightest idea. The ACR122U seems to have a firmware bug though. @Whacko: Unfortunately, I don’t have the slightest idea. The ACR122U seems to have a firmware bug though.

]]> By: Valentijn http://valentijn.sessink.nl/?p=259&cpage=1#comment-4769 Valentijn Sun, 06 Mar 2011 20:12:16 +0000 http://valentijn.sessink.nl/?p=259#comment-4769 @O: Yes, I did. Generally though, the feeling is that the ACR122U reader has a firmware bug. The other thing is, that (parts of the) mf_configure() call are part of the protocol, especially when you try to read multiple cards. All in all, you should see my patch as a "quick hack" that, for unknown reasons, works around the bug in the ACR122U. And since no one knows what this bug is, adding half-baked code may not be the best thing to do. "It works for me" though :) @O: Yes, I did. Generally though, the feeling is that the ACR122U reader has a firmware bug. The other thing is, that (parts of the) mf_configure() call are part of the protocol, especially when you try to read multiple cards. All in all, you should see my patch as a “quick hack” that, for unknown reasons, works around the bug in the ACR122U. And since no one knows what this bug is, adding half-baked code may not be the best thing to do. “It works for me” though :)

]]> By: Tim http://valentijn.sessink.nl/?p=259&cpage=1#comment-4517 Tim Fri, 18 Feb 2011 13:02:35 +0000 http://valentijn.sessink.nl/?p=259#comment-4517 Hi valentijn, Thanks for your mfoc.c update. I noticed that you use a keys.h to define your challenge keys in i suppose. The line: #include "keys.h" due to this line the make will fail. After restoring the array with default Mifare Classic keys (uncommented what you commented and commented the keys.h include) as in the original mfoc.c make can continue. Hi valentijn,

Thanks for your mfoc.c update. I noticed that you use a keys.h to define your challenge keys in i suppose. The line:

#include “keys.h”

due to this line the make will fail.

After restoring the array with default Mifare Classic keys (uncommented what you commented and commented the keys.h include) as in the original mfoc.c make can continue.

]]> By: Whacko http://valentijn.sessink.nl/?p=259&cpage=1#comment-4504 Whacko Thu, 17 Feb 2011 18:27:53 +0000 http://valentijn.sessink.nl/?p=259#comment-4504 Hey Valentijn, I'm building a Mac OSX gui for mfoc. I run into the problem that the reader seems to crash after a little while. I implemented the changes you made, but it still seems to crash. Any insights as to what might be going wrong? If necessary I can supply you with my code. Whacko Hey Valentijn,

I’m building a Mac OSX gui for mfoc. I run into the problem that the reader seems to crash after a little while. I implemented the changes you made, but it still seems to crash. Any insights as to what might be going wrong? If necessary I can supply you with my code.

Whacko

]]> By: O http://valentijn.sessink.nl/?p=259&cpage=1#comment-4290 O Wed, 02 Feb 2011 11:28:35 +0000 http://valentijn.sessink.nl/?p=259#comment-4290 Did you pass this on to the authors of mfoc? Did you pass this on to the authors of mfoc?

]]>