Proxmark3 community

tck

Member

Registered: 2011-04-06

Posts: 7

What's wrong with rev486

Hi,

I've just downloaded the latest and greatest SVN Revision 486 and after some struggle get it complied successfully. But it seems that I'm somehow unable to communicate with my brandnew PM3 from hackable devices. Everytime I start the proxmark3 client (i'm running in an Backtrack 5 VM with win7 host) I get:

root@bt:~/proxmark3-read-only# client/proxmark3

Connected units:
        1. SN: ChangeMe [002/009]
proxmark3> tune
help             This help. Use '<command> help' for details of the following commands:

data             { Plot window / data buffer manipulation... }
exit             Exit program
hf               { HF commands... }
hw               { Hardware commands... }
lf               { LF commands... }
quit             Quit program
proxmark3> version
help             This help. Use '<command> help' for details of the following commands:

data             { Plot window / data buffer manipulation... }
exit             Exit program
hf               { HF commands... }
hw               { Hardware commands... }
lf               { LF commands... }
quit             Quit program

I've also flashed the PM3 completely:

root@bt:~/proxmark3-read-only# client/flasher -b /root/proxmark3-read-only/bootrom/obj/bootrom.elf /root/proxmark3-read-only/armsrc/obj/osimage.elf /root/proxmark3-read-only/armsrc/obj/fpgaimage.elf
Loading ELF file '/root/proxmark3-read-only/bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00001618->0x00001618) [R X] @0x294

Loading ELF file '/root/proxmark3-read-only/armsrc/obj/osimage.elf'...
Loading usable ELF segments:
1: V 0x00110000 P 0x00110000 (0x0000fa30->0x0000fa30) [R X] @0xb8
2: V 0x00200000 P 0x0011fa30 (0x00001d00->0x00001d00) [RWX] @0xfae8
Note: Extending previous segment from 0xfa30 to 0x11730 bytes

Loading ELF file '/root/proxmark3-read-only/armsrc/obj/fpgaimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R  ] @0xb4

Waiting for Proxmark to appear on USB...
Connected units:
        1. SN: ChangeMe [002/007]
Found.

Flashing...
Writing segments for file: /root/proxmark3-read-only/bootrom/obj/bootrom.elf
0x00100000..0x001001ff [0x200 / 2 blocks].. OK
0x00100200..0x00101817 [0x1618 / 23 blocks]....................... OK

Writing segments for file: /root/proxmark3-read-only/armsrc/obj/osimage.elf
0x00110000..0x0012172f [0x11730 / 280 blocks]........................................................................................................................................................................................................................................................................................ OK

Writing segments for file: /root/proxmark3-read-only/armsrc/obj/fpgaimage.elf
0x00102000..0x0010c4bb [0xa4bc / 165 blocks]..................................................................................................................................................................... OK

Resetting hardware...
All done.

Have a nice day!

But nothing has changed. When I  run "tune" or "version" I only get the help-text. Are there any ideas what I'm doing wrong????

Thanks in advance
tck

Last edited by tck (2011-07-26 18:49:04)

tck

Member

Registered: 2011-04-06

Posts: 7

Re: What's wrong with rev486

hehehe .... sorry ... i've found it by myself ... and the next problem ...

root@bt:~/proxmark3-read-only# client/proxmark3

Connected units:
        1. SN: ChangeMe [002/011]
proxmark3> hw version
write failed: No error!
Trying to reopen device...
Segmentation fault

/var/log/messages says:

Jul 26 13:40:40 bt kernel: [ 2879.069512] usb 2-1: new full speed USB device using uhci_hcd and address 11
Jul 26 13:40:45 bt kernel: [ 2884.465894] generic-usb 0003:9AC4:4B8F.0009: hiddev0,hidraw0: USB HID v1.00 Device [ProxMark-3 RFID Instrument] on usb-0000:02:00.0-1/input0
Jul 26 13:41:00 bt kernel: [ 2899.091854] proxmark3[1910]: segfault at 0 ip b77ac637 sp b5a0e170 error 4 in libusb-0.1.so.4.4.4[b77a8000+6000]

i'll keep on searching ...

Bugman1400

Contributor

Registered: 2010-12-20

Posts: 132

Re: What's wrong with rev486

There may be a buffer overflow issue. Sometimes Proxmark3 will fail to start or ,once started, will fail to process commands correctly. I've always found that a reboot of my computer was necessary.

tck

Member

Registered: 2011-04-06

Posts: 7

Re: What's wrong with rev486

OK, the answer is ... don't try this from an VM Guest. Works like a charme with native (physical) ubuntu 11.04.