Hello,

I have a problem with the Spirit Settings App on my Mac with Apple Silicon (M1 Ultra) running macOS 12.6. When starting the app I always get an error that the interface is not detected. I have installed the SiLabs device drivers and when USB dongle is connected I see the device under /dev/cu.usbserial-0001 as well as /dev/tty.usbseriasl-0001.

So whats wrong?
I assume that the device name is not as expected.

When running the same software under Windows 11 for ARM in a VM it is working fine (after assigning the device to the VM.

Kind regards

Michael

Hello,

please check this:
http://manual.spirit-system.com/index.p ... _under_Mac

The driver is not fully installed or is not allowed in your system, for this reason it has no correct device.

_________________
Spirit System developer

Hello,

thanks for the response. I think the driver is properly installed. I assume this, because when assigning the USB device to the Windows 11 VM the WIndows App of Spirit Settings is working fine.

Both devices are available

/dev/cu.usbserial-0001
/dev/tty.usbserial-0001

Which device name is searched in the Spirit Settings App?
What is the criteria that you assume that the USB driver is not installed properly?


What is the correct device?

When USB dongle is connected to USB A port I see this:

ml@Mac-Studio ~ % ioreg -p IOUSB
+-o Root <class IORegistryEntry, id 0x100000100, retain 41>
+-o AppleT6000USBXHCI@03000000 <class AppleT6000USBXHCI, id 0x10000049e, registered, matched, active, busy 0 (7 ms), retain 39>
+-o AppleT6000USBXHCI@05000000 <class AppleT6000USBXHCI, id 0x1000004cc, registered, matched, active, busy 0 (2 ms), retain 39>
+-o AppleT6000USBXHCI@04000000 <class AppleT6000USBXHCI, id 0x1000004c4, registered, matched, active, busy 0 (5778 ms), retain 104>
+-o AppleT6000USBXHCI@00000000 <class AppleT6000USBXHCI, id 0x1000004d0, registered, matched, active, busy 0 (7 ms), retain 39>
+-o AppleT6000USBXHCI@01000000 <class AppleT6000USBXHCI, id 0x10000043b, registered, matched, active, busy 0 (5 ms), retain 39>
+-o AppleT6000USBXHCI@02000000 <class AppleT6000USBXHCI, id 0x100000433, registered, matched, active, busy 0 (5 ms), retain 39>
+-o AppleEmbeddedUSBXHCIASMedia3142@08000000 <class AppleEmbeddedUSBXHCIASMedia3142, id 0x100000d18, registered, matched, active, busy 0 (378 ms), retain 73>
| +-o USB Receiver@08300000 <class IOUSBHostDevice, id 0x100000de2, registered, matched, active, busy 0 (242 ms), retain 44>
| +-o CP2102 USB to UART Bridge Controller@08400000 <class IOUSBHostDevice, id 0x100011fde, registered, matched, active, busy 0 (69 ms), retain 20>
+-o AppleUSBXHCITR@06000000 <class AppleUSBXHCITR, id 0x10000d4b2, registered, matched, active, busy 0 (460 ms), retain 202>
+-o USB2 Hub@06100000 <class IOUSBHostDevice, id 0x10000d4bd, registered, matched, active, busy 0 (394 ms), retain 29>
| +-o Studio Display@06140000 <class IOUSBHostDevice, id 0x10000d4da, registered, matched, active, busy 0 (363 ms), retain 81>
+-o USB3 Gen2 Hub@06300000 <class IOUSBHostDevice, id 0x10000eb89, registered, matched, active, busy 0 (41 ms), retain 26>


And when it's connected using a USB-C to USB-A adapter I see this:

ml@Mac-Studio ~ % ioreg -p IOUSB
+-o Root <class IORegistryEntry, id 0x100000100, retain 41>
+-o AppleT6000USBXHCI@03000000 <class AppleT6000USBXHCI, id 0x10000049e, registered, matched, active, busy 0 (7 ms), retain 39>
+-o AppleT6000USBXHCI@05000000 <class AppleT6000USBXHCI, id 0x1000004cc, registered, matched, active, busy 0 (2 ms), retain 39>
+-o AppleT6000USBXHCI@04000000 <class AppleT6000USBXHCI, id 0x1000004c4, registered, matched, active, busy 0 (5830 ms), retain 110>
| +-o CP2102 USB to UART Bridge Controller@04100000 <class IOUSBHostDevice, id 0x10001201b, registered, matched, active, busy 0 (51 ms), retain 20>
+-o AppleT6000USBXHCI@00000000 <class AppleT6000USBXHCI, id 0x1000004d0, registered, matched, active, busy 0 (7 ms), retain 39>
+-o AppleT6000USBXHCI@01000000 <class AppleT6000USBXHCI, id 0x10000043b, registered, matched, active, busy 0 (5 ms), retain 39>
+-o AppleT6000USBXHCI@02000000 <class AppleT6000USBXHCI, id 0x100000433, registered, matched, active, busy 0 (5 ms), retain 39>
+-o AppleEmbeddedUSBXHCIASMedia3142@08000000 <class AppleEmbeddedUSBXHCIASMedia3142, id 0x100000d18, registered, matched, active, busy 0 (382 ms), retain 67>
| +-o USB Receiver@08300000 <class IOUSBHostDevice, id 0x100000de2, registered, matched, active, busy 0 (242 ms), retain 44>
+-o AppleUSBXHCITR@06000000 <class AppleUSBXHCITR, id 0x10000d4b2, registered, matched, active, busy 0 (460 ms), retain 202>
+-o USB2 Hub@06100000 <class IOUSBHostDevice, id 0x10000d4bd, registered, matched, active, busy 0 (394 ms), retain 29>
| +-o Studio Display@06140000 <class IOUSBHostDevice, id 0x10000d4da, registered, matched, active, busy 0 (363 ms), retain 81>
+-o USB3 Gen2 Hub@06300000 <class IOUSBHostDevice, id 0x10000eb89, registered, matched, active, busy 0 (41 ms), retain 26>


Kind regards

Michael

i have no problems on M1 Macbook Air - runs on macOS directly as well Win11 ARM VM under Parallels like a charm (in my case always with adapter A/C).

which version of the SiLabs driver are you using? I am on SiLabsUSBDriverDisk_V6.0.1.dmg

Ciao
Michael

_________________
cheers
Michael

It has to see /dev/ttySilabs... device. Here we have 2 Mac computers with M1 and they works well. Just according the guide.

_________________
Spirit System developer

Please note when using a Virtual Machine then USB is completely unused by the Mac and is used only by Virtual Machine.
So it does not matter if Mac has a driver or not. It depends on system which is installed there.

In some Mac configuration you have to manually allow installed drivers, because system policy does not allow loading it for security reasons.
So it must be allowed in the recovery mode of the Mac. But this is not default configuration of Mac, so this should not happen normally.

More likely you have missed button to allow the driver during installation. This is very important.

_________________
Spirit System developer

Hello,

thanks for all your hints. I got it running now. But very strange way. I have to login as Admin to macOS and run the installer. RUnning the installer from normal user wasn't working even that he asked for admin account credentials. Never had this issue.

But as said, now it is working.

Kind regards

MIchael