(Partial Solved)cdc driver and resetting USB ports on mac

Navster · 2017-07-21 04:22:59

so I have updated my proxmark3 easy on windows and it shows as :
Prox/RFID mark3 RFID instrument
bootrom: master/v2.2.0-536-g138927d-suspect 2017-07-02 09:16:48
os: master/v2.2.0-536-g138927d-suspect 2017-07-02 09:16:53
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

uC: AT91SAM7S256 Rev A
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 192561 bytes (73%). Free: 69583 bytes (27%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 256K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>

I'm assuming I have updated from HID to CDC.
When I connect to my mac it does not detect the PM3. When I go to about this mac and under system info it shows up as a HID device.....thoughts and Thank you in advance.

Last edited by Navster (2017-08-02 21:26:14)

Navster · 2017-07-21 21:13:41

I tired using the newest build from icemans fork. It seem like the newer bootrom's revert the cdc back to hid, product id 0x4b8f vendor id 0x9ac4

iceman · 2017-07-22 13:13:28

No it does not revert back. The only change is the vendor & product id thats changed. I've mention on other threads that this change will confuse all "detection" of HID vs CDC. However rest assure that icemanfork is cdc. You need to go back ut subversion r750 or even older to have a HID device.

However when the vendor/product id changes, ususally the com port changes on windows, and for linux ppl, you may need to update your blacklist file. There is an updated one on github www.proxmark.org/forum/viewtopic.php?pid=28774#p28774

Navster · 2017-07-22 21:06:10

Fixed problem on window but on mac still showing up as hid even though it is cdc

Navster · 2017-07-31 01:20:14

iceman wrote:

No it does not revert back. The only change is the vendor & product id thats changed. I've mention on other threads that this change will confuse all "detection" of HID vs CDC. However rest assure that icemanfork is cdc. You need to go back ut subversion r750 or even older to have a HID device.
However when the vendor/product id changes, ususally the com port changes on windows, and for linux ppl, you may need to update your blacklist file. There is an updated one on github www.proxmark.org/forum/viewtopic.php?pid=28774#p28774

updated blacklist file mac still gives me invalid port when i run: proxmark3 /dev/tty.usbmodem1421

when i check under about this mac- system report-usb i see:PM3:

Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Speed: Up to 12 Mb/sec
Manufacturer: proxmark.org
Location ID: 0x14200000 / 11
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

when i ran : ls /dev/cu* on terminal does not show the usb port just bluetooth.

i ran system_profiler on mac an i get:

Proxmark3:

Version: 1.0.0d2
Last Modified: 2017-07-30, 1:18 AM
Bundle ID: com.proxmark.driver.dummy
Loaded: No
Obtained from: Not Signed
Location: /System/Library/Extensions/Proxmark3.kext
Kext Version: 1.0.0d2
Loadable: No
Signature Validation Errors: Not Signed
Dependencies: Satisfied
Signed by: Not Signed.

when i check under about this mac- system report-usb i see:PM3:

Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Speed: Up to 12 Mb/sec
Manufacturer: proxmark.org
Location ID: 0x14200000 / 11
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

Thoughts?

iceman · 2017-07-31 10:51:54

Sorry, I have no OSX enviroment. No idea how it works on OSX.

Navster · 2017-07-31 22:37:02

i did some googling and reset the usb's on the mac:

Reset SMC of a MacBook Air, MacBook Pro Retina, or MacBook Pro’s with an internal non-removable battery

This is how to reset SMC on most modern Mac laptops, none of which have a removable battery:

Shutdown your MacBook Air / MacBook Pro
Connect the power adapter to the Mac
On the MacBook / Pro’s keyboard, hold down the Shift+Control+Option keys and the Power button at the same time
Release all keys and the power button at the same time – the little light on the MagSafe adapter may change colors briefly to indicate the SMC has reset
Boot your Mac as usual

PM3 works but if i disconnect usb and plug back in its a invalid port. However a usb reset seems to make it work.

the mac now recognizes the pm3, yay!!! but still shows up as :
Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Speed: Up to 12 Mb/sec
Manufacturer: proxmark.org
Location ID: 0x14200000 / 2
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

im running version:
bootrom: master/v2.2.0-566-g8614a5a-suspect 2017-07-18 08:43:28
os: master/v2.2.0-566-g8614a5a-suspect 2017-07-18 08:43:32
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

Last edited by Navster (2017-08-01 17:53:28)

iceman · 2017-08-01 08:18:44

Not sure if its working or not.
but if its working, you might re-cap the "reseting of usb-ports" on OSX short for future OSX users.
and edit your first post and add the suffix "[solved]" to your title

Navster · 2017-08-01 08:27:20

iceman wrote:

Not sure if its working or not.
but if its working, you might re-cap the "reseting of usb-ports" on OSX short for future OSX users.
and edit your first post and add the suffix "[solved]" to your title

So far if the pm3 client is plugged in, the pm3 client is recognized. It’s still recognized until unplugged. If I try to replugg the pm3 client I get invalid port. I have to restart Mac with the pm3 plugged in for the mac to recognize it. For some reason the apple hid seems to grab the pm3 client once unplugged. I did read something on codeless kext. I have updated the file but still no luck.

Last edited by Navster (2017-08-01 17:44:30)

Navster · 2017-08-04 07:30:17

iceman wrote:

No it does not revert back. The only change is the vendor & product id thats changed. I've mention on other threads that this change will confuse all "detection" of HID vs CDC. However rest assure that icemanfork is cdc. You need to go back ut subversion r750 or even older to have a HID device.
However when the vendor/product id changes, ususally the com port changes on windows, and for linux ppl, you may need to update your blacklist file. There is an updated one on github www.proxmark.org/forum/viewtopic.php?pid=28774#p28774

Tried changing VID/PID no difference. Only time it shows up as CDC on Mac is if i flash lua version boot room and flash. When I install the newest versions of boot room or flash. Shows up as hid on Mac.???

ntk · 2017-08-04 13:31:44

have you tried main repo V3.0?

Navster · 2017-08-04 23:22:09

no i haven't, i wil try that. i only see 2.5.0, maybe I'm looking in the wrong spot.

Last edited by Navster (2017-08-04 23:29:12)

iceman · 2017-08-06 09:37:44

Got to github and use the latest source from there, or read the instructions how to use the homebrew alternative.

Navster · 2017-08-06 22:26:01

ntk wrote:

have you tried main repo V3.0?

so i update to: v3
Prox/RFID mark3 RFID instrument
bootrom: master/v3.0.1-63-g8cf533f-suspect 2017-08-06 20:39:26
os: master/v3.0.1-63-g8cf533f-suspect 2017-08-06 20:50:17
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

i ran system_profiler SPUSBDataType
PM3:

Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Speed: Up to 12 Mb/sec
Manufacturer: proxmark.org
Location ID: 0x14200000 / 3
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

still shows up as HID.

Tom5ive · 2017-09-22 12:46:41

So I am one of those that have had issues with the PM3 and upgrading to CDC - then the PM3 not being recognised half way through the process.

I think there is something going on with newer versions of OS X and the step that involves loading the kernel extension. After thinking I had bricked my pm3 when I could no longer see it under /dev/cu.**** or under a system_profiler SPUSBDataType dump (yes after reboots etc). I backtracked and noticed that I was only unable to connect after issuing the command "sudo make install_kext" to load the kernel extension, after deleting the kext using:

rm -rf /System/Library/Extensions/Proxmark3.kext

I was then able to see the it again under /dev/cu.*** and also connect with the proxmark3 application. I've since compiled and flashed the latest bootloader and firmware WITHOUT doing the kext step. My PM3 shows up as:

PM3:

Product ID: 0x4b8f
Vendor ID: 0x9ac4
Version: 0.01
Speed: Up to 12 Mb/sec
Manufacturer: proxmark.org
Location ID: 0x14100000 / 25
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0

What I think happened when Navster reset the SMC was, that the kernel extension was unloaded allowing the device to connect.

This was my exact experience. I have since tried to update to CDC again and can have the same issue.

Last edited by Tom5ive (2017-09-22 12:49:21)

iceman · 2017-09-30 21:07:55

So if OSX users could verify this suggested fix from previous post...

OSX:

sudo rm -rf /System/Library/Extensions/Proxmark3.kext
sudo make install_kext
ls /dev/cu*

Tom5ive · 2017-12-03 09:56:52

I think I have finally figured this out! Argh what a pain it has been but I hope that this post can help some others!

I'm currently running on high Sierra and was previously on Sierra when the issues began.

What I finally found, is that the /dev/usbmodem*** listing is changing mid way through flashing the fullimage.elf file. This happens when flashing from the main fork to iceman's fork, or vice versa and sometimes when flashing from the same fork and just updating or re-flashing.

It seems to happen when the flasher utility puts the PM3 into a certain mode wherein both the green / blue LEDs are statically lit. This is why some of us can flash the bootloader BUT then have issues with the process hanging flashing fullimage.elf. The fix when this happens, is to CTRL+c (exit) the flash command and reissue again with the changed NEW /dev/cu.usbmodem** listing.

The CDC / HID confusion is also related to this. The PM3 seems to get "stuck" looking like a CDC device from the output of the "system_profiler SPUSBDataType" command if you have flashed the bootloader and then gotten halfway through the process I have explained here.

This is all with the latest stable iceman Git compiles locally on OSX High Sierra. If I use the main fork I don't get the switch half way through the process. I've tried flashing back n forth with both multiple times to test all of the above.

I have linked an example screenshot that should help explain what is happening. Please let me know if I can clarify further!

https://imgur.com/a/uFmQI

iceman · 2017-12-03 10:26:12

are you using both bootrom and fullimage from the same build?
when going between iceman fork and offical pm3 or the other way around, then yes, this will occure. Its mainly because iceman fork uses a serialnumber which offical pm3 doesnt. hence the enumeration of the serial comport ends with 88 in iceman fork.

Tom5ive · 2017-12-04 07:50:09

Yes - bootrom and fullimage from the same build.

This seems to happen to me with the main fork too. Even when just doing a re flash - not changing builds or changing from one fork to the other. But only since High Sierra - I'm pretty cure it was not happening in El Cap.

iceman · 2017-12-04 08:40:00

It should not happen in offical pm3 releases...

but then, OSX seems to behave differently. There are some issues on Github based on OSX. You might be able to test things out for us.

Tom5ive · 2017-12-04 22:34:55

Definitely happening for me on both clients, fresh compilations locally, doesn't happen if I use the brew tap for the main fork though. I've only ever used the client on OS X - it does seem a bit buggy at times. With the iceman FW and client I sometimes get a semi random segmentation fault.

I've also identified a fairly major bug with the iceman fork, which is that EM410x tags get identified as indala. A lot of EM's are flat out unreadable / can't do anything with them on iceman. But on the main fork they read and can be manipulated. I found this out last night while trying to unlock a friends implanted xEM that is locked with one of those white multi-frequency cloners with a screen and then did some more testing.

Very happy to do some testing in my spare time. I'm using the PM3 a lot at the moment as a lot of my research relates to RFID.

iceman · 2017-12-05 06:10:36

...can you specify it down a bit more semi random segmentation fault hard to figure out with that little info.

regarding LF, yes, its in a refactoring state. Not good at all.

Tom5ive · 2018-09-11 03:11:37

This turned out to be for a specific card when hardnesting a specific block on that card. Got to follow up but I think its repeatable. Will get you a nonces file asap.

Proxmark3 community

Announcement

#1 2017-07-21 04:22:59

(Partial Solved)cdc driver and resetting USB ports on mac

#2 2017-07-21 21:13:41

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#3 2017-07-22 13:13:28

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#4 2017-07-22 21:06:10

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#5 2017-07-31 01:20:14

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#6 2017-07-31 10:51:54

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#7 2017-07-31 22:37:02

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#8 2017-08-01 08:18:44

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#9 2017-08-01 08:27:20

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#10 2017-08-04 07:30:17

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#11 2017-08-04 13:31:44

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#12 2017-08-04 23:22:09

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#13 2017-08-06 09:37:44

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#14 2017-08-06 22:26:01

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#15 2017-09-22 12:46:41

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#16 2017-09-30 21:07:55

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#17 2017-12-03 09:56:52

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#18 2017-12-03 10:26:12

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#19 2017-12-04 07:50:09

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#20 2017-12-04 08:40:00

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#21 2017-12-04 22:34:55

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#22 2017-12-05 06:10:36

Re: (Partial Solved)cdc driver and resetting USB ports on mac

#23 2018-09-11 03:11:37

Re: (Partial Solved)cdc driver and resetting USB ports on mac

Board footer