Proxmark3 community

PetNoc

Member

Registered: 2015-07-21

Posts: 8

Another flashing question

Hi Folks,

I just received my pm3 and needed to flash  to flash it to be recognised as a serial port.
Did the procedure on Win 7:

https://github.com/Proxmark/proxmark3/wiki/Windows

and all completed ok but it was still not seen as com port.
When i try to re-do the operation it does not work anymore,

When i run the FLASH NEW Bootrom (uses old flasher exe with -b option).bat
it gets stuck saying "Waiting for the USB to become available" forever.

I connected it to linux to see what kernel reports and i see the below:

Without the button pressed it still shows as a HID device:

Jul 21 19:39:57 kali kernel: [24976.492004] usb 1-1.2: new full-speed USB device number 9 using dwc_otg
Jul 21 19:40:02 kali kernel: [24981.613630] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f
Jul 21 19:40:02 kali kernel: [24981.625384] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 21 19:40:02 kali kernel: [24981.637690] usb 1-1.2: Product: ProxMark-3 RFID Instrument
Jul 21 19:40:02 kali kernel: [24981.648119] usb 1-1.2: Manufacturer: J. Westhues
Jul 21 19:40:02 kali kernel: [24981.657479] usb 1-1.2: SerialNumber: ChangeMe
Jul 21 19:40:02 kali kernel: [24981.683065] hid-generic 0003:9AC4:4B8F.0002: hiddev0,hidraw0: USB HID v1.00 Device [J. Westhues ProxMark-3 RFID Instrument] on usb-bcm2708_usb-1.2/input0

But with the button pressed it shows as serial:

Jul 21 19:40:42 kali kernel: [25021.242011] usb 1-1.2: new full-speed USB device number 11 using dwc_otg
Jul 21 19:40:42 kali kernel: [25021.366158] usb 1-1.2: New USB device found, idVendor=2d2d, idProduct=504d
Jul 21 19:40:42 kali kernel: [25021.377745] usb 1-1.2: New USB device strings: Mfr=1, Product=0, SerialNumber=0
Jul 21 19:40:42 kali kernel: [25021.390636] usb 1-1.2: Manufacturer: proxmark.org
Jul 21 19:40:42 kali kernel: [25021.412750] cdc_acm 1-1.2:1.0: This device cannot do calls on its own. It is not a modem.
Jul 21 19:40:42 kali kernel: [25021.440067] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
Jul 21 19:40:46 kali kernel: [25025.667879] usb 1-1.2: USB disconnect, device number 11

What did i screw up ?

I can't attempt to re-flash it on linux as i have problem compiling the binaries.

I am thinking of using jtag to flash it now.
Has anyone tried using Travis Goodspeed's GoodFET for this job ?

Regards
Peter

Dake

Contributor

Registered: 2015-06-16

Posts: 32

Re: Another flashing question

For the compilation problem with linux it is maybe you must install gcc-arm-none-eabi packet.
And then, after have to follow manual for linux, for bootrom flashing you tape in /client : ./flasher -b /dev/ttyACM{X} ../bootrom/obj/bootrom.elf and for image flashing : ./flasher /dev/ttyACM{X} ../armsrc/obj/fullimage.elf

Last edited by Dake (2015-07-22 08:42:01)

PetNoc

Member

Registered: 2015-07-21

Posts: 8

Re: Another flashing question

Perfect, thanks a lot
That was it (missing gcc-arm-none-eabi)

Now i have the bin files ready.
Do i understand it correctly that i need to flash in particular order ?

Peter

iceman

Administrator

Registered: 2013-04-25

Posts: 9,538

Website

Re: Another flashing question

yes,  always bootrom first,  then fullimage.

PetNoc

Member

Registered: 2015-07-21

Posts: 8

Re: Another flashing question

oki, so i now bricked it completely i think

I managed to flash the bootrom.elf under linux (after blacklisting it from mm)
but did NOT flash the fullimage immediately.
Now when i connect it to usb, linux does not see it at all and i have red and yellow led ON.
Is jtag the only way now ?

marshmellow

Contributor

From: US

Registered: 2013-06-10

Posts: 2,302

Re: Another flashing question

Hold pm3 button down and plug it into CPU (hold button down until finished flashing the fullimage.elf.)

PetNoc

Member

Registered: 2015-07-21

Posts: 8

Re: Another flashing question

ok, done with a few more bumps
thanks a lot for help.
Just a note for future reference.

After flashing the bootimage first, by linux was not detecting the pm3 anymore after connecting it to usb port.
not a single line in /var/log/kernel.log

last messages related to usb before were:

Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1012.898165] xhci_hcd 0000:0a:00.0: HC died; cleaning up
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.796848] xhci_hcd 0000:0a:00.0: Stopped the command ring failed, maybe the host is dead
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.864054] xhci_hcd 0000:0a:00.0: Host not halted after 16000 microseconds.
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.864064] xhci_hcd 0000:0a:00.0: Abort command ring failed
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.867669] xhci_hcd 0000:0a:00.0: HC died; cleaning up
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.871390] sched: RT throttling activated
Jul 22 09:48:20 winnie-Precision-M4600 kernel: [ 1032.871529] usb usb1-port1: couldn't allocate usb_device

Rebooting it fixed the problem (i guess simply unloading and reloading usb kernel modules would do)

Thanks a lot once more folks.

Regards
Peter