[solved] Cannot use out of the box?

Delphis · 2017-06-09 22:24:21

Hi,

I just got my Proxmark device. I installed the driver as per the info (I'm on Windows 10). I'm seeing 'Proxmark COM3' in the Device Manager.

When I run the client software, enter 'hw version' I get:

Prox/RFID mark3 RFID instrument
bootrom: master/v2.3 2016-09-19 20:28:38
os: master/v2.3 2016-09-19 20:28:38
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 183707 bytes (35%). Free: 340581 bytes (65%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

However, running 'hw tune' yields:

Measuring antenna characteristics, please wait...#db# DownloadFPGA(len: 42096)
......#db# DownloadFPGA(len: 42096)
.
# LF antenna: 0.00 V @ 125.00 kHz
# LF antenna: 0.00 V @ 134.00 kHz
# LF optimal: 0.28 V @ 122.45 kHz
# HF antenna: 0.11 V @ 13.56 MHz
# Your LF antenna is unusable.
# Your HF antenna is unusable.

I thought the solution on the previous poster the mentioned about antenna being unusable was to flash the firmware. From this it seems I already HAVE the latest firmware?

Last edited by Delphis (2017-06-13 14:17:42)

ntk · 2017-06-09 22:40:02

which HW version you have there? how do you connect the antennas... check connector?

marshmellow · 2017-06-10 05:05:56

you do not have the latest firmware.
did you verify your antenna connections are good?

iceman · 2017-06-10 07:39:17

hm.. Don't be too sure of the firmware number. This is my device just flashed with latest pm3 master fullimage.elf, ignore bootrom.

Prox/RFID mark3 RFID instrument          
bootrom: iceman/master/release-build(no_git) 2017-05-17 23:02:50
os: master/v2.2.0-506-g8040afa-dirty-suspect 2017-06-10 06:08:04
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

I think we need to make a "Hard tag" on Github to force the new version v3.0.1

Delphis · 2017-06-12 14:33:45

Ah, so they ship without the latest firmware.. ookay. I'll check that. Yes, connections are good.

I'm still baffled as to why something that's shipped together as a kit doesn't ACTUALLY work out of the box.

Edit: This page where I bought it: https://store.ryscc.com/collections/featured/products/new-proxmark3-kit

mentions 2.3.0 as the 'current version'. Is there a 3.0 zip file to download? or even from another site?

Last edited by Delphis (2017-06-12 14:46:35)

marshmellow · 2017-06-12 14:41:05

That is a question for your seller not us.

It is possible your firmware version (that you flash) is not matched to your client version (application you run). Which is why running and flashing the current version may fix your issue.

Delphis · 2017-06-12 14:47:37

marshmellow wrote:

That is a question for your seller not us.
It is possible your firmware version (that you flash) is not matched to your client version (application you run). Which is why running and flashing the current version may fix your issue.

It's the 2.3 client I'm using.

Dot.Com · 2017-06-12 14:50:36

Is it the one with the horse head logo on it ?

iceman · 2017-06-12 15:07:59

Many sellers incl Elechouse ships their devices with older firmware. I would say almost everyone does.

@op, you might aswell dip your toe into the water and start getting the latest source from GitHub.
or look into @gator96100 's pre-compiled bin-distros. Or use homebrew if you are on a OS X machine.

I strongly suggest the latest release v3.0.1.

Delphis · 2017-06-12 16:47:53

Yea.. understood.

I put it on a new installation Ubuntu (16.04 LTS), compiled a clone of the master branch of the repository. Followed these instructions:

https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux

Compiled, run (as root) and with the device showing up in dmesg as ttyACM0 ..

./proxmark3 /dev/ttyACM0

Just returns back to the command prompt immediately.

I'm missing something.. Just not sure what it is.

PS: this is the device I have https://snag.gy/mECHZ9.jpg

iceman · 2017-06-12 17:02:49

you will need to flash fullimage to your device

Delphis · 2017-06-12 18:29:44

Okay, read this: https://github.com/Proxmark/proxmark3/wiki/flashing

I can get as far as the red and yellow lights come on, then they'll be on for a while and I hear a 'click' and the USB device shows as disconnected in dmesg.

Okay.. Flashing worked for me like this:

1. Run flasher software

./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf

2. Hold the button in (and keep holding it)

3. Connect to USB (and keep holding that button)

4. Should write and make progress until 'All done' appears.

root@ubuntu-test:/usr/src/proxmark3/client# ./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
Loading ELF file '../armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002b970->0x0002b970) [R X] @0x94
1: V 0x00200000 P 0x0012d970 (0x000019f0->0x000019f0) [RW ] @0x2ba04
Note: Extending previous segment from 0x2b970 to 0x2d360 bytes

Waiting for Proxmark to appear on /dev/ttyACM0......... Found.

(just hangs here)

The device continues to blink and click but I don't know if it's flashing or not?

Edit: If I try the fullimage flash procedure and keep holding the button when connecting it to the USB port, the software exits saying 'Sending bytes to proxmark failed'

Trying to adjust my timing of how long I hold the button down (IF I run the flasher software and THEN plug it in while holding the button just long enough so that it connects to the USB), I now get:

root@ubuntu-test:/usr/src/proxmark3/client# ./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
Loading ELF file '../armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002b970->0x0002b970) [R X] @0x94
1: V 0x00200000 P 0x0012d970 (0x000019f0->0x000019f0) [RW ] @0x2ba04
Note: Extending previous segment from 0x2b970 to 0x2d360 bytes

Waiting for Proxmark to appear on /dev/ttyACM0....................... Found.

Flashing...
Writing segments for file: ../armsrc/obj/fullimage.elf
0x00102000..0x0012f35f [0x2d360 / 362 blocks]......................Sending bytes to proxmark failed

Last edited by Delphis (2017-06-12 19:00:40)

Delphis · 2017-06-12 19:03:08

After all that, the thing is re-flashed but the client software still exits immediately after running.

Edit: Putting the thing back on a Windows machine, I get from the windows client (2.3 client):

proxmark3> hw version
[[[ Cached information ]]]

Prox/RFID mark3 RFID instrument
bootrom: master/v2.3 2016-09-19 20:28:38
os: master/v2.2.0-506-g8040afa-suspect 2017-06-12 15:08:22
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 193375 bytes (37%). Free: 330913 bytes (63%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

Saying 2.2 now? o.O

I'll re-clone and select the 3.0 tag. Didn't know the master branch was so old.

Last edited by Delphis (2017-06-12 19:20:19)

Delphis · 2017-06-12 20:05:36

I appreciate you all trying to help, reflashing with newer firmware wasn't the answer though.

I re-flashed the 2.3 binaries as found here: https://store.ryscc.com/blogs/news/upgrading-your-proxmark3-to-v2-3-over-usb

I'm using the client software on Ubuntu x64 and the precompiled binaries work great, it's communicating and the antenna is fine.

Edit: I forgot to add WHY the antenna is fine now. Apparently I had it too close to a metal shelf and it couldn't tune properly

Last edited by Delphis (2017-06-13 14:16:48)

marshmellow · 2017-06-12 21:38:07

When you flash from unreleased code the version numbers will not be accurate, even though you have more up to date software than the last release.

Delphis · 2017-06-13 14:17:26

marshmellow wrote:

When you flash from unreleased code the version numbers will not be accurate, even though you have more up to date software than the last release.

That makes sense, just confusing.

iceman · 2017-06-13 16:32:57

..at least try once the latest release v3.0.1, you'll get very much more out of your proxmark3 device.

Proxmark3 community

Announcement

#1 2017-06-09 22:24:21

[solved] Cannot use out of the box?

#2 2017-06-09 22:40:02

Re: [solved] Cannot use out of the box?

#3 2017-06-10 05:05:56

Re: [solved] Cannot use out of the box?

#4 2017-06-10 07:39:17

Re: [solved] Cannot use out of the box?

#5 2017-06-12 14:33:45

Re: [solved] Cannot use out of the box?

#6 2017-06-12 14:41:05

Re: [solved] Cannot use out of the box?

#7 2017-06-12 14:47:37

Re: [solved] Cannot use out of the box?

#8 2017-06-12 14:50:36

Re: [solved] Cannot use out of the box?

#9 2017-06-12 15:07:59

Re: [solved] Cannot use out of the box?

#10 2017-06-12 16:47:53

Re: [solved] Cannot use out of the box?

#11 2017-06-12 17:02:49

Re: [solved] Cannot use out of the box?

#12 2017-06-12 18:29:44

Re: [solved] Cannot use out of the box?

#13 2017-06-12 19:03:08

Re: [solved] Cannot use out of the box?

#14 2017-06-12 20:05:36

Re: [solved] Cannot use out of the box?

#15 2017-06-12 21:38:07

Re: [solved] Cannot use out of the box?

#16 2017-06-13 14:17:26

Re: [solved] Cannot use out of the box?

#17 2017-06-13 16:32:57

Re: [solved] Cannot use out of the box?

Board footer