Having trouble trying to update RDV2 using Kali

KinnyAdelaide · 2018-12-05 11:02:51

Hi all,

I am trying to upgrade but couldnt. What I did play by play was :

1. I held down the button.
2. Connected the cable.
3. Issued the dmesg command.
4. Issued the flasher and bootrom command.

As you can see below, I couldnt go any further after it failed to send bytes.

 [ 1698.347925] usb 1-4: new full-speed USB device number 57 using xhci_hcd
[ 1703.475372] usb 1-4: New USB device found, idVendor=2d2d, idProduct=504d
[ 1703.475375] usb 1-4: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[ 1703.475377] usb 1-4: Manufacturer: proxmark.org
[ 1703.475575] usb 1-4: ep 0x83 - rounding interval to 1024 microframes, ep desc says 2040 microframes
[ 1703.475971] cdc_acm 1-4:1.0: ttyACM0: USB ACM device
root@KittyIsFurious:~/pm3/proxmark3/client# ./flasher /dev/ttyACM0 -b ../bootrom/obj/bootrom.elf
Loading ELF file '../bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000c84->0x00000c84) [R X] @0x298

Waiting for Proxmark to appear on /dev/ttyACM0 .
 Found.
Sending bytes to proxmark failed          
Waiting for a response from the proxmark...          
You can cancel this operation by pressing the pm3 button          
^C
root@KittyIsFurious:~/pm3/proxmark3/client# ./proxmark3 ./dev/ttyacm0
ERROR: invalid serial port
proxmark3>

Any help is very much appreciated! Thanks

iceman · 2018-12-05 11:22:35

....kali / archlinux ppl
did you follow the instructions on wiki https://github.com/Proxmark/proxmark3/wiki/Kali-Linux ?

possible error
if device gets disconnected while getting enumerated, it is usally the modem-manager which are spooking. Some users has tried killing it with some success. A more permanent solution must be found for Kali users.

KinnyAdelaide · 2018-12-05 12:02:40

yes i did, was following that guide trying to set up.

The thing is I tried to kill that modem pid but it keeps disappearing, changing pid numbers.

Thanks

szymonunion · 2018-12-05 14:42:56

Kinny,

why killing <PID> if You can do:

sudo apt-get remove modemmanager (or sthg similar) ?

KinnyAdelaide · 2018-12-05 14:45:14

szymonunion wrote:

Kinny,
why killing <PID> if You can do:
sudo apt-get remove modemmanager (or sthg similar) ?

thanks i will try that when i can.

KinnyAdelaide · 2018-12-05 14:50:00

i switched back to my WIN 7, followed the steps again, set up proxspace, fresh git and files.

After hours of trying to get it work, it stops detecting pm3 when it got to writing [0xc84 / 7 blocks] while my finger was still holding down on the button.

Subsequently, all four LED are lit A, B, C and D. STD is on but i think that is saying the battery is fully charged. Windows also stop installing the driver as I can see it became unknown device in device manager.

Thanks in advance!

pm3 ~$ ./client/flasher com17 -b ./bootrom/obj/bootrom.elf
Loading ELF file './bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000c84->0x00000c84) [R X] @0x298

Waiting for Proxmark to appear on com17 .
 Found.

Flashing...
Writing segments for file: ./bootrom/obj/bootrom.elf
 0x00100000..0x001001ff [0x200 / 1 blocks]. OK
 0x00100200..0x00100e83 [0xc84 / 7 blocks]Waiting for a response from the proxma
rk...
You can cancel this operation by pressing the pm3 button
pm3 ~$ ./client/proxmark3.exe ./com17
ERROR: invalid serial port
proxmark3>

iceman · 2018-12-05 15:12:51

yuk... Failed bootrom flash usually mean you will need to jtag recover it. There is countless guides about it, read up on Wiki first.

KinnyAdelaide · 2018-12-08 03:59:46

iceman wrote:

yuk... Failed bootrom flash usually mean you will need to jtag recover it. There is countless guides about it, read up on Wiki first.

Hi iceman,

Im not quite a hardware person, is there any video that shows how to connect the segger j link or other jtags to pm3 rdv2?

I hope that i do not need to solder it as i dont have that nor the knowledge and yeah i want to get a clear picture of what i have to do before buying a jtag.

Thanks

iceman · 2018-12-08 08:13:49

as mentioned, plenty of posts, threads, blogs on how to jtag ... Just use jumper wires and you can stay away from soldering

KinnyAdelaide · 2018-12-17 08:08:56

i tried 200 and it does not connect too.

 Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>exec device = AT91SAM7S256
ERROR while parsing value for IRPre. Using default: -1.
ERROR while parsing value for DRPre. Using default: -1.
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>auto
Device "AT91SAM7S256" selected.


Connecting to target via JTAG
Cannot connect to target.
J-Link>

Last edited by KinnyAdelaide (2018-12-17 08:11:18)

KinnyAdelaide · 2018-12-17 09:08:43

Proxmark3 community

Announcement

#1 2018-12-05 11:02:51

Having trouble trying to update RDV2 using Kali

#2 2018-12-05 11:22:35

Re: Having trouble trying to update RDV2 using Kali

#3 2018-12-05 12:02:40

Re: Having trouble trying to update RDV2 using Kali

#4 2018-12-05 14:42:56

Re: Having trouble trying to update RDV2 using Kali

#5 2018-12-05 14:45:14

Re: Having trouble trying to update RDV2 using Kali

#6 2018-12-05 14:50:00

Re: Having trouble trying to update RDV2 using Kali

#7 2018-12-05 15:12:51

Re: Having trouble trying to update RDV2 using Kali

#8 2018-12-08 03:59:46

Re: Having trouble trying to update RDV2 using Kali

#9 2018-12-08 08:13:49

Re: Having trouble trying to update RDV2 using Kali

#10 2018-12-17 08:08:56

Re: Having trouble trying to update RDV2 using Kali

#11 2018-12-17 09:08:43

Re: Having trouble trying to update RDV2 using Kali

Board footer