Added new compiled windows release (named 0.0.3) in the 1st post with piwi's latest patches.
Unfortunately the main trunk seems not to be updated with the relatively new iclass stuff.
If you are updating from ver. 0.0.2 remember to update both bootloader and fullimage !! Otherwise your pm3 will not be recognized by windows !!!
Hi piwi, I think there is a problem in the new OS/FPGA files; I just flashed the latest fullimage release (starting from my 0.0.2) and now the proxmark is not shown in the COM list devices and the red led remains on; after a few couple of seconds it automatically reset itself.
Going back to 0.0.2 (holding the button is necessary) and flashing the latest OS-image OR the fpga-image only has the same behaviour but the red led doesn't remain on.
This is the problematic compiled firmware (there seem to be a "empty loadtable segment detected in fullimage.elf, is this intentional?" error while compiling... is this normal ?).
Should I also update the bootloader ?
You are using a proxmark.exe compiled for the CDC/serial interface with the old firmware with libusb interface; you must update the firmware if you want to use the new cdc/serial proxmark.exe; to update use the UpdateBootloader.pdf included in the main compiled archive.
If you want to remain in your actual firmware version you need to use the libusb drivers privided in the archive (folder \libusb-win32 (old usb interface) - that you are already using because you get info from proxmark3 hardware) and use an older compiled proxmark.exe (previous to r655).
I found some correlations but more examples are needed; my preliminary (very simple) analysis suggests that it will be probably impossible to obtain back the full 10 HEX ID starting from the already converted value, only a part should be "recoverable". If you can provide more examples I can try to investigate deeper and dismatle this supposition.