[chirp_users] CHIRP on Mac mini M1
Hi!
Trying to make the subject computer and software run. Had it running, albeit without the Mac drivers and the 2021/08/30 distribution broke it. Anybody else trying to get this to work and how did you do it?
Thanks, Kerry
Hi Kerry,
On Sat, Sep 11, 2021 at 12:37 PM Kerry Whittle t2ckerry@gmail.com wrote:
Hi!
Trying to make the subject computer and software run. Had it running, albeit without the Mac drivers and the 2021/08/30 distribution broke it. Anybody else trying to get this to work and how did you do it?
Thanks, Kerry
Nothing changed in the 2021/08/30 build that should have affected CHIRP working on macOS. Are you sure this was the case? For example, did you fall back to the previous build of CHIRP to get it working again?
Jim KC9HI
Hi Jim,
I’m still feeling my way around. Ever since I loaded 2021/08/30 I haven’t gotten anything to run. I dropped back to 2021/08/26 and had the same problem. I checked to make sure the permissions on the app were OK and now spctl is messed up as it is giving me errors implying it can’t find it’s configuration.
Let me look and see how far back in versions I have to go to get it going again.
Kerry
On Sep 11, 2021, at 11:57 AM, Jim Unroe rock.unroe@gmail.com wrote:
Hi Kerry,
On Sat, Sep 11, 2021 at 12:37 PM Kerry Whittle t2ckerry@gmail.com wrote:
Hi!
Trying to make the subject computer and software run. Had it running, albeit without the Mac drivers and the 2021/08/30 distribution broke it. Anybody else trying to get this to work and how did you do it?
Thanks, Kerry
Nothing changed in the 2021/08/30 build that should have affected CHIRP working on macOS. Are you sure this was the case? For example, did you fall back to the previous build of CHIRP to get it working again?
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I went back a month and I’m still getting an application error before it ever makes an appearance on the screen. Here’s the info I get:
Process: CHIRP [1521] Path: /Volumes/VOLUME/*/CHIRP.app/Contents/MacOS/chirp Identifier: com.danplanet.chirp Version: ??? Code Type: X86-64 (Translated) Parent Process: ??? [1] Responsible: CHIRP [1521] User ID: 501
Date/Time: 2021-09-11 12:06:39.852 -0500 OS Version: macOS 11.5.2 (20G95) Report Version: 12 Anonymous UUID: 4DD67A22-6E32-B061-1ED5-25F60D7F71B4
Time Awake Since Boot: 2300 seconds
System Integrity Protection: enabled
Notes: Translocated Process
Crashed Thread: Unknown
Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2): --> mapped file 104293000-104295000 [ 8K] r-x/rwx SM=COW Object_id=765d2599
Backtrace not available
Unknown thread crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x0000000000000000 x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000 x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000000000000 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x0000000000000000 lr: 0x0000000000000000 sp: 0x000000030c7fd7f0 pc: 0x00007ffdffe6b3ec cpsr: 0x00000000 far: 0x0000000000000000 esr: 0x00000000
Binary images description not available
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 0 thread_create: 0 thread_set_state: 0
VM Region Summary: Writable regions: Total=18.7M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.7M(100%)
VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= STACK GUARD 56.0M 1 Stack 8176K 1 VM_ALLOCATE 10.5M 1 VM_ALLOCATE (reserved) 72K 2 reserved VM address space (unallocated) mapped file 4.7G 11 =========== ======= ======= TOTAL 4.8G 16 TOTAL, minus reserved VM space 4.8G 16
Model: Macmini9,1, BootROM 6723.140.2, proc 8:4:4 processors, 16 GB, SMC Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin Memory Module: LPDDR4 AirPort: spairport_wireless_card_type_airport_extreme, wl0: Jul 7 2021 00:48:27 version 18.50.40.10.7.8.121 FWID 01-f5ad2691 Bluetooth: Version 8.0.5d7, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 USB Device: USB 3.1 Bus USB Device: USB 3.1 Bus USB Device: USB3.0 Hub USB Device: USB3.0 Hub USB Device: USB 10/100/1000 LAN USB Device: USB2.0 Hub USB Device: USB2.0 Hub USB Device: USB 2.0 Hub USB Device: USB 3.1 FD USB Device: Back-UPS ES 725 FW:802.n5.D USB FW:n5 USB Device: USB Billboard Device USB Device: USB 3.0 Bus USB Device: HD Pro Webcam C920 Thunderbolt Bus: Mac mini, Apple Inc. Thunderbolt Bus: Mac mini, Apple Inc.
On Sep 11, 2021, at 11:57 AM, Jim Unroe rock.unroe@gmail.com wrote:
Hi Kerry,
On Sat, Sep 11, 2021 at 12:37 PM Kerry Whittle t2ckerry@gmail.com wrote:
Hi!
Trying to make the subject computer and software run. Had it running, albeit without the Mac drivers and the 2021/08/30 distribution broke it. Anybody else trying to get this to work and how did you do it?
Thanks, Kerry
Nothing changed in the 2021/08/30 build that should have affected CHIRP working on macOS. Are you sure this was the case? For example, did you fall back to the previous build of CHIRP to get it working again?
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 have Xcode installed.
You'll need to run these every time you update the CHIRP app.
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 scottjl@gmail.com wrote:
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 have Xcode installed.
You'll need to run these every time you update the CHIRP app. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 drivers for the cable you're using really depend on the chipset in the cable. MacOS does have some default drivers, and they may work for you. If they don't I suggest going to the web site specific for the chipset and not the cable brand, they tend to be newer. Google something like "chipset macos driver download" and you should find the page.
On Sun, Sep 12, 2021 at 10:45 AM Kerry Whittle t2ckerry@gmail.com wrote:
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 scottjl@gmail.com wrote:
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 have
Xcode installed.
You'll need to run these every time you update the CHIRP app. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to
chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to scottjl@gmail.com at scottjl@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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 vendor id on the Mac or the laptop pc for the programming cable. It’s just numbers to me no initials for the company who made them. I did get a windows driver set on a tiny cd for the cable for the baofeng. Some of it is written in Chinese and reading that is beyond me. So I have no idea what kind of cable I have.
I keep working on it. At least you guys got the program running for me so I can use the bigger screen to edit files.
Thanks, Kerry
On Sep 12, 2021, at 2:13 PM, Scott Lopez scottjl@gmail.com wrote:
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 drivers for the cable you're using really depend on the chipset in the cable. MacOS does have some default drivers, and they may work for you. If they don't I suggest going to the web site specific for the chipset and not the cable brand, they tend to be newer. Google something like "chipset macos driver download" and you should find the page.
On Sun, Sep 12, 2021 at 10:45 AM Kerry Whittle <t2ckerry@gmail.com mailto:t2ckerry@gmail.com> wrote: 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 <scottjl@gmail.com mailto:scottjl@gmail.com> wrote:
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 have Xcode installed.
You'll need to run these every time you update the CHIRP app. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com mailto:t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to scottjl@gmail.com mailto:scottjl@gmail.com at scottjl@gmail.com mailto:scottjl@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
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-00...
MacOS does come with default drivers for some of the chips from these manufactures, but they aren't always the most up-to-date. The easiest way to find out what chipset you're using is to use the System Information application (located in /Applications/Utilities). Open the app, look at Hardware > USB and then look for your cable. Look for an item that says something about serial or UART. Or unplug and replug the cable, pressing Command-R each time and look for something that disappears and shows up. Once you find the right item, you can select it and get more info, under vendor ID you should see either Prolific or Future. You should be able to figure out the chipset from the item name itself, for example one of my cables identifies as "FT232R USB UART" which tells me it's a Future Technologies chipset and needs the 232 drivers. Another cable I have identifies as "USB-Serial Controller" with a vendor ID of Prolific. Looking at the Product ID I see it's "2303" which happens to be a chipset from Prolific looking at their website. There's only one MacOS driver available, so that's the one to use. Pretty much 99% of these cheap $10 cables are going to use one chipset or the other and not something very rare. I haven't seen any cables that are USB-C yet, these are all USB-A, so I need to use them with an adapter or hub with USB-A ports for my MacBook Air M1. Even though the drivers aren't ARM native, they seem to work just fine in my experience.
You will also have to do some guesswork when selecting the port in CHIRP itself. On the MacOS version the drop-down list for port will show things like /dev/cu.somethingsomething. Look for one that says "usbserial" or the like. If you can't find it, again it might be useful to try unplugging and replugging just the cable, and restarting CHIRP and look for an entry that disappears and shows up on the list. Remember what you select, as it should be called the same thing in the future.
It won't hurt to install drivers from both manufactures, they'll just be sitting around unused if you don't plug a cable with that chip in, so if you're really stuck, install both. If you're still at a loss, then get another cheap cable from Amazon, look for one that says FTDI or Prolific chipset.
Also important, do make sure the cable is plugged in all the way to your radio, some of my radios require more pressure to push it in fully. Set the radio to an unused frequency and set the volume to 70% or so.
I have no problems programming all of my radios with CHIRP on MacOS (Intel or M1) or Windows 10 following these general guidelines.
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-...
Thanks for the help guys!
Kerry de KK4JO
On Sep 12, 2021, at 3:49 PM, Scott Lopez scottjl@gmail.com wrote:
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/ https://ftdichip.com/drivers/ Prolific Technology - http://www.prolific.com.tw/us/ShowProduct.aspx?pcid=41&showlevel=0041-00... http://www.prolific.com.tw/us/ShowProduct.aspx?pcid=41&showlevel=0041-0041
MacOS does come with default drivers for some of the chips from these manufactures, but they aren't always the most up-to-date. The easiest way to find out what chipset you're using is to use the System Information application (located in /Applications/Utilities). Open the app, look at Hardware > USB and then look for your cable. Look for an item that says something about serial or UART. Or unplug and replug the cable, pressing Command-R each time and look for something that disappears and shows up. Once you find the right item, you can select it and get more info, under vendor ID you should see either Prolific or Future. You should be able to figure out the chipset from the item name itself, for example one of my cables identifies as "FT232R USB UART" which tells me it's a Future Technologies chipset and needs the 232 drivers. Another cable I have identifies as "USB-Serial Controller" with a vendor ID of Prolific. Looking at the Product ID I see it's "2303" which happens to be a chipset from Prolific looking at their website. There's only one MacOS driver available, so that's the one to use. Pretty much 99% of these cheap $10 cables are going to use one chipset or the other and not something very rare. I haven't seen any cables that are USB-C yet, these are all USB-A, so I need to use them with an adapter or hub with USB-A ports for my MacBook Air M1. Even though the drivers aren't ARM native, they seem to work just fine in my experience.
You will also have to do some guesswork when selecting the port in CHIRP itself. On the MacOS version the drop-down list for port will show things like /dev/cu.somethingsomething. Look for one that says "usbserial" or the like. If you can't find it, again it might be useful to try unplugging and replugging just the cable, and restarting CHIRP and look for an entry that disappears and shows up on the list. Remember what you select, as it should be called the same thing in the future.
It won't hurt to install drivers from both manufactures, they'll just be sitting around unused if you don't plug a cable with that chip in, so if you're really stuck, install both. If you're still at a loss, then get another cheap cable from Amazon, look for one that says FTDI or Prolific chipset.
Also important, do make sure the cable is plugged in all the way to your radio, some of my radios require more pressure to push it in fully. Set the radio to an unused frequency and set the volume to 70% or so.
I have no problems programming all of my radios with CHIRP on MacOS (Intel or M1) or Windows 10 following these general guidelines. _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kerry at t2ckerry@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
participants (3)
-
Jim Unroe -
Kerry Whittle -
Scott Lopez