Proxmark developers community

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.

#1 2017-12-01 02:44:38

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Moving from iceman fork to the official firmware instruction

Hi guys,

have any of you moved from icemans latest firmware to the official full version?

How did go about it? I want to try something out, and want to do it.

Unfortunately, when I held down the button and try to flash the bootrom, it does not work. I 've tried it without holding down the button, again, no go.

I'm running the latest Kali OS.


Help will be greatly appreciated, thanks


root@U201702:~/proxmark3/client# ./flasher /dev/ttyACM0 -b ../bootrom/obj/bootrom.elf
Loading ELF file '../bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000c80->0x00000c80) [R X] @0x298
 
( THAT IS WHERE I RELEASE THE BUTTON-->) ( If I keep pressing it, it stays like above forever!)
 
Waiting for Proxmark to appear on /dev/ttyACM0............ Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/ttyACM0..........................
..............................
..........................................................................
..........................................................................
..........................................................................
......................^C 

Last edited by Heru (2017-12-01 05:01:15)

Offline

#2 2017-12-01 05:36:51

iceman
Administrator
Registered: 2013-04-25
Posts: 4,158
Website

Re: Moving from iceman fork to the official firmware instruction

its waiting for /dev/ttyACM0 to come up.  It didn't. Look if you got another com-port assigned.. 

ls /dev/ttyAC*


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#3 2017-12-01 08:20:34

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

iceman wrote:

its waiting for /dev/ttyACM0 to come up.  It didn't. Look if you got another com-port assigned.. 

ls /dev/ttyAC*

Hi dear iceman, thanks for your response,

the second time when proxmark connects ( unlug and plug it back_) to my laptop it usually gets following com port /dev/ttyACM1.

So any cure for it, like hard-coding the COM Port to /dev/ttyACM0, make sure it does not hop over different COM ports etc.?

Yea, I'll be keep trying but I gotta be careful not to brick it, dont have any tool to recover from it.

Offline

#4 2017-12-01 09:05:55

iceman
Administrator
Registered: 2013-04-25
Posts: 4,158
Website

Re: Moving from iceman fork to the official firmware instruction

...your device changes comport once it enters bootload mode.    So,  instead of waiting in wait, you need to press ctrl-c  and change your flash command to match the new comport without touching the device.   You can see the device is in bootload mode with two leds lit.

if you can,  try the alias "/dev/pm3-0"  but that will only work is you used iceman fork's udev rule...


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#5 2017-12-01 11:17:02

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

Ok, thanks much,

I'm using icemans udev rule, so yes I'll try the alias too

Offline

#6 2017-12-02 09:56:45

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

Hi Iceman, thanks for your timeless support, but Im still unable to make any progress,.

When I hold the button, then connect the device to my laptop( while monitoring the usb debug), it does not connect at all. does not assign any of ttyACM0, 1 COM port,  So I assume that is the main problem for me.

On the other hand, if I connect the device without holding down the button , it connects to either ACM0 or ACM1 com port, which is expected result.

Also, I tried to connect the device to a Windows 7 box and force upgrade it from there, Unfortunately, could not connect the to device,

After entering "./client/proxmark3.exe com3", the command does nothing, just blank screen. ( this is a setup where Win7 driver installed and working, shown as proxmark3 in Device Manager COM port section),

So I assume this is because I installed the existing iceman 3.0.1 firmware on Linux box, So I guess it could happen in Windows environment,

Offline

#7 2017-12-02 09:59:32

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

For now, my option is just leave it as it is, hopefully some people will come up with a safer solution to upgrade to the master.

Offline

#8 2017-12-02 17:50:54

iceman
Administrator
Registered: 2013-04-25
Posts: 4,158
Website

Re: Moving from iceman fork to the official firmware instruction

Strange.  I swap regulary between my fork and offical pm3.
I'm suspect you are doing something wrong.  No need to use the "press-the-button" trick if your device is working normally.

Upgrading from win or linux doesn't matter at all.  Its just the same.  You need to have the device installed (update the driver) on a win7 machine.


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#9 2017-12-03 01:10:29

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

Ok, thank you, Note well taken,

My issue is, as soon as the device goes into the bootloader mode, ( 2 blue lights lit). the laptop refuses to assign a COM port to it, (linux box)

For example, when I connect the device while holding the button ( bootloader mode), it never gets a com port assigned, ( dmesg | grep -i usb) nothing.

