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 am currently running winter 2010 firmware.
How can I downgrade the fw to summer 2009 version over usb?
I don't have JTAG cable.
Any help would be appreciated?
Offline
Hi !
I'm looking for the same thing as you.
Have you find a solution ?
I tried to flash the fpgaimage doing that:
I downloaded the archive, replaced the fpgaimage.s19 into armsrc/obj folder, connecting and holding the button then enter this command :
"./flasher fpga ../armsrc/obj/fpgaimage.s19" but received:
Could not open file 'fpga': No such file or directory
Error while loading fpga
Best regards.
Last edited by JeanLuc (2012-04-06 14:21:54)
Offline
Hi !
I'm looking for the same thing as you.
Have you find a solution ?Best regards.
What is the reason for the downgrade?
I don't think you can do this without the JTAG because of the bootloader. Previous versions of the firmware required the JTAG. The USB feature was an upgrade in 2010.
Seems like it would be just as easy to purchase a JTAG cable...........they are very cheap.
Offline
I want to downgrade because I would like to use a python API for a project.
Actually, my version is:
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 526 2012-02-20 13:58:51
#db# os: svn 526 2012-02-20 13:58:53
#db# FPGA image built on 2009/12/ 8 at 8: 3:54
Do I need to downgrade the bootrom version too ?
I think I only need to downgrade the fpgaimage...
Hmmm, thanks for the answer !
Last edited by JeanLuc (2012-04-06 14:47:34)
Offline
What FPGA firmware version does the Python API specify is required to work?
Offline
Hi !
I'm sorry for the late answer.
It is said on the topic:
That code was written against firmware version 20090713
If I'm right, this is the version which can be downloaded in the download section.
Offline
Have you tried using the later firmware to see if the python API will work? If not, use a firmware that can be installed with the later bootware and see if the python script works. If it doesn't, you will most likely need to get a JTAG......they're cheap!
Offline
Have you tried using the later firmware to see if the python API will work? If not, use a firmware that can be installed with the later bootware and see if the python script works. If it doesn't, you will most likely need to get a JTAG......they're cheap!
I have tried, but received this error:
Traceback (most recent call last):
File "./tune.py", line 8, in <module>
antennas = pm3.tune()
File "/home/logan/Documents/Stage EADS/ProxMark3/pyprox.backup/proxmark.py", line 98, in tune
raise ProxError("Unexpected response %x" %resp.cmd)
proxmark.ProxError: Unexpected response 100
In the topic of this API (cf. previous posts), someone got a similar error, and the author answered :
That code was written against firmware version 20090713. The code has not been maintained. It also relies on a specific version of libusb and python-usb.
About libraries, everything is ok.
But indeed, the code is different between the older and the newer firmware.
Due to the difficulties to downgrade the pm3, I search another solution, like modify the API source code.
I maybe found something:
For the tune command, here is a part of the code in the API:
if resp.cmd != 0x401:
raise ProxError("Unexpected response %x" %resp.cmd)
The 0x401 code is not this one any more for the measured antenna, it is 0x410 now. But even if I change this line, there's still something wrong.
It seems the script does not let enough time to measure antenna characteristics...
PS: Do I need to continue on this topic, continue on the API's topic, or create a new one?
Last edited by JeanLuc (2012-04-17 10:21:02)
Offline
I'm not sure revising the python script will help. You may have better luck revising the firmware to work with the existing python script. The firmware has to be able to recognize the python commands in order to know what to do with the PM3 hardware. Get it?
Offline
Yep, I understand.
But... for my project, it would be interesting to execute some commands in a script. This way, I would just have to start my script and not typing commands manually. So that's why I'm studying the code of the API, in order to understand how it works to improve it.
Offline
Pages: 1