Proxmark3 developers 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.

#1 2020-08-01 00:52:58

BFreakout
Contributor
Registered: 2020-07-31
Posts: 4

ERROR: cannot communicate with the Proxmark

Hello Community,

I tried my new Proxmark3 on Windows 10 to get it working with ProxSpace.

In the end I finally managed to install a new bootrom and fullimage with pm3-flash-all. Then I would like to connect with the command pm3. It finds the port automatically and connects. Then I get an error message that communication is not working.

Then the device manager only shows my device under USB controller and that it would be an unknown device (error when requesting a device description). Windows only recognizes the device when I disconnect it from the USB and plug it in again with the button pressed (the blue and green flash light is on). I then installed the bootrom and fullimage again. It didn't help.

My terminal output:

$ runme64.bat
pm3 ~$ ./pm3-flash-all
[=] Session log C:\Users\Gregor\Documents\ProxSpace\pm3/.proxmark3/logs/log_20200730.txt
[+] About to use the following files:
[+]    C:\Users\Gregor\Documents\ProxSpace\pm3\client\../bootrom/obj/bootrom.elf
[+]    C:\Users\Gregor\Documents\ProxSpace\pm3\client\../armsrc/obj/fullimage.elf
[+] Waiting for Proxmark3 to appear on COM7
[|] 59 found
[=] Available memory on this board: 512K bytes

[=] Permitted flash range: 0x00100000-0x00180000
[+] Loading ELF file C:\Users\Gregor\Documents\ProxSpace\pm3\client\../bootrom/obj/bootrom.elf
[+] Loading usable ELF segments:
[+]    0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
[+]    1: V 0x00200000 P 0x00100200 (0x00000d50->0x00000d50) [R X] @0x298

[+] Loading ELF file C:\Users\Gregor\Documents\ProxSpace\pm3\client\../armsrc/obj/fullimage.elf
[+] Loading usable ELF segments:
[+]    0: V 0x00102000 P 0x00102000 (0x0003d788->0x0003d788) [R X] @0x94
[+]    1: V 0x00200000 P 0x0013f788 (0x00001964->0x00001964) [RW ] @0x3d81c
[=] Note: Extending previous segment from 0x3d788 to 0x3f0ec bytes

[+] Flashing...
[+] Writing segments for file: C:\Users\Gregor\Documents\ProxSpace\pm3\client\../bootrom/obj/bootrom.elf
[+]  0x00100000..0x001001ff [0x200 / 1 blocks]
OK
[+]  0x00100200..0x00100f4f [0xd50 / 7 blocks]
OK

[+] Writing segments for file: C:\Users\Gregor\Documents\ProxSpace\pm3\client\../armsrc/obj/fullimage.elf
[+]  0x00102000..0x001410eb [0x3f0ec / 505 blocks]
mm OK

[+] All done

Have a nice day!
pm3 ~$ ./pm3
[=] Session log C:\Users\Gregor\Documents\ProxSpace\pm3/.proxmark3/logs/log_20200730.txt
[=] Using UART port COM7
[!!] ERROR: cannot communicate with the Proxmark

pm3 ~$

Offline

#2 2020-08-04 13:53:12

BFreakout
Contributor
Registered: 2020-07-31
Posts: 4

Re: ERROR: cannot communicate with the Proxmark

I execute make PLATFORM=PM3OTHER clean && make PLATFORM=PM3OTHER all and ./pm3-flash-all - Now it´s work without problems.

Offline

Board footer

Powered by FluxBB