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
I've looked for this problem on the site and I can't find anyone who had it before.
I'm trying to program the PM3 for the first time using the ebuller image. I connect the device to USB and all four LEDs light up. I plug in the programmer (an olimex wiggler clone) to the parallel port and start up the armpgm software. I select the entry for SAM7X256-16-to-48MHz, click Check, and the program just hangs. It continues to hang, and the only way to get it out of that state is to unplug the proxmark. If I do that, it says Unable to stop target, the same as if the proxmark isn't connected. Trying to use any of the functions of armpgm causes it to hang.
Has anyone else had this problem getting the device running before? For what it's worth, when plugged in the device is drawing about 90mA, so I don't think there's a short on the board. Thanks in advance for your help.
Offline
Make sure it's plugged into the 2x10 pin header and also that it's plugged the right way around. Also that the PM3 is supplied power via USB.
Offline
The programmer is definitely plugged in the right way (the key is on the top edge of the board, pin 1 is top right), and the board is getting powered because the LEDs are on (and I measured the current draw).
Offline
For what it's worth, all four of the JTAG pins are jittering away while armpgm is hung, so it seems like the signal is getting to the microcontroller and back.
Offline
Check in the BIOS that your parallel port is configured in legacy mode (standard, AT or something like that) and not in ECP or EPP modes and that you installed the port driver.
Offline
No dice. At this point I've tried EPP, ECP, AT, and PS/2 parallel port modes.
Offline
Apparently the microcontroller was faulty (probably heat damage). I switched the part out and it's working fine now.
Offline
Good job sorting that out
Offline
I had the same symptom but the reason was my parallel cable so i change it. (Some pins were not linked)
Offline
Pages: 1