Proxmark3 community

Research, development and trades concerning the powerful Proxmark3 device.

Remember; sharing is caring. Bring something back to the community.


"Learn the tools of the trade the hard way." +Fravia

You are not logged in.

Announcement

Time changes and with it the technology
Proxmark3 @ discord

Users of this forum, please be aware that information stored on this site is not private.

#1 2011-06-24 18:50:29

amigu
Member
Registered: 2011-06-22
Posts: 5

Why not generate the "fpgaimage.s19" and "osimage.s19" files.

Hello,

I am just new to ProxMark3. I downloaded "2009.09.05.ProxSpace.zip" and updated it using SUV. Then I followed the "compiling.txt" instructions there. The following is what I got. The last 5 lines indicate there are two errors. Also this did not generate the "fpgaimage.s19" and "osimage.s19" files.  Can someone please let me know what is the problem?

C:\ProxSpace\pm3-20090905-r216>make clean
make -C bootrom clean
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
rm -rf obj/*.o
rm -rf obj/*.elf
rm -rf obj/*.s19
rm -rf obj/*.map
rm -rf obj/*.d
rm -rf version.c
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
make -C armsrc clean
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
rm -rf obj/*.o
rm -rf obj/*.elf
rm -rf obj/*.s19
rm -rf obj/*.map
rm -rf obj/*.d
rm -rf version.c
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
make -C client clean
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/client'
rm -f cli cli.exe flasher flasher.exe proxmark3 proxmark3.exe snooper snooper.ex
e obj/nonce2key/crapto1.o obj/nonce2key/crypto1.o obj/nonce2key/nonce2key.o obj/
mifarehost.o obj/crc16.o obj/iso14443crc.o obj/iso15693tools.o obj/data.o obj/gr
aph.o obj/ui.o obj/util.o obj/cmddata.o obj/cmdhf.o obj/cmdhf14a.o obj/cmdhf14b.
o obj/cmdhf15.o obj/cmdhflegic.o obj/cmdhficlass.o obj/cmdhfmf.o obj/cmdhw.o obj
/cmdlf.o obj/cmdlfem4x.o obj/cmdlfhid.o obj/cmdlfti.o obj/cmdparser.o obj/cmdmai
n.o obj/*.o *.o *.moc.cpp
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/client'


C:\ProxSpace\pm3-20090905-r216>make
make -C bootrom all
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c vers
ion.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I.
-mthumb -mthumb-interwork -o obj/version.o version.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I.
-mthumb-interwork -o obj/ram-reset.o ram-reset.s
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I.
-mthumb-interwork -o obj/flash-reset.o flash-reset.s
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I.
-mthumb-interwork -o obj/usb.o ../common/usb.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -I.
-mthumb-interwork -o obj/bootrom.o bootrom.c
arm-eabi-gcc -nostartfiles -nodefaultlibs -Wl,-gc-sections -n -Wl,-T,ldscript-fl
ash,-Map,obj/bootrom.map -o obj/bootrom.elf obj/version.o obj/ram-reset.o obj/fl
ash-reset.o obj/usb.o obj/bootrom.o -lgcc
arm-eabi-objcopy -Osrec --srec-forceS3 --strip-debug --no-change-warnings --chan
ge-addresses -0x100000 --change-start 0 --change-section-address .bss+0 --change
-section-address .data+0 --change-section-address .commonarea+0 obj/bootrom.elf
obj/bootrom.s19
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/bootrom'
make -C armsrc all
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
make[1]: Entering directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/version.o version.c
arm-eabi-objcopy -O elf32-littlearm -I binary -B arm --redefine-sym _binary____f
pga_fpga_bit_start=_binary_fpga_bit_start --redefine-sym _binary____fpga_fpga_bi
t_end=_binary_fpga_bit_end --prefix-sections=fpga_bit  ../fpga/fpga.bit obj/fpga
.o
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/start.o start.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/iso15693.o iso15693.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/iso15693tools.o ../common/iso15693tools.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/lfops.o lfops.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/hitag2.o hitag2.c
arm-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=gnu99 -O2
-DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -I. -mthumb -mthumb-
interwork -o obj/appmain.o appmain.c
appmain.c: In function 'MeasureAntennaTuning':
appmain.c:189:9: error: variable 'ptr' set but not used [-Werror=unused-but-set-variable]
cc1.exe: all warnings being treated as errors

make[1]: *** [obj/appmain.o] Error 1
make[1]: Leaving directory `/c/ProxSpace/pm3-20090905-r216/armsrc'
make: *** [armsrc/all] Error 2

Offline

#2 2011-06-26 03:02:20

0xFFFF
Administrator
From: Vic - Australia
Registered: 2011-05-31
Posts: 632

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

Hi amigu,

Have a look at merlok's instructions...
http://www.proxmark.org/forum/viewtopic.php?id=833
post #4

Regards,

-0xFFFF

Offline

#3 2011-06-26 19:04:38

uberdude
Contributor
Registered: 2011-05-24
Posts: 17

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

I've been having a similar problem. I followed the instructions up to step 8. I was able to build the bootrom.s19, fpgaimage.s19 and os.s19 and update my pm3 just fine. I used an older version of the client (before I changed the pm3 to a libusb device) and everything looks fine.

However, I haven't been able to open the client. Every time I double click on the client (C:\Proxmark\Proxspace\pm3\client\proxmark3.exe) I get an error that says "This application has failed to start because QtCore4.dll was not found. Re-installing the application may fix this problem."

I've tried re-installing and making all again, but that doesn't seem to fix the problem. Additionally, in \Qt\4.6.2\bin, the QtCore4.dll file is clearly there.

I don't understand whats going on here. I'm much more a hardware and embedded systems guy than a software guy. Any help would be greatly appreciated. Thanks

Offline

#4 2011-06-26 21:04:27

thefkboss
Contributor
Registered: 2008-10-26
Posts: 198

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

you have to copy QtCore4.dll to client folder

Offline

#5 2011-06-26 22:29:30

uberdude
Contributor
Registered: 2011-05-24
Posts: 17

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

Thanks, figured that out on my own, seems like theres a PATH problem in the software. Not sure why that was necessary, but its up and running and everything seems to be working fine.

Offline

#6 2011-06-27 18:06:09

amigu
Member
Registered: 2011-06-22
Posts: 5

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

Hello everyone,

Thanks for your help. Now I am able to generate all the .s19 files.

uberdude, I have the same problem as you now, i.e. the client (C:\Proxmark\Proxspace\pm3\client\proxmark3.exe) would not start.

I double clicked proxmark3.exe. Then I got an error:
"The procedure entry point _Z13qFlagLocationPKc could not be located in the dynamic link library QtCore4.dll".

I have added the "C:\ProxSpace_new\Qt\4.6.2\bin" to system PATH. But it does not help. Does anyone or, uberdude, please let me know how this problem can be solved?

Thanks!

Offline

#7 2011-06-28 00:20:06

uberdude
Contributor
Registered: 2011-05-24
Posts: 17

Re: Why not generate the "fpgaimage.s19" and "osimage.s19" files.

Amigu,

I tried adding stuff to the system PATH but that didn't help anything, I think its some sort of software PATH problem.

Anyway, I copied all 3 files from \Qt\4.6.2\bin into the client folder.

Then I got another .dll error and copied all the files from that folder (I don't recall which folder and I'm on a different computer now) into the client folder. Everything seems to be working fine after I did that. Its a dirty solution but it works...

Offline

Board footer

Powered by FluxBB