Meadow cli issue on macOS Monterey / Apple Silicon

I have 2 Meadow F7v1 boards that I am unable to connect to properly from macOS Monterey (12.6) running on an M1 Mac.

If I run meadow list ports I get back /dev/tty.usbmodem346A386535361
I set this port by running meadow use port /dev/tty.usbmodem346A386535361

If I try and get the device info I get

❯ meadow device info
Connecting to Meadow on /dev/tty.usbmodem346A386535361
Unable to find Meadow.

If I set the F7 to DFU mode and run meadow flash os this starts to work but ultimately errors with

Meadow.CLI.Core.Exceptions.DeviceNotFoundException: Could not find a connected Meadow with the serial number

I have managed to try this on an older intel Mac running macOS Catalina (10.15) and everything works as expected.
Both systems have the latest .NET 6 SDK installed and dfu-util v0.11, so this would appear to be some specific issue related to either the OS or the CPU Architecture.

Anyone have any ideas about how to fix?

@jack We have an internal build working on M1/2 and hope to get it out by RC2.

I see the docs now mention that x86/Rosetta is required (for now) too :+1:.

(I did think I was going crazy for a moment, but I had an old tab open with the previous version of the docs :sweat_smile:)