Proxmark3 community

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

[Resolved] Flashing bootrom problem (Windows 10 x64)

Hi

I am trying to flash the bootrom but doesn't succeed without any error message.
See this youtube video: https://www.youtube.com/watch?v=ATO35fD_UDE

The CDC driver is installed and my proxmark is currently running the v2.2 (http://prntscr.com/aju3yq)

Notes:
1) OS: Windows 10 x64
2) My goal is to flash this fork from iceman1001: https://github.com/iceman1001/proxmark3
3) Can't flash the main repository aswell.
4) Tried this in a virtual machine (Windows 10 x64) also failed
5) I need to keep pushing the button otherwise this red and orange light goes out (Maybe part of the problem?)
6) Device is not bricked

Compile console output (Without warnings)
http://pastebin.com/bd1F78jP

Compile console warnings:

cmddata.c: In function 'getSamples':
cmddata.c:2019: warning: dereferencing pointer 'sc' does break strict-aliasing rules
cmddata.c:2017: warning: dereferencing pointer 'sc' does break strict-aliasing rules
cmddata.c:2018: warning: dereferencing pointer 'sc' does break strict-aliasing rules
cmddata.c:2016: note: initialized from here
cmdhf14a.c: In function 'CmdHF14ACUIDs':
cmdhf14a.c:450: warning: dereferencing pointer 'card' does break strict-aliasing rules
cmdhf14a.c:451: warning: dereferencing pointer 'card' does break strict-aliasing rules
cmdhf14a.c:443: note: initialized from here
Qt: Untested Windows version 6.2 detected!
compressed 84672 input bytes to 34566 output bytes
compressed 11328 input bytes to 6571 output bytes
c:/proxspaceorigianl/devkitarm/bin/../lib/gcc/arm-none-eabi/4.7.1/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol Vector; defaulting to 00102000

Any help to troubleshoot this would be awesome!
Thanks!

Last edited by Vinnie (2016-04-02 14:15:01)

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

What commands are you using when trying to flash?
I also notice you are using Qt6.2,    which makes me wonder if you are using the recommened build environment found here:

https://storage.googleapis.com/google-c … -130613.7z

or if you downloaded the lastest of QT, cygwin, perl for windows and making your own build environment?

Did you follow the wiki's recommendations?
https://github.com/Proxmark/proxmark3/wiki/Windows

Last edited by iceman (2016-03-25 15:21:40)

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

I downloaded the latest Proxspace.
The QT version in that Proxspace is v4.6.2 (Latest QT is v5.6)

I use this command for flashing:
./client/flasher.exe -b COM4 ./bootrom/obj/bootrom.elf

The compiled bootrom.elf is ~7KB

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

Did you follow the wiki's recommendations?
https://github.com/Proxmark/proxmark3/wiki/Windows

Jep I did.
But one question: I don't need to update the proxmark to the new CDC interface, right?

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

Your output say "Qt: Untested Windows version 6.2 detected!"...  if you are using the QT4.6.2 that is a strange output.

And what is the output from running the flash command?

regarding the CDC,  it depends on what kind of bootrom/fpga image you have on your pm3 device already.
If its an older not updated for a long time, you will need to make the transition to CDC.

If is a newer model like the pm3 rdv2,  its most likely its already on CDC.

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

How can I find the version of Qt used in the Mingw32 environment?

I added a path value to the right Qt bin-folder but didn't help.

Ouput flash command while holding down button:

Loading ELF file 'COM4'...

Output flash command when I release the button while it tried to flash:

Error while reading ELF file header
Error while loading COM4

See youtube video

Output hw ver Proxmark:

proxmark3> hw ver
[[[ Cached information ]]]

Prox/RFID mark3 RFID instrument
bootrom: master/v2.2 2015-07-31 11:28:11
os: master/v2.2 2015-07-31 11:28:12
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/06/22 at 21:47:54

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 162219 bytes (62%). Free: 99925 bytes (38%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

Last edited by Vinnie (2016-03-25 18:29:46)

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

If I run moc.exe -v in my dev environment it says:

pm3 ~$ moc.exe -v
Qt: Untested Windows version 6.2 detected!
Qt Meta Object Compiler version 62 (Qt 4.6.2)

Edit: I looked it up and it's because the old Qt doesn't recognize the newer OS's.
It's only a warning.

Last edited by Vinnie (2016-03-25 18:37:57)

Vinnie

Contributor

From: Belgium

Registered: 2016-03-24

Posts: 39

Re: [Resolved] Flashing bootrom problem (Windows 10 x64)

SOLVED

Command had to be:
client/flasher.exe COM4 -b bootrom/obj/bootrom.elf