Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
Hi,
I recently purchased a Proxmark III and upgraded to the Winter '10 bootloader/OS/client. After the upgrade, doing anything with the device is flakey at best. A simple "hw tune" command yields (in most cases; sometimes it works. this seems random):
proxmark3> hw tune
write failed: usb_reap: timeout error!
Trying to reopen device...
After this, proxmark3.exe crashes. I suspected something wrong with the Windows client, so I managed to compile it for OS X. Same thing there with slightly different messages:
write failed: Operation timed out!
Trying to reopen device...
Segmentation fault
Same thing under Ubuntu. I tried re-flashing the Proxmark, but the problems persist. Things worked fine with the old (summer '09) release. I'd appreciate any tips on how to solve this. If nothing else, can I downgrade to the older firmware? Is it safe? If so, should I flash using the old or new client?
Thank you!
Tomas
Offline
I flashed the firmware to revision 440 (the latest), but that didn't help. Tune seems to work at the moment, but the device crashes (?) shortly after I issue the command.
proxmark3> hw tune
proxmark3> Can't open logfile, logging disabled!
#db# Measuring antenna characteristics, please wait.
proxmark3>
# LF antenna: 0.00 V @ 125.00 kHz
# LF antenna: 0.00 V @ 134.00 kHz
# LF optimal: 0.00 V @ 12000.00 kHz
# HF antenna: 7.48 V @ 13.56 MHz
# Your LF antenna is unusable.
proxmark3>
So far, so good, but after ~20 seconds of doing nothing:
read failed: Result too large(-34)!
Trying to reopen device...
Segmentation fault
And the device clicks (as it reboots, I guess). Any ideas?
Offline
Turns out it's my iMac misbehaving somehow, because it seems to work fine on my MacBook. Strange.
Offline
Did you ever figure out what caused this? I'm having exactly the same issue.
Thanks
Offline
Winter 10 it's a old old old version the last version is r653
You must read properly the manual
Offline
Unfortunately I get the same errors with the latest SVN version when running in OS X Mountain Lion. I think I've also seen an async timeout as well as the result too large error.
Running Windows 7 on the same computer works fine, however.
I have no idea what's going on here, nor have I really tried to debug it.
Offline
Same here guys. I'm not being able to run the client under OSX... Winxp 32b under vmware was my solution. I'll try to figure out what's going wrong....
Offline
Pages: 1