Yes! We got it! I was hesitant to load x86 drivers on the m1 but once I
searched the product id 0x7523 and vendor id 0x1a86, I found an old driver for
the Winchiphead chipset at
https://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/
Thanks for the help guys!
Kerry
What matters is the chipset in the USB cable, it's actually a USB to
serial. Most cables are made with a chip from one of two manufacturers:
Future Technologies (FTDI) - https://ftdichip.com/drivers/
Prolific Technology -
http://www.prolific.com.tw/us/ShowProduct.aspx?pcid=41&showlevel=0041-0041
What matters is the chipset in the mini too! There’s very little work going on
for the M1 from what I can tell. I wish I knew how to write a driver, I would.
Your script is perfect for me! That’s where I happened to put my chirp.
I can’t seem to ascribe any meaning from what I do see in the ven
Here's my little script. I keep CHIRP in my home directory Applications, so
adjust your path as necessary:
❯ cat bin/chirp_sign.sh
#!/opt/homebrew/bin/bash
xattr -c ~/Applications/CHIRP.app
xattr -c ~/Applications/CHIRP.app/Contents
codesign --force --deep --sign - ~/Applications/CHIRP.app
The dr
Yay! Chirp is running again! I was going to try to figure out those commands
again but you got them first. Thanks! I’m going to make a script out of those
commands.
Now, about the drivers, how does that work on the m1?
> On Sep 12, 2021, at 7:49 AM, Scott Lopez wrote:
>
> Assuming you put the
Assuming you put the chrip.app in your Applications folder, try running the
following commands:
xattr -c /Applications/CHIRP.app
xattr -c /Applications/CHIRP.app/Contents
codesign --force --deep --sign - /Applications/CHIRP.app
Need to run these from the command line (use Terminal) and you must h
