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

Announcement

Time changes and with it the technology
Proxmark3 @ discord

Users of this forum, please be aware that information stored on this site is not private.

Pages: 1

#1 2019-10-21 18:48:35

Hala
Contributor
Registered: 2019-09-11
Posts: 4

[SOLVED] Flashing to newest firmware issue

Hello...

I was trying to to flash the PM to the newest  version from RRG\iceman repo,  however I got the following:

[!!] Note: Your bootloader does not understand the new CHIP_INFO command           
[!!] It is recommended that you first update your bootloader alone,           
[!!] reboot the Proxmark3 then only update the main firmware

After searching, I tried flashing the booloader alone and it was successful. However, when I tried running the client I got: 


 unknown command:: 0x61334d50[!!] ERROR: cannot communicate with the Proxmark

I realized later that the device is not enumerated correctly and it gets disconnected even though I removed ModemManager. After searching here and there I tried button trick to flash the device as follows:

  1. press button and keep it pressed (IMPORTANT)

  2. plug in device

  3. run flash command sudo client/flasher /dev/ttyACM0 armsrc/obj/fullimage.elf

  4. wait until flash is finished.

  5. release button.

And the method was successful, but when I unplugged and re plugged it again, ran the client, it could not find the device on the port. So I checked, the enumeration problem still presists.

What am I missing here or doing wrong? yikes


I need help as this is maybe the third time this happens.  yikes

Your help is much appreciated. Thanks! big_smile

Last edited by Hala (2019-10-22 11:03:07)

Offline

#2 2019-10-21 19:32:40

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

That would be the correct way to update it.   However did you compile the repo for your device?  If you have a RDV4, nothing extra to do,   if you have other proxmark3 device you will need to follow instructions https://github.com/RfidResearchGroup/pr … ameters.md

Offline

#3 2019-10-22 11:02:41

Hala
Contributor
Registered: 2019-09-11
Posts: 4

Re: [SOLVED] Flashing to newest firmware issue

Yes its not an RDV4, I missed that! Followed the instructions in the link and It's working now, thanks a lot!

Offline

#4 2019-11-28 22:06:48

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

Hi all,

I have exactly the same problem .... bit it isn't solved by configuring a Makefile.platform in the proxmark3 directory with PLATFORM=PM3OTHER.
With button pushed during plugging and holding the button it seems that the flashing went well:

~/proxmark3$ pm3-flash-
pm3-flash-all        pm3-flash-bootrom    pm3-flash-fullimage  
ralf@LaptopS:~/proxmark3$ pm3-flash-bootrom 
[=] Waiting for Proxmark3 to appear...
[=] Session log /home/john/.proxmark3/log_20191128.txt
[+] About to use the following file:          
[+]     /usr/local/bin/../share/proxmark3/firmware/bootrom.elf          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
.Found           
[=] Available memory on this board: 512K bytes
          
[=] Permitted flash range: 0x00100000-0x00180000          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/bootrom.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00100200 (0x00000de0->0x00000de0) [R X] @0x298          
          
          
[+] Flashing... 
          
[+] Writing segments for file: /usr/local/bin/../share/proxmark3/firmware/bootrom.elf          
[+]  0x00100000..0x001001ff [0x200 / 1 blocks]          
. OK           
[+]  0x00100200..0x00100fdf [0xde0 / 7 blocks]          
....... OK           

          
[+] All done.           

Have a nice day!          
~/proxmark3$ pm3-flash-fullimage 
[=] Waiting for Proxmark3 to appear...
[=] Session log /home/john/.proxmark3/log_20191128.txt
[+] About to use the following file:          
[+]     /usr/local/bin/../share/proxmark3/firmware/fullimage.elf          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
.Found           
[=] Available memory on this board: 512K bytes
          
[=] Permitted flash range: 0x00102000-0x00180000          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/fullimage.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00102000 P 0x00102000 (0x00040700->0x00040700) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00142700 (0x00001418->0x00001418) [RW ] @0x40794          
[=] Note: Extending previous segment from 0x40700 to 0x41b18 bytes          
          
          
[+] Flashing... 
          
