Proxmark3 community

jpsmith888

Contributor

Registered: 2017-11-09

Posts: 7

Win32 error 998 Errors in "make clean && make all"

Hello,

I am working with a Proxmark3 RDV:

Prox/RFID mark3 RFID instrument
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:09
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: 169916 bytes (32%). Free: 354372 bytes (68%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> hw ver
[[[ Cached information ]]]

Prox/RFID mark3 RFID instrument
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:09
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: 169916 bytes (32%). Free: 354372 bytes (68%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

I followed the windows setup instructions (using the git repository from nov. 2017) and when I went opened runme.bat and ran "make clean && make all" things seemed to mostly be working except the following errors:

make[1]: Leaving directory `/pm3/client'
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
      3 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
5054959 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
10101083 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
15144305 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
20197832 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
25244710 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
30295618 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
35736784 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
40785016 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
45834985 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
50891815 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
56491856 [main] perl 21708 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
56546922 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
61593892 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
66622344 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
71667746 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
76723792 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
81750621 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
86806052 [main] perl 19012 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 19012, Win32 error 998
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

...

make[1]: Leaving directory `/pm3/bootrom'
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
      6 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
5067453 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
10251172 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
15299493 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
20335953 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
25375147 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
30421178 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
35472570 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
40517976 [main] perl 17620 child_copy: linked dll data write copy failed, 0x142000..0x142370, done 0, windows pid 17620, Win32 error 998
45645461 [main] perl 22092 _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 -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
../client/fpga_compress ../fpga/fpga_lf.bit ../fpga/fpga_hf.bit obj/fpga_all.bit.z
compressed 84672 input bytes to 34652 output bytes
arm-none-eabi-objcopy -O elf32-littlearm -I binary -B arm --prefix-sections=fpga_all_bit obj/fpga_all.bit.z obj/fpga_all.o

...

gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3  -o mfkey32 crypto1.o crapto1.o parity.o util_posix.o mfkey.o mfkey32.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3  -o mfkey64 crypto1.o crapto1.o parity.o util_posix.o mfkey.o mfkey64.c
make[1]: Leaving directory `/pm3/tools/mfkey'
pm3 ~$

These errors have made me too nervous to flash it to the latest firmware. However, many of the functions still seem work. So my questions are:

1.) Does anyone know how to resolve the win32 998 errors?

2.) Should I proceed with flashing even with these errors?

3.) Is it a terrible idea to not flash?

P.S. I saw one other post about this error and the fix was suggested to go into the msys folder and run the msys.bat file and execute "make clean && make all" there. I tried this and still got the errors.

Thanks to anyone who replies!

Charlie

Contributor

Registered: 2017-01-27

Posts: 129

Re: Win32 error 998 Errors in "make clean && make all"

Any luck fixing this issues?

I'm having the same issue on my new Windows 10 machine. I confirmed my user is the Admin and have full access to the proxspace folder.

Skeltek

Contributor

Registered: 2017-12-31

Posts: 19

Re: Win32 error 998 Errors in "make clean && make all"

Never heard about those errors, but they should have prevented the compiler from making a binary from the source files. So it did not make any 'software' from the source text, alas there would not be any new version compiled which you could flash onthe PM3.
Maybe best wait for someone else to answer. Getting late here, cant google now... need sleep.

piwi

Contributor

Registered: 2013-06-04

Posts: 704

Re: Win32 error 998 Errors in "make clean && make all"

perl is not working in your proxspace. I suggest that you open an issue at https://github.com/Gator96100/ProxSpace

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: Win32 error 998 Errors in "make clean && make all"

i have had the same problem,   its not gator96100 fault,  its mingw and perl on windows which doesn't like memory addressing.
So don't open a issue on gator96100 GH...

rkblackfire

Contributor

Registered: 2018-01-11

Posts: 3

Re: Win32 error 998 Errors in "make clean && make all"

Hello,

I had the same error. Looking at the error log You see

../tools/mkversion.pl .. > version.c || cp ../common/default_version.c version.c

The error is only thrown there, so in pm3/tools/mkversion.pl comment the lines 14,15 and 19:
#my $gitversion = `git describe --dirty`;
#my $gitbranch = `git rev-parse --abbrev-ref HEAD`;

#my $fullgitinfo = $gitbranch . '/' . $gitversion;

and change line 39 to
"no GIT info",

after that, all runs fine.

Yes, it only hides the problem but if you git yourself it's useable.

Richard.

Charlie

Contributor

Registered: 2017-01-27

Posts: 129

Re: Win32 error 998 Errors in "make clean && make all"

i have had the same problem,   its not gator96100 fault,  its mingw and perl on windows which doesn't like memory addressing.
So don't open a issue on gator96100 GH...

does the problem only seem to happen in Win 10?

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: Win32 error 998 Errors in "make clean && make all"

nay,  I got in in the mingw on both win10 and win7.

possible solution:
try modifying the runme.bat file to this http://www.proxmark.org/forum/viewtopic … 943#p30943