Proxmark3 community

CoolLink

Contributor

Registered: 2016-12-09

Posts: 31

What is the purpose of the ProxSpace Environment

I am still new and learning the fundamentals of the PM3. so far i can flash compiled firmware, run some of the hw, hf, data and lf commands with success. Read most of the manuals covering the PM3.

But i still can not figure out what's the importance of the ProxSpace environment folder? because even the runme.bat file i haven't used it at all.

can someone just help me understand the importance of the ProxSpace folder.

it will help in understanding the pm3 better.

thanks in advance

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: What is the purpose of the ProxSpace Environment

It contains the sourcecode and all stuff needed to compile the project on a windows platform via MINGW.

diaconom

Contributor

Registered: 2014-08-31

Posts: 16

Re: What is the purpose of the ProxSpace Environment

I'm trying to setup ProxSpace to compile the latest version of ProxMark3. Are the following messages normal?

I run make clean && make all and after normal prompts, I notice the following errors when trying to compile the bootrom:

make -C bootrom  all
make[1]: Entering directory `/pm3/bootrom'
make[1]: Leaving directory `/pm3/bootrom'
make[1]: Entering directory `/pm3/bootrom'
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c
      1 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
5164138 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
10248206 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
15331308 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
20416365 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
25505118 [main] perl 10140 child_copy: linked dll data write copy failed, 0x1E2000..0x1E2370, done 0, windows pid 10140, Win32 error 998
32897355 [main] perl 26412 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
34320825 [main] perl 24220 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)

.... the script also fails during the compile of armsrc and exists with an Error 2.

make -C armsrc  all
make[1]: Entering directory `/pm3/armsrc'
make[1]: Leaving directory `/pm3/armsrc'
make[1]: Entering directory `/pm3/armsrc'
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c
      2 [main] perl 12532 child_copy: linked dll data write copy failed, 0x1D2000..0x1D2370, done 0, windows pid 12532, Win32 error 998
5135023 [main] perl 12532 child_copy: linked dll data write copy failed, 0x1D2000..0x1D2370, done 0, windows pid 12532, Win32 error 998
10295621 [main] perl 12532 child_copy: linked dll data write copy failed, 0x1D2000..0x1D2370, done 0, windows pid 12532, Win32 error 998
15380117 [main] perl 12532 child_copy: linked dll data write copy failed, 0x1D2000..0x1D2370, done 0, windows pid 12532, Win32 error 998
20889571 [main] perl 12532 child_copy: linked dll data write copy failed, 0x1D2000..0x1D2370, done 0, windows pid 12532, Win32 error 998
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -DWITH_ISO14443a_StandAlone -DWITH_LF -DWITH_ISO15693 -DWITH_ISO14443a -DWITH_ISO14443b -DWITH_ICLASS -DWITH_LEGICRF -DWITH_HITAG  -DWITH_CRC -DON_DEVICE -DWITH_HFSNOOP -fno-strict-aliasing -ffunction-sections -fdata-sections -DZ_SOLO -DZ_PREFIX -DNO_GZIP -DZLIB_PM3_TUNED -I../zlib -mthumb -mthumb-interwork -o obj/version.o version.c
make[1]: *** No rule to make target `fpga_lf.bit', needed by `obj/fpga_all.bit.z'.  Stop.
make[1]: Leaving directory `/pm3/armsrc'
make: *** [armsrc/all] Error 2
pm3 ~$

Can anyone point me in the right direction to get this resolved? Thanks.

ntk

Contributor

Registered: 2015-05-24

Posts: 701

Re: What is the purpose of the ProxSpace Environment

unusual,

which perl version and which proxspace are you using , diaconom?

diaconom

Contributor

Registered: 2014-08-31

Posts: 16

Re: What is the purpose of the ProxSpace Environment

I have made sure I removed any Perl/GIT tools and reinstalled the "master" latest branch but still get the following errors.

I have also built a new clean Win7 VM environment but same issue.... (BTW, get a Perl.exe has stopped working 1/2 way through the errors)

pm3 ~$ perl -version

This is perl, v5.8.6 built for cygwin-thread-multi-64int

Copyright 1987-2004, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'.  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

pm3 ~$ cd bootrom/
pm3 ~/bootrom$ make
perl ../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c
      1 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
5021188 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
10032692 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
15044503 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
20058215 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
25070310 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
30083344 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
35095045 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
77760425 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
82772266 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
87785329 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
92796820 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
97810152 [main] perl 21420 child_copy: linked dll data write copy failed, 0x102000..0x102370, done 0, windows pid 21420, Win32 error 998
105792781 [main] perl 18392 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb -mthumb-interwork -o obj/version.o version.c
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb-interwork -o obj/ram-reset.o ram-reset.s
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb-interwork -o obj/flash-reset.o flash-reset.s
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb -mthumb-interwork -o obj/cmd.o ../common/cmd.c
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb -mthumb-interwork -o obj/usb_cdc.o ../common/usb_cdc.c
arm-none-eabi-gcc -c -I../include -I../common -Wall -Werror -pedantic -std=c99 -Os -I. -mthumb -mthumb-interwork -o obj/bootrom.o bootrom.c
arm-none-eabi-gcc -nostartfiles -nodefaultlibs -Wl,-gc-sections -n -Wl,-T,ldscript-flash,-Map,obj/bootrom.map -o obj/bootrom.elf obj/version.o obj/ram-reset.o obj/flash-reset.o obj/cmd.o obj/usb_cdc.o obj/bootrom.o -lgcc
arm-none-eabi-objcopy -Osrec --srec-forceS3 --strip-debug --no-change-warnings --change-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
pm3 ~/bootrom$

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: What is the purpose of the ProxSpace Environment

its an issue with perl and mingw/cygwin,  not with the proxmark development environment.  If you want some answers, I suggest start asking supportforums for mingw/perl. 

I also seen this error and I have not found an answer to it. Just some wage "its how memory is reserved when executing mingw programs like perl"...

jayc

Contributor

Registered: 2017-05-03

Posts: 26

Re: What is the purpose of the ProxSpace Environment

How I got around this with the help of @ntk go in deeper into your /proxspace/msys and run that .bat file. And do the same compile there "make clean all". That should work.