[+] Writing segments for file: /usr/local/bin/../share/proxmark3/firmware/fullimage.elf          
[+]  0x00102000..0x00143b17 [0x41b18 / 526 blocks]          
.............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. OK           

          
[+] All done.           

Have a nice day!

After that, no communication with the PM3 is possible as there isn't the /devttyACM0 device.
Any hints will be appreciated !
Regards,

JD:

Offline

#5 2019-11-29 20:29:02

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

and which /dev/tty* do you get?

Offline

#6 2019-12-03 09:27:36

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

@ iceman:

There isn't any /dev/ttyACM* at all, i.e. nothing/none. Now I'm back on your (deprecated) iceman-fork. I was lucky to get it running (again).

Offline

#7 2019-12-03 16:55:53

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

is there a  /dev/ttyusb*

Offline

#8 2019-12-03 21:36:11

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

No, there isn't.

If I flash back to your deprecated fork, there is a /dev/ttyACM0. That is reproducible.

Last edited by JohnDoePM (2019-12-03 21:39:13)

Offline

#9 2019-12-03 21:55:36

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

I get the feeling your compilation with "PM3OTHER" fails and when you flash it on a device, it will not show up.  Your output from compiling and the Makefile.platform output would be nice to see.  You can use pastebin.com to share it with.

Offline

#10 2019-12-04 06:54:30

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

@ iceman:

That 's the output of the build process:

===================================================================
Platform name:     Proxmark3 Generic target
PLATFORM:          PM3OTHER
Platform extras:   No extra selected
Included options:  LF HITAG ISO15693 LEGICRF ISO14443b ISO14443a ICLASS FELICA NFCBARCODE HFSNIFF
Standalone mode:   LF_SAMYRUN
===================================================================
[*] MAKE client/clean
[*] MAKE bootrom/clean
[*] MAKE fpga_compress/clean
[*] MAKE armsrc/clean
[*] MAKE recovery/clean
[*] MAKE mfkey/clean
[*] MAKE nonce2key/clean

