[SOLVED][RDV4] not understanding setup/compile/flashing

fazer · 2019-04-09 10:02:13

Hello, I just received my proxmark3 rdv4 , I'v l'upgrade & 2 leds red (a & c) light , I'v os kali linux inside , So I installed yesterday ubuntu 18.04 on my PC next to kali. After installation always the same & by Hazar I came across this message from Iceman 1001 of 16/07/2017 (ref:513c6c9) a big thanks to him because yesterday I was able to find my proxmark3 OK .
Good day to you.
Hello again here is my update info, I see the hf ok instead the Lf the date is lower? . Thank you good day
#db# Time elapsed: 1500ms
#db# Bytes transferred: 951296
#db# USB Transfer Speed PM3 -> Client = 634197 Bytes/s
#db# Various
#db# MF_DBGLEVEL........2
#db# ToSendMax..........-1840494903
#db# ToSendBit..........0
proxmark3> hw version
Prox/RFID mark3 RFID instrument
bootrom: master/v3.1.0-83-g1f61f19-suspect 2019-04-08 16:07:38
os: master/v3.1.0-83-g1f61f19-suspect 2019-04-08 16:07:38
fpga_lf.bit built for 2s30vq100 on 2015/03/06 at 07:38:04
fpga_hf.bit built for 2s30vq100 on 2019/03/20 at 08:08:07
SmartCard Slot: available

uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 207094 bytes (40%). Free: 317194 bytes (60%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>

Last edited by fazer (2019-04-09 10:22:46)

iceman · 2019-04-09 10:42:16

You should read https://github.com/RfidResearchGroup/pr … uctions.md for Kali / Arch linux installations.

Run and post the output from these commands.

hw status
hw tune

fazer · 2019-04-09 11:26:22

Hi Iceman, many thanks ok run and back avec info (status and tune).

fazer · 2019-04-09 12:31:15

to Iceman 1001, i'v a problem ?
pascal@pascal-Inspiron-660:~$ git clone https://github.com/iceman1001/proxmark3.git
fatal: le chemin de destination 'proxmark3' existe déjà et n'est pas un répertoire vide.
pascal@pascal-Inspiron-660:~$ git pull
fatal: ni ceci ni aucun de ses répertoires parents n'est un dépôt git : .gi
How to purge the git sweater?,I also look for my own thanks again for your help

Last edited by fazer (2019-04-09 12:33:46)

iceman · 2019-04-09 13:23:04

I suggest you learn git by finding a howto guide

fazer · 2019-04-09 19:57:20

Good-evening Iceman, thank a lot .

[ CLIENT ]
client: iceman build for RDV40 with flashmem; smartcard;

[ ARM ]
bootrom: iceman/master/8c4f8eae 2019-04-09 20:52:47
os: iceman/master/8c4f8eae 2019-04-09 20:52:57

[ FPGA ]
LF image built for 2s30vq100 on 2018/ 9/ 8 at 13:57:51
HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23

[ Hardware ]
--= uC: AT91SAM7S512 Rev B
--= Embedded Processor: ARM7TDMI
--= Nonvolatile Program Memory Size: 512K bytes, Used: 252013 bytes (48%) Free: 272275 bytes (52%)
--= Second Nonvolatile Program Memory Size: None
--= Internal SRAM Size: 64K bytes
--= Architecture Identifier: AT91SAM7Sxx Series
--= Nonvolatile Program Memory Type: Embedded Flash Memory

fazer · 2019-04-10 11:33:46

Hi Iceman, i'v another question if you wish ( what the best Os to work proxmark3, kali linux , ubuntu , windob 10 ) . Thanks and have a nice day .
Fazer

fazer · 2019-06-16 12:49:24

Hello, after having made a bet open git pull and install on my proxmark3 rdv4 now the four red leds remain lit. I put the order. thank you good Sunday.

[+] Loading ELF file armsrc/obj/fullimage.elf
[+] Loading usable ELF segments:
[+] 0 : V 0x00102000 P 0x00102000 (0x00039b40->0x00039b40) [R X] @0x94
[+] 1 : V 0x00200000 P 0x0013bb40 (0x0000135c->0x0000135c) [RW ] @0x39bd4
[=] Note: Extending previous segment from 0x39b40 to 0x3ae9c bytes

[+] Waiting for Proxmark3 to appear on /dev/ttyACM0
..............................Found

[+] Flashing...

[+] Writing segments for file: bootrom/obj/bootrom.elf
[+] 0x00100000..0x001001ff [0x200 / 1 blocks]
. OK
[+] 0x00100200..0x00100f7f [0xd80 / 7 blocks]
.[!] Received packet OLD frame payload error too short? 406/534
[=] You can cancel this operation by pressing the pm3 button
[!] Communicating with Proxmark3 device failed

it is serious doctor there is there a solution for this problem. thank you so much.

iceman · 2019-06-16 17:24:48

looks like it failed the fullimage flash.

try one hand button trick.
unplug device, press and hold button (don't let go), flash fullimage, first when flashing finished and you get OK, you can release button.

Restart yr device and it should work just fine.

fazer · 2019-06-16 20:46:29

Hello Iceman, I will try this procedure thank you again good evening.

fazer · 2019-06-16 21:16:53

Re Iceman,
./client/flasher /dev/ttyACM0 armsrc/obj/fullimage.elf
[+] Loading ELF file armsrc/obj/fullimage.elf
[+] Loading usable ELF segments:
[+] 0 : V 0x00102000 P 0x00102000 (0x00039b40->0x00039b40) [R X] @0x94
[+] 1 : V 0x00200000 P 0x0013bb40 (0x0000135c->0x0000135c) [RW ] @0x39bd4
[=] Note: Extending previous segment from 0x39b40 to 0x3ae9c bytes

[+] Waiting for Proxmark3 to appear on /dev/ttyACM0
............................................................
[!] ERROR: invalid serial port /dev/ttyACM0

[!!] Could not find Proxmark3 on /dev/ttyACM0 .
Thanks good-evening

fazer · 2019-06-17 10:57:03

Hello Iceman, I have more USB connection with the proxmark3, I order a J-link adapter at Lab401 & I must receive the standadalone kit (bluetooth + battery) a question do you believe when bluetooth your procedure would be it not easier for me before doing a jtag. I have an Ulink 2 that served me before & V4 pirate bus to do this manipulation. thank you in advance a good week.

mwalker · 2019-06-17 11:05:37

When pressing and holding the button then plugging into the computer (still holding the button) see if the proxmark was assigned a different com port. If so, while still holding the button, try to flash the fullimage.elf again but using the new com port.

fazer · 2019-06-17 14:52:34

Hi Mwalker, ok thanks i will try this procedure .

fazer · 2019-06-18 19:42:05

Good evening, I tried the procedure without success on different bones, Ubuntu, Kali, Windows7 and 10 on laptop. I'm going to have to believe I have a jtag. I looked on the net there is procedure but not seen for rdv4, there is there a link for this procedure, I saw in proxmark / tools / tools for the procedure. Thanks again for your helps good evening.

fazer · 2019-07-11 20:18:59

Hi Iceman, here we are all in order.Thank you for the joob good evening.

pi@raspberrypi:~/proxmark3/client $ ./proxmark3 /dev/rfcomm0

██████╗ ███╗ ███╗ ████╗ ...iceman fork
██╔══██╗████╗ ████║ ══█║ ...dedicated to RDV40
██████╔╝██╔████╔██║ ████╔╝
██╔═══╝ ██║╚██╔╝██║ ══█║ iceman@icesql.net
██║ ██║ ╚═╝ ██║ ████╔╝ https://github.com/rfidresearchgroup/proxmark3/
╚═╝ ╚═╝ ╚═╝ ╚═══╝ pre-release v4.0

Support iceman on patreon, https://www.patreon.com/iceman1001/

[=] Using UART port /dev/rfcomm0
[=] Communicating with PM3 over FPC UART
[=] PM3 UART serial baudrate: 115200

[ Proxmark3 RFID instrument ]

[ CLIENT ]
client: RRG/Iceman
compiled with GCC 6.3.0 20170516

[ PROXMARK RDV4 ]
external flash: present
smartcard reader: present

[ PROXMARK RDV4 Extras ]
FPC USART for BT add-on support: present

[ ARM ]
bootrom: RRG/Iceman/master/c388f66b-dirty-unclean 2019-07-10 16:35:47
os: RRG/Iceman/master/c388f66b-dirty-unclean 2019-07-10 16:35:58
compiled with GCC 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]

[ FPGA ]
LF image built for 2s30vq100 on 2019/ 4/18 at 9:35:32
HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23

[ Hardware ]
--= uC: AT91SAM7S512 Rev B
--= Embedded Processor: ARM7TDMI
--= Nonvolatile Program Memory Size: 512K bytes, Used: 251494 bytes (48%) Free: 272794 bytes (52%)
--= Second Nonvolatile Program Memory Size: None
--= Internal SRAM Size: 64K bytes
--= Architecture Identifier: AT91SAM7Sxx Series
--= Nonvolatile Program Memory Type: Embedded Flash Memory

[fpc] pm3 -->

iceman · 2019-07-13 10:31:47

Good thing you solved you problem. Looks like the blue shark is working.

I suggest you edit your first post and add the prefix [solved] to the title.

Proxmark3 community

Announcement

#1 2019-04-09 10:02:13

[SOLVED][RDV4] not understanding setup/compile/flashing

#2 2019-04-09 10:42:16

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#3 2019-04-09 11:26:22

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#4 2019-04-09 12:31:15

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#5 2019-04-09 13:23:04

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#6 2019-04-09 19:57:20

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#7 2019-04-10 11:33:46

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#8 2019-06-16 12:49:24

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#9 2019-06-16 17:24:48

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#10 2019-06-16 20:46:29

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#11 2019-06-16 21:16:53

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#12 2019-06-17 10:57:03

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#13 2019-06-17 11:05:37

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#14 2019-06-17 14:52:34

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#15 2019-06-18 19:42:05

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#16 2019-07-11 20:18:59

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

#17 2019-07-13 10:31:47

Re: [SOLVED][RDV4] not understanding setup/compile/flashing

Board footer