Winter '10 - test release

iZsh · 2010-02-26 16:09:02

Hello,

I just uploaded a binary beta release
http://proxmark3.googlecode.com/files/p … s_beta.zip

if you guys (well, people with some knowledge, because there are no documentation yet) could give it a try, if possible from a pristine windows (so I know whether or not I forgot some DLLs), that'd be great.

to flash the proxmark with it, just use:
flasher.exe ..\arm\fullimage.elf
from the bin directory.

Let me know how it goes...

(on a pristine windows computer, you'll *first* have to install the proxmark driver I included, since it will install the libusb0 DLL. The installation procedure *will* be documented of course...)

Edit: A bootrom is included. If someone (with JTAG ^^) can test it as well...

Edit2: I have updated the link to the beta version

Last edited by iZsh (2010-02-27 11:10:23)

d18c7db · 2010-02-26 21:55:37

Thanks iZsh and and marcan, the latest changes are pretty awesome.

I compiled the latest r405 tree in the proxspace environment (devkitARM-r27) and it compiles fine, no warnings or errors. The main os flashes and appears to work (issued some lf and hf commands and data plot window, but no antenna and no actual tag reading)

The bootrom fails to flash, see out output below (i've deleted some progress dots ... for brevity):

$ client/flasher.exe -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 (0x0000172c->0x00001780) [RWX] @0x294
Error: PHDR file size does not equal memory size
(DATA+BSS PHDRs do not make sense on ROM platforms!)
Error while loading bootrom/obj/bootrom.elf

$ client/flasher.exe armsrc/obj/fullimage.elf
Loading ELF file 'armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R  ] @0xb4
1: V 0x00110000 P 0x00110000 (0x000140b8->0x000140b8) [R X] @0xa570
2: V 0x00200000 P 0x001240b8 (0x00000004->0x00000004) [RW ] @0x1e628
Note: Extending previous segment from 0x140b8 to 0x140bc bytes

Waiting for Proxmark to appear on USB... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB... Found.

Flashing...
Writing segments for file: armsrc/obj/fullimage.elf
 0x00102000..0x0010c4bb [0xa4bc / 165 blocks].....<deleted>.. OK
 0x00110000..0x001240bb [0x140bc / 321 blocks]....<deleted>.. OK

Resetting hardware...
All done.

Have a nice day!

Omikron · 2010-02-26 22:29:41

I'd test it, but I just packed up all of my equipment in preparation for RSA next week. I'll test it some when I get to San Francisco. :-P

iZsh · 2010-02-26 22:30:28

Can you test the binary release? Because I'd really like to do a binary release for end users : they shouldn't have to compile anything. That'd prevent "non-developers" from compiling anything (which tends to yield to frustrations on both side).

@marcan: you fail

marcan · 2010-02-26 22:44:05

d18c7db: try svn again, I forgot to make the PHDRs explicit for the bootrom. The flasher is really paranoid and I'm trying to strictly follow some ELF semantics, so it issues that error if the BSS and DATA sections are merged because theoretically that would imply allocating space in Flash for BSS (even though that is unnecessary and makes no sense - it's an artifact of the way ROM images are built with ELF).

d18c7db · 2010-02-26 23:02:22

Heh, as luck would have it something went wrong, I don't think it's a problem with the source code, just something weird with the USB bus, I'll recover with the JTAG and try again

Flashing...
Writing segments for file: bootrom/obj/bootrom.elf
 0x00100000..0x001001ff [0x200 / 2 blocks].. OK
 0x00100200..0x0010192b [0x172c / 24 blocks]...........write failed: usb_reap: timeout error!
Trying to reopen device...
proxmark3> ReceiveCommandPoll returned 0
Error: Unexpected reply 0x0000 (expected ACK)
 ERROR
Error writing block 11 of 24

d18c7db · 2010-02-26 23:09:20

Yep, it's all good, flashed the bootloader a couple of times and it succeeded. Btw "hw ver" shows "#db# bootrom: Missing/Invalid version information"

$ client/flasher.exe -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 (0x0000172c->0x0000172c) [R X] @0x294

Waiting for Proxmark to appear on USB... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB.... Found.

Flashing...
Writing segments for file: bootrom/obj/bootrom.elf
 0x00100000..0x001001ff [0x200 / 2 blocks].. OK
 0x00100200..0x0010192b [0x172c / 24 blocks]........................ OK

Resetting hardware...
All done.

Have a nice day!

$ client/proxmark3
proxmark3> hw ver
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: Missing/Invalid version information
#db# os: svn 389-suspect 2010-02-26 20:22:29
#db# FPGA image built on 2009/12/ 8 at  8: 3:54
proxmark3>

Last edited by d18c7db (2010-02-26 23:11:09)

marcan · 2010-02-26 23:12:05

Can you confirm that flashing an old bootrom and then the new bootrom still works?

d18c7db · 2010-02-26 23:20:06

Yes that's what I did to recover, flashed an old Summer 2009 bootrom via JTAG then upgraded via USB.

marcan · 2010-02-27 00:29:43

The bootrom version glitch should be fixed now (had to add KEEP() to make sure the linker doesn't throw away the section)

iZsh · 2010-02-27 11:10:54

I updated the link to the beta version

proxcat · 2010-02-27 16:46:35

Just tested on a pristine windows host. Flashing worked fine however proxmark3.exe failed to start due to missing DLLs. First one encountered was mingwm10.dll but there may be more.

proxcat · 2010-02-27 16:50:48

Re: DLL woes, I think the client Makefile might need a -static thrown in.

iZsh · 2010-02-27 17:20:20

mingwm10.dll is available on the internet, could you tell me what's missing apart from this one?

as for the -static, that's not that simple unfortunately...

proxcat · 2010-02-27 17:24:54

Looks like that was the only one missing. Nice work!

iZsh · 2010-02-27 17:51:42

ok, I'll upload a new version tomorrow including the .dll.
I have to go atm

Widmo · 2010-02-27 21:05:49

How to install drivers?

Thanks

proxcat · 2010-02-27 22:25:31

On XP, connect your Proxmark then click:

Control Panel -> System -> Hardware Tab -> Device Manager

Find the Proxmark under "Human Interface Devices", it will show up as a "USB Human Interface Device".

Right click the device and select "Update Driver", specify the proxmark_driver folder and you should be all set.

Widmo · 2010-02-28 02:58:57

Ye, I think it is that way, but proxmark is not detected in this lists.

I have Windows 7 x64 and x86 and can't do it on both.

I will wait for some XP system

Thank You!

iZsh · 2010-02-28 11:56:23

I updated the zip file. it now includes the missing dll and the bootrom fix from d18.

Hopefully this archive would now work just fine

Last edited by iZsh (2010-02-28 11:56:47)

Widmo · 2010-02-28 13:59:12

Ye, I think it is that way, but proxmark is not detected in this lists.

I have Windows 7 x64 and x86 and can't do it on both.

I will wait for some XP system

Thank You!

aawnsd · 2010-03-02 00:25:40

tried http://proxmark3.googlecode.com/files/p … s_beta.zip (downloaded 03/01/2010) on a newly installed win os.

For installing USB driver I followed instructions from here: http://www.proxmark.org/forum/post/2813/#p2813

d18c7db wrote:

This is the magic: run msys\mingw\bin\inf-wizard.exe, it is a GUI app, click next, select the device with PID/VID 9AC4/4B8F, on the next screen leave everything as is (or you can put proxmark3 in the manufacturer name), click next and save the files back in msys\mingw\bin
Next go into the Windows Device Manager (right click My Computer, select Manage) and expand the Human Interface Devices tree, double click each device in turn and select the Details tab until you find the one with PID/VID 9AC4/4B8F, exit that dialog and right click that last device, select Update Driver, select "No" to windows connecting to Windows Update, select advanced on the next screen, select "Don't search, I will choose...", select "Have Disk", then browse to msys\mingw\bin and let it install the driver.

I got all the tools flasher, proxmark3, cli up and running...

I still get one error during "hw reset" or during flashing. I tried to build latest trunk (412), but issue stays. Here is what I get:

proxmark3> hw reset
write failed: usb_reap: reaping request failed, win error: one device connected to the system is not running...
!
Trying to reopen device...
read failed: usb_reap: reaping request failed, win error: one device connected to the system is not running...
(-5)!
Trying to reopen device...
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 412-suspect 2010-03-01 21:18:48
#db# os: svn 412-suspect 2010-03-01 21:18:10
#db# FPGA image built on 2009/12/ 8 at  8: 3:54

Anybody can help on the meaning and on how to solve it?

iZsh · 2010-03-02 02:04:54

probably nothing to worry about, looks like a timing issue since it seems to work after the 2nd attempt (when it tries to reopen the device it just sleeps for a while and try again, so it really depends how long it takes for your OS to reacquire the device). It seems to work just fine in your log, except of course the unnecessary error messages until it actually works.

BTW, the driver was included in the zip file (with the .inf file already generated), so you only had to tell the device manager to use it (but that's probably what you actually did? I'm not sure since you quoted the generation part as well).

d18c7db · 2010-03-02 04:34:20

Actually that "usb_reap" error is quite a pain if it happens in the middle of flashing the bootloader as it happened to me since you then have to break out the JTAG if you have it, or scream and pull your hair if you don't

proxcat · 2010-03-02 12:38:08

When running in an XP VM, the client gets to fire off about one or two commands before the client goes loopy. By loopy, I mean continuous reap errors or crashing. I plan on doing some more testing running native today.

One thing I've noticed is that the voltages reported by 'hw tune' differ from previous releases.

Is there a reason why we aren't tracking bugs with googlecode?

Proxmark developers community

#1 2010-02-26 16:09:02

Winter '10 - test release

#2 2010-02-26 21:55:37

Re: Winter '10 - test release

#3 2010-02-26 22:29:41

Re: Winter '10 - test release

#4 2010-02-26 22:30:28

Re: Winter '10 - test release

#5 2010-02-26 22:44:05

Re: Winter '10 - test release

#6 2010-02-26 23:02:22

Re: Winter '10 - test release

#7 2010-02-26 23:09:20

Re: Winter '10 - test release

#8 2010-02-26 23:12:05

Re: Winter '10 - test release

#9 2010-02-26 23:20:06

Re: Winter '10 - test release

#10 2010-02-27 00:29:43

Re: Winter '10 - test release

#11 2010-02-27 11:10:54

Re: Winter '10 - test release

#12 2010-02-27 16:46:35

Re: Winter '10 - test release

#13 2010-02-27 16:50:48

Re: Winter '10 - test release

#14 2010-02-27 17:20:20

Re: Winter '10 - test release

#15 2010-02-27 17:24:54

Re: Winter '10 - test release

#16 2010-02-27 17:51:42

Re: Winter '10 - test release

#17 2010-02-27 21:05:49

Re: Winter '10 - test release

#18 2010-02-27 22:25:31

Re: Winter '10 - test release

#19 2010-02-28 02:58:57

Re: Winter '10 - test release

#20 2010-02-28 11:56:23

Re: Winter '10 - test release

#21 2010-02-28 13:59:12

Re: Winter '10 - test release

#22 2010-03-02 00:25:40

Re: Winter '10 - test release

#23 2010-03-02 02:04:54

Re: Winter '10 - test release

#24 2010-03-02 04:34:20

Re: Winter '10 - test release

#25 2010-03-02 12:38:08

Re: Winter '10 - test release

Board footer