Kubuntu 32bit Installation / Proxmark wont communicate

ZaZaKodes · 2015-10-04 22:06:59

HI there,

I have spent about 16 hours trying to figure out why my PM3 won't communicate with my computer. I am completely new to this controller and Linux, and have a basics level understanding to command line, I received my PM3 2 days ago and I am using a Panasonic Toughbook CF-18. I decided it would be best to use Kubuntu on this laptop.

I installed following https://code.google.com/p/proxmark3/wiki/Linux and use the devkitARM for a 32 bit system. Everything worked until i got to running dmesg.

It wrote a lot of script, far more than I have found in any questions to this similar problem. I have found similar problems but when I run the same trouble shooting, stilll nothing happens.

this post is the most similar to my problem

http://www.rajatswarup.com/blog/tag/howto/

when I get to: make all, it ends with this

make[2]: Entering directory `/home/osiris/proxmark3/proxmark3/liblua'
make all SYSCFLAGS="-DLUA_USE_LINUX" SYSLIBS="-Wl,-E -ldl -lreadline"
make[3]: Entering directory `/home/osiris/proxmark3/proxmark3/liblua'
gcc -O2 -Wall -DLUA_COMPAT_ALL -DLUA_USE_LINUX -c -o lapi.o lapi.c
make[3]: gcc: Command not found
make[3]: *** [lapi.o] Error 127
make[3]: Leaving directory `/home/osiris/proxmark3/proxmark3/liblua'
make[2]: *** [linux] Error 2
make[2]: Leaving directory `/home/osiris/proxmark3/proxmark3/liblua'
make[1]: *** [lua_build] Error 2
make[1]: Leaving directory `/home/osiris/proxmark3/proxmark3/client'
make: *** [client/all] Error 2

I have tried as much as I can, being a complete noob, I have exhausted all avenues. If anyone could help me, I would be grateful, step by step even better.

much love!

meter · 2015-10-05 10:38:24

I should install gcc on your ubuntu. Exec this command

sudo apt-get install build-essential

and should solve.

Also version of gcc ARM is important
I'm using this and I don't have issue. With gcc 4.7 I have some issues with bootloader.
I will try gcc 4.9 and 5.0 one day for now is better 4.8

Last edited by meter (2015-10-05 10:45:13)

ZaZaKodes · 2015-10-13 19:07:30

Thank you, will try!

ZaZaKodes · 2015-10-15 03:45:49

Hey Meter,

Thank you for the help!

In dmesg my PM3 now reads as: proxmark.org and not Jwesthues after following your instructions.
Although my PM3 led stays Red and Amber and clicks green for a smidge after 20 seconds or so.
When I try the flash it just does the dots......... I can't figure it out.
lol this has been a two week ordeal, but great learning and I appreciate it a lot actually,
by any chance do you have any other suggestions?

I am a noob and still learning so if you do have any step by step that would be great when you or anyone else that can help.

Thank you again.

iceman · 2015-10-15 05:36:52

can you run "hw ver" and paste here?

meter · 2015-10-15 09:01:25

I think the PM3 loop in bootloader mode, something is wrong in your flash. Try this:

dettach PM3 from USB execute this command

sudo tail -f /var/log/messages

type some ENTER key just for make an empty space in your console
attach PM3 to USB wait all leds do them game and rele do "click/clack" post here all new lines appear in console after the empty space.
So we can understand if your bootloader is HID(old version) or CDC (new version).

or you can read this wiki

ZaZaKodes · 2015-10-16 16:36:07

When I entered the sudo tail - /var/log/messages
this is the response that I received.

tail: cannot open ‘/var/log/messages’ for reading: No such file or directory

ZaZaKodes · 2015-10-16 16:39:57

this is the output that I received when I put the dmesg.

[46352.825621] sd 0:0:0:0: [sda] Starting disk
[46352.850314] rtc_cmos 00:03: System wakeup disabled by ACPI
[46352.870331] serial 00:06: activated
[46352.893386] serial 00:07: activated
[46353.721586] PM: resume of devices complete after 1119.252 msecs
[46353.721789] PM: Finishing wakeup.
[46353.721792] Restarting tasks ... done.
[46354.780406] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[46354.780416] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[46354.780423] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[46354.796646] ata1.00: configured for UDMA/100
[52475.560092] usb 2-2: new full-speed USB device number 2 using uhci_hcd
[52475.734152] usb 2-2: New USB device found, idVendor=2d2d, idProduct=504d
[52475.734170] usb 2-2: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[52475.734181] usb 2-2: Manufacturer: proxmark.org
[52476.694148] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[52476.703221] usbcore: registered new interface driver cdc_acm
[52476.703231] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

ZaZaKodes · 2015-10-16 16:59:04

When I entered
Use the older version of the flasher to update the proxmark:

[== Undefined ==]
 cd client/hid-flasher
 make
 ./flasher -b ../../bootrom/obj/bootrom.elf
 ./flasher ../../armsrc/obj/fullimage.elf 
 cd ../..

this is what outputs:

Could not open file '../../bootrom/obj/bootrom.elf': No such file or directory
Error while loading ../../bootrom/obj/bootrom.elf

ZaZaKodes · 2015-10-16 17:01:21

I have followed every direction to the letter, I love the learning! but is there a way that I can team view my computer?

ZaZaKodes · 2015-10-16 17:13:32

I went to the proxmark3 folder and said make and now

cd client/hid-flasher
 make
 ./flasher -b ../../bootrom/obj/bootrom.elf
 ./flasher ../../armsrc/obj/fullimage.elf 
 cd ../..

ZaZaKodes · 2015-10-16 17:26:40

Now when I try to flash this is what I get.

sudo ./flasher -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 (0x00000b88->0x00000b88) [RWX] @0x298
Attempted to write bootloader but bootloader writes are not enabled

Last edited by ZaZaKodes (2015-10-16 17:28:19)

iceman · 2015-10-16 23:08:07

ok, so you flashed the bootrom with the old hid-flasher.
now you need to flash the fullimage with the new flasher..

/client/flasher com2 /armsrc/obj/fullimage.elf

or something like that...

meter · 2015-10-16 23:50:47

or better for him

from client dir

./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf

if you receive the error No such file or directory, you should compile before with command make at top of directory.

Proxmark3 community

Announcement

#1 2015-10-04 22:06:59

Kubuntu 32bit Installation / Proxmark wont communicate

#2 2015-10-05 10:38:24

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#3 2015-10-13 19:07:30

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#4 2015-10-15 03:45:49

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#5 2015-10-15 05:36:52

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#6 2015-10-15 09:01:25

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#7 2015-10-16 16:36:07

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#8 2015-10-16 16:39:57

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#9 2015-10-16 16:59:04

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#10 2015-10-16 17:01:21

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#11 2015-10-16 17:13:32

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#12 2015-10-16 17:26:40

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#13 2015-10-16 23:08:07

Re: Kubuntu 32bit Installation / Proxmark wont communicate

#14 2015-10-16 23:50:47

Re: Kubuntu 32bit Installation / Proxmark wont communicate

Board footer