===================================================================
Platform name:     Proxmark3 Generic target
PLATFORM:          PM3OTHER
Platform extras:   No extra selected
Included options:  LF HITAG ISO15693 LEGICRF ISO14443b ISO14443a ICLASS FELICA NFCBARCODE HFSNIFF
Standalone mode:   LF_SAMYRUN
===================================================================
[*] MAKE client/all
[-] CC proxmark3.c
[-] CC uart/uart_posix.c
[-] CC uart/uart_win32.c
[-] CC ui.c
[-] CC ../common/commonutil.c
[-] CC util.c
[-] CC ../common/util_posix.c
[-] CC scandir.c
[-] CC ../common/crc16.c
[-] CC comms.c
[-] CC ../common/crapto1/crapto1.c
[-] CC ../common/crapto1/crypto1.c
[-] CC mifare/mifaredefault.c
[-] CC mifare/mfkey.c
[-] CC tea.c
[-] CC fido/additional_ca.c
[-] CC fido/cose.c
[-] CC fido/cbortools.c
[-] CC fido/fidocore.c
[-] CC crypto/asn1dump.c
[-] CC crypto/libpcrypto.c
[-] CC crypto/asn1utils.c
[-] CC cliparser/argtable3.c
[-] CC cliparser/cliparser.c
[-] CC loclass/cipher.c
[-] CC loclass/cipherutils.c
[-] CC loclass/ikeys.c
[-] CC loclass/elite_crack.c
[-] CC fileutils.c
[-] CC whereami.c
[-] CC mifare/mifarehost.c
[-] CC ../common/parity.c
[-] CC ../common/crc.c
[-] CC ../common/crc64.c
[-] CC ../common/legic_prng.c
[-] CC ../common/iso15693tools.c
[-] CC prng.c
[-] CC graph.c
[-] CC cmddata.c
[-] CC ../common/lfdemod.c
[-] CC emv/crypto_polarssl.c
[-] CC emv/crypto.c
[-] CC emv/emv_pk.c
[-] CC emv/emv_pki.c
[-] CC emv/emv_pki_priv.c
[-] CC emv/test/cryptotest.c
[-] CC emv/apduinfo.c
[-] CC emv/dump.c
[-] CC emv/tlv.c
[-] CC emv/emv_tags.c
[-] CC emv/dol.c
[-] CC emv/emvjson.c
[-] CC emv/emvcore.c
[-] CC emv/test/crypto_test.c
[-] CC emv/test/sda_test.c
[-] CC emv/test/dda_test.c
[-] CC emv/test/cda_test.c
[-] CC emv/cmdemv.c
[-] CC emv/emv_roca.c
[-] CC mifare/mifare4.c
[-] CC mifare/mad.c
[-] CC mifare/ndef.c
[-] CC cmdanalyse.c
[-] CC cmdhf.c
[-] CC cmdhflist.c
[-] CC aidsearch.c
[-] CC cmdhf14a.c
[-] CC cmdhf14b.c
[-] CC cmdhf15.c
[-] CC cmdhfepa.c
[-] CC cmdhflegic.c
[-] CC cmdhficlass.c
[-] CC cmdhfmf.c
[-] CC cmdhfmfu.c
[-] CC cmdhfmfp.c
[-] CC cmdhfmfhard.c
[-] CC hardnested/hardnested_bruteforce.c
[-] CC cmdhfmfdes.c
[-] CC cmdhftopaz.c
[-] CC cmdhffido.c
[-] CC cmdhffelica.c
[-] CC cmdhfthinfilm.c
[-] CC cmdhw.c
[-] CC cmdlf.c
[-] CC cmdlfawid.c
[-] CC cmdlfcotag.c
[-] CC cmdlfem4x.c
[-] CC cmdlffdx.c
[-] CC cmdlfguard.c
[-] CC cmdlfgallagher.c
[-] CC cmdlfhid.c
[-] CC cmdlfhitag.c
[-] CC cmdlfio.c
[-] CC cmdlfindala.c
[-] CC cmdlfjablotron.c
[-] CC cmdlfkeri.c
[-] CC cmdlfnexwatch.c
[-] CC cmdlfnedap.c
[-] CC cmdlfnoralsy.c
[-] CC cmdlfpac.c
[-] CC cmdlfparadox.c
[-] CC cmdlfpcf7931.c
[-] CC cmdlfpresco.c
[-] CC cmdlfpyramid.c
[-] CC cmdlfsecurakey.c
[-] CC cmdlft55xx.c
[-] CC cmdlfti.c
[-] CC cmdlfviking.c
[-] CC cmdlfvisa2000.c
[-] CC cmdlfmotorola.c
[-] CC cmdtrace.c
[-] CC cmdflashmem.c
[-] CC cmdflashmemspiffs.c
[-] CC cmdsmartcard.c
[-] CC cmdusart.c
[-] CC cmdwiegand.c
[-] CC cmdparser.c
[-] CC cmdmain.c
[-] CC pm3_binlib.c
[-] CC scripting.c
[-] CC cmdscript.c
[-] CC pm3_bitlib.c
[-] CC cmdcrc.c
[-] CC ../common/bucketsort.c
[-] CC flash.c
[-] CC wiegand_formats.c
[-] CC wiegand_formatutils.c
[-] UIC ui/ui_overlays.h
[-] CXX proxgui.cpp
[-] CXX proxguiqt.cpp
[-] MOC proxguiqt.moc.cpp
[-] CXX proxguiqt.moc.cpp
[-] CC(NOSIMD) hardnested/hardnested_bf_core.c
[-] CC(NOSIMD) hardnested/hardnested_bitarray_core.c
[-] CC(MMX) hardnested/hardnested_bf_core.c
[-] CC(MMX) hardnested/hardnested_bitarray_core.c
[-] CC(SSE2) hardnested/hardnested_bf_core.c
[-] CC(SSE2) hardnested/hardnested_bitarray_core.c
[-] CC(AVX) hardnested/hardnested_bf_core.c
[-] CC(AVX) hardnested/hardnested_bitarray_core.c
[-] CC(AVX2) hardnested/hardnested_bf_core.c
[-] CC(AVX2) hardnested/hardnested_bitarray_core.c
[-] CC(AVX512) hardnested/hardnested_bf_core.c
[-] CC(AVX512) hardnested/hardnested_bitarray_core.c
[*] MAKE liblua for linux
[-] CC lapi.c
[-] CC lcode.c
[-] CC lctype.c
[-] CC ldebug.c
[-] CC ldo.c
[-] CC ldump.c
[-] CC lfunc.c
[-] CC lgc.c
[-] CC llex.c
[-] CC lmem.c
[-] CC lobject.c
[-] CC lopcodes.c
[-] CC lparser.c
[-] CC lstate.c
[-] CC lstring.c
[-] CC ltable.c
[-] CC ltm.c
[-] CC lundump.c
[-] CC lvm.c
[-] CC lzio.c
[-] CC lauxlib.c
[-] CC lbaselib.c
[-] CC lbitlib.c
[-] CC lcorolib.c
[-] CC ldblib.c
[-] CC liolib.c
[-] CC lmathlib.c
[-] CC loslib.c
[-] CC lstrlib.c
[-] CC ltablib.c
[-] CC loadlib.c
[-] CC linit.c
[=] AR liblua.a
[*] MAKE jansson
[-] CC dump.c
[-] CC error.c
[-] CC hashtable.c
[-] CC hashtable_seed.c
[-] CC load.c
[-] CC memory.c
[-] CC pack_unpack.c
[-] CC strbuffer.c
[-] CC strconv.c
[-] CC utf.c
[-] CC path.c
[-] CC value.c
[=] AR libjansson.a
[*] MAKE tinycbor
[-] CC cborencoder.c
[-] CC cborencoder_close_container_checked.c
[-] CC cborerrorstrings.c
[-] CC cborparser.c
[-] CC cborparser_dup_string.c
[-] CC cborpretty.c
[-] CC cbortojson.c
[-] CC cborvalidation.c
[=] AR tinycbor.a
[*] MAKE reveng
[-] CC bmpbit.c
[-] CC cli.c
[-] CC getopt.c
[-] CC model.c
[-] CC poly.c
[-] CC preset.c
[-] CC reveng.c
[-] CC bmpbit.c
[=] TEST bmptst
[=] AR libreveng.a
[*] MAKE mbedtls
[-] CC aes.c
[-] CC asn1parse.c
[-] CC asn1write.c
[-] CC base64.c
[-] CC bignum.c
[-] CC ctr_drbg.c
[-] CC entropy_poll.c
[-] CC entropy.c
[-] CC error.c
[-] CC timing.c
[-] CC ecp.c
[-] CC ecp_curves.c
[-] CC certs.c
[-] CC camellia.c
[-] CC blowfish.c
[-] CC cipher_wrap.c
[-] CC cipher.c
[-] CC cmac.c
[-] CC des.c
[-] CC ecdsa.c
[-] CC md.c
[-] CC md_wrap.c
[-] CC md5.c
[-] CC oid.c
[-] CC pem.c
[-] CC arc4.c
[-] CC pk.c
[-] CC pk_wrap.c
[-] CC pkwrite.c
[-] CC pkcs5.c
[-] CC pkcs12.c
[-] CC pkparse.c
[-] CC platform.c
[-] CC platform_util.c
[-] CC rsa.c
[-] CC rsa_internal.c
[-] CC sha1.c
[-] CC sha256.c
[-] CC sha512.c
[-] CC threading.c
[-] CC x509.c
[-] CC x509_crl.c
[-] CC x509_crt.c
[=] AR libmbedtls.a
[*] MAKE zlib
[-] CC deflate.c
[-] CC adler32.c
[-] CC trees.c
[-] CC zutil.c
[-] CC inflate.c
[-] CC inffast.c
[-] CC inftrees.c
[=] AR libz.a
[*] MAKE amiibo
[-] CC amiibo.c
[-] CC drbg.c
[-] CC keygen.c
[=] AR libamiibo.a
[=] GEN lualibs/pm3_cmd.lua
[=] GEN lualibs/mfc_default_keys.lua
[=] LD proxmark3
[*] MAKE bootrom/all
[=] GEN version.c
[-] CC version.c
[-] CC ram-reset.s
[-] CC flash-reset.s
[-] CC ../common_arm/usb_cdc.c
[-] CC ../common_arm/clocks.c
[-] CC bootrom.c
[=] LD obj/bootrom.elf
[=] GEN obj/bootrom.s19
[*] MAKE fpga_compress/all
[*] MAKE zlib
[-] CC deflate.c
[-] CC adler32.c
[-] CC trees.c
[-] CC zutil.c
[-] CC inflate.c
[-] CC inffast.c
[-] CC inftrees.c
[=] AR libz.a
[-] CC fpga_compress.c
[=] LD fpga_compress
[*] MAKE armsrc/all
[-] CC fpga_version_info.c
[-] GEN obj/fpga_all.bit.z
[-] GEN obj/fpga_all.o
[-] CC start.c
[-] CC iso15693.c
[-] CC ../common/iso15693tools.c
[-] CC thinfilm.c
[-] CC lfops.c
[-] CC lfsampling.c
[-] CC pcf7931.c
[-] CC ../common/lfdemod.c
[-] CC ../common/zlib/inflate.c
[-] CC ../common/zlib/inffast.c
[-] CC ../common/zlib/inftrees.c
[-] CC ../common/zlib/adler32.c
[-] CC ../common/zlib/zutil.c
[-] CC legicrf.c
[-] CC legicrfsim.c
[-] CC ../common/legic_prng.c
[-] CC hitag2_crypto.c
[-] CC hitag2.c
[-] CC hitagS.c
[-] CC appmain.c
[-] CC printf.c
[-] CC dbprint.c
[-] CC ../common/commonutil.c
[-] CC util.c
[-] CC string.c
[-] CC BigBuf.c
[-] CC ticks.c
[-] CC ../common_arm/clocks.c
[-] CC hfsnoop.c
[-] CC fpgaloader.c
[-] CC iso14443a.c
[-] CC mifareutil.c
[-] CC mifarecmd.c
[-] CC epa.c
[-] CC mifaresim.c
[-] CC iso14443b.c
[-] CC ../common/crapto1/crypto1.c
[-] CC des.c
[-] CC desfire_key.c
[-] CC mifaredesfire.c
[-] CC ../common/mbedtls/aes.c
[-] CC ../common/mbedtls/platform_util.c
[-] CC iclass.c
[-] CC optimized_cipher.c
[-] CC ../common/crc.c
[-] CC ../common/crc16.c
[-] CC ../common/crc32.c
[-] CC felica.c
[-] CC ../armsrc/Standalone/lf_samyrun.c
[-] CC ../common/parity.c
[-] CC ../common_arm/usb_cdc.c
[-] CC cmd.c
[-] GEN version.c
[-] CC version.c
[=] LD obj/fullimage.stage1.elf
[-] GEN obj/fullimage.nodata.bin
[-] GEN obj/fullimage.nodata.o
[-] GEN obj/fullimage.data.bin
[-] GEN obj/fullimage.data.bin.z
[-] GEN obj/fullimage.data.o
[=] LD obj/fullimage.elf
[=] GEN obj/fullimage.s19
[*] MAKE recovery/all
[=] GEN bootrom.bin
[=] GEN fullimage.bin
[=] GEN proxmark3_recovery.bin
[*] MAKE mfkey/all
[-] CC mfkey32.c
[-] CC ../../common/crapto1/crypto1.c
[-] CC ../../common/crapto1/crapto1.c
[-] CC ../../common/bucketsort.c
[=] LD mfkey32
[-] CC mfkey32v2.c
[=] LD mfkey32v2
[-] CC mfkey64.c
[=] LD mfkey64
[*] MAKE nonce2key/all
[-] CC nonce2key.c
[-] CC ../../common/crapto1/crypto1.c
[-] CC ../../common/crapto1/crapto1.c
[-] CC ../../common/bucketsort.c
[=] LD nonce2key