Another instance is when you enter the flash command manually, then the device tries to go to the bootloader mode. Again, refuses to assign COM port, ( 2 x lights lit, I'm also monitoring the dmesg usb debug real time to observe)....hence "Waiting blabla " message.

When I press control+c, and attempt with a different ACMX port, the same thing happens.

For the Windows 7 issue, I 'll try re-compiling it and run it again, TBH, I highly doubt it will work, but this is another issue right, 

thanks for your help iceman

Offline

#10 2017-12-03 07:57:16

iceman
Administrator
Registered: 2013-04-25
Posts: 4,158
Website

Re: Moving from iceman fork to the official firmware instruction

hw version
hw status

Lets start with this.  when did you upgrade to iceman fork?   there was a issue for september commits. 
If you didn't clone / compiled fro github,  did you download a binary precompiled distro from someone?


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#11 2017-12-04 04:30:17

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

Proxmark3 RFID instrument

 [ ARM ]
 bootrom: iceman/master/ice_v3.1.0-19-gfeea1a45 2017-10-05 18:09:38
      os: iceman/master/ice_v3.1.0-19-gfeea1a45 2017-10-05 18:09:44
 [ FPGA ]
 LF image built for 2s30vq100 on 2015/03/06 at 07:38:04
 HF image built for 2s30vq100 on 2017/05/17 at 17:48:26

 [ Hardware ]
  --= uC: AT91SAM7S512 Rev B
  --= Embedded Processor: ARM7TDMI
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 220509 bytes (42%) Free: 303779 bytes (58%)
  --= Second Nonvolatile Program Memory Size: None
  --= Internal SRAM Size: 64K bytes
  --= Architecture Identifier: AT91SAM7Sxx Series
  --= Nonvolatile Program Memory Type: Embedded Flash Memory


pm3 --> hw status
#db# Memory
#db#   BIGBUF_SIZE.............40000
#db#   Available memory........40000
#db# Tracing
#db#   tracing ................1
#db#   traceLen ...............0
#db# Fgpa
#db#   mode....................HF
#db# LF Sampling config:
#db#   [q] divisor.............95 (125 KHz)
#db#   [b] bps.................8
#db#   [d] decimation..........1
#db#   [a] averaging...........Yes
#db#   [t] trigger threshold...0
#db# USB Speed:
#db#   Sending USB packets to client...
#db#   Time elapsed............1500ms
#db#   Bytes transferred.......860672
#db#   USB Transfer Speed PM3 -> Client = 573781 Bytes/s
#db# Various
#db#   MF_DBGLEVEL.............2
#db#   ToSendMax...............-1
#db#   ToSendBit...............0
#db#   ToSend BUFFERSIZE.......2308
#db# Installed StandAlone Mods
#db#    LF HID26 standalone - aka SamyRun (Samy Kamkar)
#db# Running
pm3 -->

Thanks for looking after this.

I bought PM3 in October and installed the iceman fork straight away following this guide    "https://github.com/iceman1001/proxmark3"

The install went smooth, had no issue at all if I remember correctly

Since then, I never upgrade/downgrade any bootloader or OS image, just runs as it is, until the date.

Offline

#12 2017-12-04 04:40:04

Heru
Contributor
Registered: 2017-10-08
Posts: 36

Re: Moving from iceman fork to the official firmware instruction

Connecting+button pressed :

[63442.695533] usb 2-1.3: new full-speed USB device number 116 using ehci-pci
[63443.191641] usb 2-1.3: device not accepting address 116, error -32
[63443.271613] usb 2-1.3: new full-speed USB device number 117 using ehci-pci
[63443.767649] usb 2-1.3: device not accepting address 117, error -32
[63443.847706] usb 2-1.3: new full-speed USB device number 118 using ehci-pci
[63444.263753] usb 2-1.3: device not accepting address 118, error -32
[63444.343714] usb 2-1.3: new full-speed USB device number 119 using ehci-pci
[63444.759803] usb 2-1.3: device not accepting address 119, error -32
[63444.759922] usb 2-1-port3: unable to enumerate USB device

Normal connection:

[63478.371313] usb 2-1.3: new full-speed USB device number 126 using ehci-pci
[63483.553494] usb 2-1.3: New USB device found, idVendor=9ac4, idProduct=4b8f
[63483.553499] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[63483.553502] usb 2-1.3: Product: PM3 Device
[63483.553504] usb 2-1.3: Manufacturer: proxmark.org
[63483.553506] usb 2-1.3: SerialNumber: 88888888
[63483.554032] cdc_acm 2-1.3:1.0: ttyACM1: USB ACM device

Offline

#13 2017-12-04 08:34:21

iceman
Administrator
Registered: 2013-04-25
Posts: 4,158
Website

Re: Moving from iceman fork to the official firmware instruction

hm,  the october bricking...   yeah,  you will to take out a buspirate, segger,  and JTAG your device with latest version of source.
Then this problem will go away.   I did some changes in the usb_cdc which caused ppl's pm3's to get bricked.


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

Board footer

Powered by FluxBB