[solved] Trouble flashing IceMan's fork bootrom.

samburner3 · 2017-02-19 01:13:00

iceman wrote:

@samburner3 if you try icemanfork, you will find that your tag will correctly be identified as a Generation 1 magic tag.

Hmm (On MAC OS X) I have Tap this repo with home brew: brew tap iceman1001/proxmark3
downloaded your fork into a new directory,
make clean; make,

but then on flashing the bootrom, I get "Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found." but it then hangs and nothing happens. If I disconnect or force stop it, I have to re flash the master fork bootrom for it to function again.

sam$ cd ProxMark3_IceMan/
sam$ cd proxmark3
sam$ ./client/flasher /dev/cu.usbmodem1411 -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

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.

I also followed all the normal master OS X instructions, then dropped in your fork...

brew tap nitsky/stm32
brew install readline libusb p7zip libusb-compat wget qt5 pkgconfig arm-none-eabi-gcc

export PKG_CONFIG_PATH=/usr/local/Cellar/qt5/5.6.1-1/lib/pkgconfig/

  export QT_PKG_CONFIG_QT5CORE=`find /usr -name Qt5Core.pc 2>/dev/null`
  chmod 666 $QT_PKG_CONFIG_QT5CORE
  echo "moc_location=\${prefix}/bin/moc" >> $QT_PKG_CONFIG_QT5CORE
  chmod 444 $QT_PKG_CONFIG_QT5CORE

brew link --force readline

git clone https://github.com/iceman1001/proxmark3.git
git pull

make clean; make,
cd proxmark3
./client/flasher /dev/cu.usbmodem1411 -b bootrom/obj/bootrom.elf

with same result of it hanging on

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.

and nothing else happening.

Last edited by samburner3 (2017-02-21 03:37:38)

iceman · 2017-02-19 01:15:54

you don't need to flash bootrom, if you are on CDC already. Just flash fullimage.

but if you do have problems, try press button and keep button pressed, meanwhile you flash fullimage.
after its done, you can release button..

samburner3 · 2017-02-19 01:33:58

Tried first without holding button:

sam$ client/flasher /dev/cu.usbmodem1411 armsrc/obj/fullimage.elf
Loading ELF file 'armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x00030e50->0x00030e50) [R X] @0x94
1: V 0x00200000 P 0x00132e50 (0x00001af4->0x00001af4) [RW ] @0x30ee4
Note: Extending previous segment from 0x30e50 to 0x32944 bytes

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on /dev/cu.usbmodem1411... Found.
Error: Unexpected reply 0x00fe (expected ACK)

And a second time:

sam$ client/flasher /dev/cu.usbmodem1411 armsrc/obj/fullimage.elf
Loading ELF file 'armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x00030e50->0x00030e50) [R X] @0x94
1: V 0x00200000 P 0x00132e50 (0x00001af4->0x00001af4) [RW ] @0x30ee4
Note: Extending previous segment from 0x30e50 to 0x32944 bytes

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.
Error: Unexpected reply 0x00fe (expected ACK)

Then tried with holding button:

sam$ client/flasher /dev/cu.usbmodem1411 armsrc/obj/fullimage.elf
Loading ELF file 'armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x00030e50->0x00030e50) [R X] @0x94
1: V 0x00200000 P 0x00132e50 (0x00001af4->0x00001af4) [RW ] @0x30ee4
Note: Extending previous segment from 0x30e50 to 0x32944 bytes

Waiting for Proxmark to appear on /dev/cu.usbmodem1411. Found.
Error: Unknown Proxmark mode

I have the Elechouse v2 Proxmark3.

Last edited by samburner3 (2017-02-19 01:34:30)

iceman · 2017-02-19 02:07:22

Hrm, second person today saying "Error: Unexpected reply 0x00fe (expected ACK)" ...

0xFE == NACK.

What does the output from compilation say?

samburner3 · 2017-02-19 02:14:10

iceman wrote:

What does the output from compilation say?

Sorry I'm a n00b, how do I produce this?
From compiling the fork? As in the output from the make install command?

iceman · 2017-02-19 02:23:42

the output from "make clean && make all"...
use pastebin.com

samburner3 · 2017-02-19 02:38:38

http://pastebin.com/GFd0ubW8

Last edited by samburner3 (2017-02-19 02:38:54)

iceman · 2017-02-19 14:08:11

You can use the release v1.6.9, it doesn't have this issue.

Found here https://github.com/iceman1001/proxmark3 … tag/v1.6.9

iceman · 2017-02-20 11:31:49

The issue is found.
File common/makefile.common row 66,67

https://github.com/iceman1001/proxmark3 … common#L66

You need to comment these to lines out again. After that you can compile and flashing should go as normal.

iceman · 2017-02-20 21:53:44

Just recap your solutions, edit your first post and add "[solved]" to the beginning of your subject.

Proxmark3 community

Announcement

#1 2017-02-19 01:13:00

[solved] Trouble flashing IceMan's fork bootrom.

#2 2017-02-19 01:15:54

Re: [solved] Trouble flashing IceMan's fork bootrom.

#3 2017-02-19 01:33:58

Re: [solved] Trouble flashing IceMan's fork bootrom.

#4 2017-02-19 02:07:22

Re: [solved] Trouble flashing IceMan's fork bootrom.

#5 2017-02-19 02:14:10

Re: [solved] Trouble flashing IceMan's fork bootrom.

#6 2017-02-19 02:23:42

Re: [solved] Trouble flashing IceMan's fork bootrom.

#7 2017-02-19 02:38:38

Re: [solved] Trouble flashing IceMan's fork bootrom.

#8 2017-02-19 14:08:11

Re: [solved] Trouble flashing IceMan's fork bootrom.

#9 2017-02-20 11:31:49

Re: [solved] Trouble flashing IceMan's fork bootrom.

#10 2017-02-20 21:53:44

Re: [solved] Trouble flashing IceMan's fork bootrom.

Board footer