Edit:
If I try to flash the RRG repo, there is some error message complaining about determining the flash memory of the proxmark and therefore to flash bootrom at first. This I can only achieve with the button holding (as I wrote above).

Last edited by JohnDoePM (2019-12-04 09:36:58)

Offline

#11 2019-12-04 16:07:05

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

yeah,
first flash bootrom,
reset
flash fullimage
now what is the "tail dmesg"  output?  or  lsusb ?

Offline

#12 2019-12-04 19:51:06

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

This is the log of flash all:

~/RRG-proxmark3$ pm3-flash-all 
[=] Waiting for Proxmark3 to appear...
[=] Session log /home/ralf/.proxmark3/log_20191204.txt
[+] About to use the following files:          
[+]     /usr/local/bin/../share/proxmark3/firmware/bootrom.elf          
[+]     /usr/local/bin/../share/proxmark3/firmware/fullimage.elf          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
.Found           
[+] Entering bootloader...           
[+] (Press and release the button only to abort )          
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
........... Found           
[!!] ====================== OBS ! ===========================================           
[!!] Note: Your bootloader does not understand the new CMD_BL_VERSION command            
[!!] It is recommended that you first update your bootloader alone,            
[!!] reboot the Proxmark3 then only update the main firmware 
          
[=] Available memory on this board: UNKNOWN 
          
