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.
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.
Hi folks,
I didn't find the new tty, (it should be something like ttyUSB0) under my /dev directory as I plugged the board via an USB wire.
I guess it should be a kind of driver missing problem of my Mac. However I didn't find any help elsewhere.
I'm using Radio War's r617-fix firmware kernel for proxmark3 and official r693 compiled client on Mac OS X Mountain Lion 10.8.3. Those should be all right.
Here's my usb info:
USB Hi-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x1c2d
PCI Revision ID: 0x0005
PCI Vendor ID: 0x8086
Bus Number: 0xfa
Hub:
Product ID: 0x2514
Vendor ID: 0x0424 (SMSC)
Version: b.b3
Speed: Up to 480 Mb/sec
Location ID: 0xfa100000 / 3
Current Available (mA): 500
Current Required (mA): 2
USB2.0 Hub:
Product ID: 0x0608
Vendor ID: 0x05e3 (Genesys Logic, Inc.)
Version: 77.64
Speed: Up to 480 Mb/sec
Location ID: 0xfa130000 / 6
Current Available (mA): 500
Current Required (mA): 100
ProxMark-3 RFID Instrument:
Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Serial Number: ChangeMe
Speed: Up to 12 Mb/sec
Manufacturer: J. Westhues
Location ID: 0xfa131000 / 8
Current Available (mA): 500
Current Required (mA): 500
Apple Internal Keyboard / Trackpad:
Product ID: 0x0245
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.08
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0xfa120000 / 5
Current Available (mA): 500
Current Required (mA): 40
BRCM2070 Hub:
Product ID: 0x4500
Vendor ID: 0x0a5c (Broadcom Corp.)
Version: 1.00
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0xfa110000 / 4
Current Available (mA): 500
Current Required (mA): 94
Bluetooth USB Host Controller:
Product ID: 0x821a
Vendor ID: 0x05ac (Apple Inc.)
Version: 0.41
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0xfa113000 / 7
Current Available (mA): 500
Current Required (mA): 0
FaceTime HD Camera (Built-in):
Product ID: 0x8509
Vendor ID: 0x05ac (Apple Inc.)
Version: 5.16
Serial Number: CC2B2A005MDGFLA0
Speed: Up to 480 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0xfa200000 / 2
Current Available (mA): 500
Current Required (mA): 500Here's my OS version:
$ uname -a
Darwin Rix-Mac.local 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64Is there any info more I should provide?
I referred the manner here(http://www.proxmark.org/forum/viewtopic.php?pid=5004#p5004) but it doesn't help.
Thanks.
Offline
Hi
I know this topic is fairly old but as I haven’t seen a guide one how to use the Proxmark CDC on Mac OS X. Therefore I’am posting it here.
I am on r797. I updated the firmware of the Proxmark using Linux. It now shows up as /dev/cu.usbmodem1421
I can access it with the following command:
./client/proxmark3 /dev/tty.usbmodem1421 Before the Proxmark can be attached to a VM the USB-CDC driver has to be unloaded using:
sudo kextunload /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDC.kext
sudo kextunload /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDCACMControl.kext
sudo kextunload /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBCDCACMData.kextOffline
I'm having problems on Mac as well. When I plug in the Proxmark, I get nothing new in the /dev directory. I can use USB Prober and System Info to see that the Mac does recognize the device and has registered it as an HID device.
Why do some posts reference starting the app without a command line argument of the port while others show using the port on the command line. Looking at the code, it appears that the port is a required argument.
I have been using Parallels with my Proxmark, but moving to using OS X exclusively. My proxmark is running firmware:
bootrom: svn 486-unclean 2011-08-28 18:52:03
os: svn 486-unclean 2011-08-28-18:52:03
I ran the 486 version of the client on windows to get this data. I also have the 672 cleint on windows, but could never get the firmware update to work, so I'm focusing, for the moment on getting things working from my Mac
Apparently the driver model has changed over time, is it accurate to say that:
Older versions (pre-???) used HID class and newer versions use the CDC class?
How does this change affect how the device appears on Mac and Linux vs Windows? Based on AntiCat's comment, it sounds like even with the CDC device type, it still is supposed to appear as a tty device on Mac. Is this correct?
Any suggestions as to why I'm not seeing a device appear. (Without Parallels running - so it's not grabbing the device)
Thanks
Offline
I tried the suggestions in http://www.proxmark.org/forum/viewtopic.php?pid=5004#p5004 - creating the proxmark dummy kernel extension, but this did not change anything.
I did notice in USB Prober, under "Port Information", it says "Not Captive", but it is Connected and Enabled.
Offline
@robertpalmerjr - yes, it is correct that there is a new interaface (CDC), while the old one was HID. I have no idea how the device appears on Mac though, so @AntiCat, thanks for the instructions. we should update the wiki instructions so there are valid instructions for bot pre- and post-cdc.
Oh, and @robertpalmerjr, the new interace can be traced to subversion commit "r672 - moved cdc branch to trunk" . (https://code.google.com/p/proxmark3/source/detail?r=672)
Offline
If you wish to change from the older HID firmware to the post r672 CDC based firmware I believe you have to reflash the bootloader to the newer cdc enabled bootloader.
If you have a look in this thread http://www.proxmark.org/forum/viewtopic.php?id=1551 for someone else having the same issue.
and this thread http://www.proxmark.org/forum/viewtopic.php?id=1562%20downlaod%20the%20pm3-bin-715 where you can download a precompiled release for windows, in the zip file you will find UpdateBootloader.pdf which describes how to use the old flasher to flash the new bootloader, once you have done this you can then use the new flasher to update the firmware.
The precompiled release has a batch file to do this for you "FLASH - NEW Bootrom (uses old flasher exe).bat" just be aware that messing up the bootrom would mean you would have to recover the device by jtag so read the instructions carefully.
Offline
I also posted in http://www.proxmark.org/forum/viewtopic.php?id=1614 regarding the flashing. I used the prebuilt binary for Windows to attempt flashing the newer bootloader. Unfortunately, it is failing as noted in the thread.
Offline