[!!] ====================== OBS ! ======================================           
[!!] Note: Your bootloader does not understand the new CHIP_INFO command            
[!!] It is recommended that you first update your bootloader alone,            
[!!] reboot the Proxmark3 then only update the main firmware 
          
[=] Permitted flash range: 0x00100000-0x00140000          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/bootrom.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00100200 (0x00000de0->0x00000de0) [R X] @0x298          
          
[+] Loading ELF file /usr/local/bin/../share/proxmark3/firmware/fullimage.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00102000 P 0x00102000 (0x00040700->0x00040700) [R X] @0x94          
[!!] Error: PHDR is not contained in Flash          
[+] All done.           

Have a nice day!

Then I flash boootrom first (holding the button during coming up), disconnect the proxmark from the usb port, connect again and flash the image.
Then again I reconnect the proxmark:

88.692161] usb 2-1.1: new full-speed USB device number 3 using ehci-pci
[   94.027542] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[   94.027550] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   94.027555] usb 2-1.1: Product: proxmark3
[   94.027558] usb 2-1.1: Manufacturer: proxmark.org
[   94.027561] usb 2-1.1: SerialNumber: 8888
[   94.141458] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[   94.141948] usbcore: registered new interface driver cdc_acm
[   94.141950] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  222.623818] cdc_acm 2-1.1:1.0: failed to set dtr/rts
[  222.753989] usb 2-1.1: USB disconnect, device number 3
[  222.995791] usb 2-1.1: new full-speed USB device number 4 using ehci-pci
[  228.178954] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  228.178961] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  228.178966] usb 2-1.1: Product: proxmark3
[  228.178969] usb 2-1.1: Manufacturer: proxmark.org
[  228.178972] usb 2-1.1: SerialNumber: 8888
[  228.179715] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[  229.666091] usb 2-1.1: USB disconnect, device number 4
[  230.043755] usb 2-1.1: new full-speed USB device number 5 using ehci-pci
[  235.338875] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  235.338882] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  235.338886] usb 2-1.1: Product: proxmark3
[  235.338889] usb 2-1.1: Manufacturer: proxmark.org
[  235.338893] usb 2-1.1: SerialNumber: 8888
[  235.339440] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[  426.784843] usb 2-1.1: USB disconnect, device number 5
[  431.298170] usb 2-1.1: new full-speed USB device number 6 using ehci-pci
[  431.834087] usb 2-1.1: device descriptor read/64, error -32
[  432.053320] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  432.053328] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  432.053333] usb 2-1.1: Product: proxmark3
[  432.053336] usb 2-1.1: Manufacturer: proxmark.org
[  432.053339] usb 2-1.1: SerialNumber: 8888
[  432.054005] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[  443.148811] cdc_acm 2-1.1:1.0: failed to set dtr/rts
[  443.150149] usb 2-1.1: USB disconnect, device number 6
[  443.394108] usb 2-1.1: new full-speed USB device number 7 using ehci-pci
[  448.589453] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  448.589461] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  448.589465] usb 2-1.1: Product: proxmark3
[  448.589469] usb 2-1.1: Manufacturer: proxmark.org
[  448.589472] usb 2-1.1: SerialNumber: iceman
[  448.590337] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[  449.806327] usb 2-1.1: USB disconnect, device number 7
[  454.042052] usb 2-1.1: new full-speed USB device number 8 using ehci-pci
[  454.578047] usb 2-1.1: device descriptor read/64, error -32
[  454.797484] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  454.797493] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  454.797497] usb 2-1.1: Product: proxmark3
[  454.797500] usb 2-1.1: Manufacturer: proxmark.org
[  454.797503] usb 2-1.1: SerialNumber: iceman
[  454.798323] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[  473.854405] usb 2-1.1: USB disconnect, device number 8
[  475.625914] usb 2-1.1: new full-speed USB device number 9 using ehci-pci
[  516.085775] usb 2-1.1: new full-speed USB device number 10 using ehci-pci
[  517.993754] usb 2-1.1: new full-speed USB device number 11 using ehci-pci
[  533.545702] usb 2-1.1: device descriptor read/64, error -110
[  549.161594] usb 2-1.1: device descriptor read/64, error -110
[  549.349595] usb 2-1.1: new full-speed USB device number 12 using ehci-pci
[  563.861381] usb 2-1.1: new full-speed USB device number 13 using ehci-pci
[  579.369158] usb 2-1.1: device descriptor read/64, error -110
lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 8086:0189 Intel Corp. 
Bus 001 Device 003: ID 05c8:030d Cheng Uei Precision Industry Co., Ltd (Foxlink) 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hope that helps ...

Offline

#13 2019-12-04 20:09:50

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

It gets disconnected.  Did you kill / remove the modem manager?

Offline

#14 2019-12-04 21:11:58

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

~/iceman-proxmark3/client$ sudo systemctl status ModemManager
[sudo] password for john:        
● ModemManager.service - Modem Manager
   Loaded: loaded (/lib/systemd/system/ModemManager.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

Last edited by JohnDoePM (2019-12-04 21:13:05)

Offline

#15 2019-12-04 21:36:22

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

ok, there is a similar issue on GH.
Anyway, lets see,

- Picture of your device
- tried different usb cable?
- tried different usb port?

Offline

#16 2019-12-05 13:54:10

Mashid0
Contributor
Registered: 2019-12-02
Posts: 28

Re: [SOLVED] Flashing to newest firmware issue

I've got same problem, but solved!
Let me share my Experience with positive result

Environment
MacOSX 10.15.1 (Catalina)
Xcode 11.2.1 (11B500)

brew tap
homebrew/cask
homebrew/core
rfidresearchgroup/proxmark3

Hardware
Proxmark3 Easy V3 (aliexpress)
1 button,
LEDs
Power - white
A - green
B - red
C - orange
D - blue

it looks like
https://www.dropbox.com/s/blc5i9174dgo77u/Proxpark3EasyV3.jpg?dl=0
FluxBB bbcode test

proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument          
#db# bootrom: /-suspect 2016-11-09 00:59:56          
#db# os: /-suspect 2016-11-14 03:06:26          
#db# HF FPGA image built on 2015/03/09 at 08:41:42
          
#db#   Modify by Willok(willok@163.com)

         
Prox/RFID mark3 RFID instrument

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

Have use brew way first,
Result
Boot only with pressed button
A - green - on
B - off
C - orange - on
D - off
release button, device still works if not to rum pm3 smile

port

system_profiler SPUSBDataType
proxmark3:

          Product ID: 0x4b8f
          Vendor ID: 0x9ac4
          Version: 1.00
          Serial Number: iceman
          Speed: Up to 12 Mb/s
          Manufacturer: proxmark.org
          Location ID: 0x14100000 / 18
          Current Available (mA): 500
          Current Required (mA): 500
          Extra Operating Current (mA): 0

Attention! Related macOS Issue (not influence!!!)
IOCreatePlugInInterfaceForService failed 0xe00002be (is independent PM3 connected or not)

The process all have try, to restore

make all

===================================================================
Platform name:     Proxmark3 Generic target
PLATFORM:          [b]PM3OTHER[/b]
Platform extras:   No extra selected
Included options:  LF HITAG ISO15693 LEGICRF ISO14443b ISO14443a ICLASS FELICA NFCBARCODE HFSNIFF
Standalone mode:   LF_SAMYRUN


:proxmark3 maxim$ pm3
[=] Waiting for Proxmark3 to appear...

          
██████╗ ███╗   ███╗ ████╗      ...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/          
                 on paypal - https://www.paypal.me/iceman1001          

          
[=] Session log /Users/maxim/.proxmark3/log_20191202.txt
[=] Using UART port /dev/tty.usbmodemiceman1           
[!!] ERROR: cannot communicate with the Proxmark

than port disappeared
only Power LED - on, others off

disconnect usb, hold button, connect
port - ok, boot - ok
release button

maxim$ pm3-flash-fullimage 
[=] Waiting for Proxmark3 to appear...
[=] Session log /Users/maxim/.proxmark3/log_20191202.txt
[+] About to use the following file:          
[+]     /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/fullimage.elf          
[+] Waiting for Proxmark3 to appear on /dev/tty.usbmodemiceman1           
.Found           
[=] Available memory on this board: 512K bytes
          
[=] Permitted flash range: 0x00102000-0x00180000          
[+] Loading ELF file /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/fullimage.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00102000 P 0x00102000 (0x00041480->0x00041480) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00143480 (0x00001524->0x00001524) [RW ] @0x41514          
[=] Note: Extending previous segment from 0x41480 to 0x429a4 bytes          
          
          
[+] Flashing... 
          
[+] Writing segments for file: /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/fullimage.elf          
[+]  0x00102000..0x001449a3 [0x429a4 / 533 blocks]          
..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... OK           

          
[+] All done.           

Have a nice day!

port - lost, LEDs - off (only power ON LED)
boot only with button

maxim$ pm3-flash-bootrom 
[=] Waiting for Proxmark3 to appear...
[=] Session log /Users/maxim/.proxmark3/log_20191202.txt
[+] About to use the following file:          
[+]     /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/bootrom.elf          
[+] Waiting for Proxmark3 to appear on /dev/tty.usbmodemiceman1           
.Found           
[=] Available memory on this board: 512K bytes
          
[=] Permitted flash range: 0x00100000-0x00180000          
[+] Loading ELF file /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/bootrom.elf           
[+] Loading usable ELF segments:          
[+]    0 : V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94          
[+]    1 : V 0x00200000 P 0x00100200 (0x00000e08->0x00000e08) [R X] @0x298          
          
          
[+] Flashing... 
          
[+] Writing segments for file: /usr/local/Cellar/proxmark3/HEAD-26ffd5f/bin/../share/proxmark3/firmware/bootrom.elf          
[+]  0x00100000..0x001001ff [0x200 / 1 blocks]          
. OK           
[+]  0x00100200..0x00101007 [0xe08 / 8 blocks]          
........ OK           

          
[+] All done.           

Have a nice day!

My solution!
Not via brew smile
Download project from GitHub to local folder example: /proxmark3
USE Makefile.platform file instead of just command like: export HOMEBREW_PROXMARK3_PLATFORM=PM3OTHER

1st: copy Makefile.platform.sample -> Makefile.platform
2nd: edit file content

# PLATFORM=PM3RDV4
PLATFORM=PM3OTHER

repeat compilation again
make clean
make all
make install

pm3-flash-all

DONE! Now the boot loader works as needed.
Now it work for me.

Last edited by Mashid0 (2019-12-05 14:07:30)

Offline

#17 2019-12-05 19:25:19

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

hm,  Which OS was @johndoe on?

Offline

#18 2019-12-05 20:02:12

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

iceman wrote:

- Picture of your device
- tried different usb cable?
- tried different usb port?

To 1: Click.
To 2: Yes.
To 3: Yes.

Last edited by JohnDoePM (2019-12-05 20:02:58)

Offline

#19 2019-12-05 20:32:12

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

Hm... that red one.. isn't that the bad hardware clone of RDV2.   http://www.proxmark.org/forum/viewtopic.php?id=5085

I guess stay at the working iceman repo.

Offline

#20 2019-12-05 21:10:31

JohnDoePM
Contributor
Registered: 2018-07-08
Posts: 49

Re: [SOLVED] Flashing to newest firmware issue

Sh.. . I didn't know that. So I'll stay at the iceman repo.
Do you have an idea of source of the problem ?

Offline

#21 2019-12-05 22:59:32

iceman
Administrator
Registered: 2013-04-25
Posts: 9,538
Website

Re: [SOLVED] Flashing to newest firmware issue

Sorry,  not really any idea of the source

Offline

Pages: 1

Board footer

Powered by FluxBB