Harmony Cart and Apple Silicon Mac?

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

SpiceWare

A while back I replaced my Intel based Mac Pro (2013 "trashcan") with an Apple Silicon based M2 Ultra Mac Studio.  Apple's Migration Assistant copied over the HarmonyCart program with all of my other programs.  It runs, but does not see my Harmony Cart:

Screenshot 2025-07-05 at 11.30.45 AM.png

Checking System Information the Harmony Cart does show up under the USB tree:

Screenshot 2025-07-05 at 11.30.29 AM.png

I suspect the device driver didn't migrate over as it was Intel specific. Anyone know what I need to install?

SpiceWare

Forgot to mention my Mac Studio's running macOS Sequoia 15.5

Andrew Davie

Can't help, but just a few musings.
1) If the USB tree shows the device, doesn't that imply the driver is there and working? Otherwise, how is the OS communicating with the device to get the info shown.
2) How is the Harmony software finding the correct USB device?  Does it iterate all USB items, or do you configure it somewhere?

The only experience I've had with MacOS and unusual USB devices is...

"If you want to get your AtariVox up and running quickly for MacOs....  If you use something like the YP-05 USB-serial converter, all you have to do is buy a male DB9 and connect the YP-05 GND to pin #8, VCC (5V) to pin #7, and TX to pin #1. It is not really necessary to worry about other pins. In a terminal window, do a ls /dev/cu*. - you should see the device appear/disapper as you plug in and remove.  Mine was "/dev/cu.usbserial-A50285BI". so that's the thing you put in "Avox serial port" under Input/Devices&Ports in Stella. And switch the Game Properties/Controllers/Right port to "Atari Vox" and you should be good to go."


So essentially, is there a "name" you have to enter for the Harmony software to find the cart to talk to?
Sorry I can't help - just trying to get some possibilities into your brain.

alex_79

#3
I can't help either, as I don't have a Mac, but if you can build the app from source, there's a "2.0 beta 4" version on the github repository last updated in ealry 2024.
The changelog says "Completely reworked serial port autodetection for Mac and Windows ports.", so it might be worth trying it.


SpiceWare

#4
That's a good point - if it's in the USB tree then macOS must be talking to it.

Checked the HarmonyCart program, don't see a place to specify a path to the serial device. There is a Device menu with a solitary option of Connect which causes the "Harmony Cart not found" message to briefly flicker to something else then back to the not found message.

The updated serial port detection sounds promising, though I think that's a planned change that hasn't actually been done yet because the macos directory in the commit lists 4 changed files:

  • OSystemMACOS.cxx
  • OSystemMACOS.hxx
  • SerialPortMACOS.cxx
  • SerialPortMACOS.hxx

and the windows directory contains 5 changes:
  • HarmonyCart.rc
  • OSystemWINDOWS.cxx
  • OSystemWINDOWS.hxx
  • SerialPortWINDOWS.cxx
  • SerialPortWINDOWS.hxx

but in each of those 9 files only a single line changed, the copyright:
// Copyright (c) 2009-2020 by Stephen Anthony

is now:
// Copyright (c) 2009-2024 by Stephen Anthony


I did download the source and tried src/macos/Create_build.sh. A DMG file* was created on my desktop, but the icon for the HarmonyCart program it contains is covered with a slashed circle(🚫) and doesn't run:

You can't open the application
"HarmonyCart.app" because it
may be damaged or incomplete.


I then noticed a configure program in the main directory, it fails with:

./configure: line 2: qmake: command not found

Looks like qmake is part of the Qt framework, which I'm not familiar with. Not sure if it's worth looking into Qt if the serial port detection changes haven't actually been done.


* a DMG file is a disk image, similar to an ISO, and is the typical way to distribute software for the Mac

Andrew Davie

ChatGPT gave a number of reasonable suggestions for diagnosing. I know it's cut/paste, but hey you may not have tried all these...



If your legacy Intel-based macOS program can't communicate with a serial device — even though the system sees the device in System Report — here are some focused, systematic steps to troubleshoot:

⸻

✅ 1. Check the serial device's path

In System Information (Apple menu > About This Mac > System Report), look under:

Hardware > USB or Hardware > Serial

Take note of any /dev/cu.* or /dev/tty.* device nodes.

In Terminal, you can also list serial ports with:

ls /dev/cu.*

Look for something like:

/dev/cu.usbserial-1410

This is the name your program should use to open the port.

⸻

✅ 2. Permission to access the device

You may not have permission to access the serial port. Try:

sudo chmod 666 /dev/cu.usbserial-1410

(Replace the filename as appropriate.)

Also, ensure the app has Full Disk Access:
    1.    Go to System Settings > Privacy & Security > Full Disk Access
    2.    Add your legacy program manually if it's not listed.

For macOS Ventura or later, also try enabling:
    •    Developer Tools or
    •    Files and Folders > Removable Volumes (if relevant)

⸻

✅ 3. Rosetta compatibility

If your legacy app is Intel-only and you're on an Apple Silicon (M1/M2/M3) Mac:
    •    Make sure it is running under Rosetta 2.
    •    Right-click the app in Finder > Get Info > check "Open using Rosetta" if the option is available.
    •    If it's a command-line tool, you may need to launch Terminal under Rosetta:
    •    Find Terminal in /Applications/Utilities/
    •    Duplicate it
    •    Right-click > Get Info > check "Open using Rosetta"
    •    Launch that version to run the tool

⸻

✅ 4. Driver compatibility (for USB-Serial adapters)

If you're using a USB-to-serial adapter (e.g., FTDI, Prolific, CH340), you may need drivers — and old drivers might not work on newer macOS versions.

Check:
    •    Is the driver Apple-provided? (macOS supports FTDI natively now)
    •    Or did you install a 3rd-party kext? That may no longer work post-Catalina/Big Sur due to System Integrity Protection (SIP) and driver deprecation.

Uninstall old kexts and try new DEXTs (DriverKit extensions) if the vendor provides them.

⸻

✅ 5. Test port with screen or minicom

Open the port manually:

screen /dev/cu.usbserial-1410 9600

If you can connect and send data manually, the issue is likely with the legacy app itself.

You can also use:

brew install minicom
minicom -D /dev/cu.usbserial-1410


⸻

✅ 6. App may not be using correct serial port name

Legacy code might assume a device name like /dev/ttyS0 or /dev/tty.usbmodem — update or configure it to point to the actual device name shown in /dev/cu.*.

⸻

✅ 7. Console logs

Check macOS logs for permission issues or serial I/O failures:

log stream --predicate 'eventMessage contains "usb"' --info

Or use Console.app to watch live logs while you try to connect.


Gemintronic

Bad answer from someone who knows not what he be do.

In the past I've resorted to using VMWare Fusion and a spare copy of Windows 10.  Mostly because even modern dev tools are more finicky on Macs.

Wondering if using a virtualized PC and the Intel versions of your utilities would play nice with a passed through USB / serial device.

SpiceWare

Like Andrew I've taken my leave of AtariAge, but just took a look in their Harmony support forum and see recent discussion about the HarmonyCart program not working under macOS Sequoia, Windows 11, or even Ubuntu 24.x or 25.x. On June 27th batari replied with some comments for Windows and ended with:

QuoteI will comment about Mac and Linux later

though he hasn't followed up on those yet.

I still need to review the ChatGPT results that Andrew posted.

Using a Virtual Machine is not a bad idea - I used to run Linux via VirtualBox to build my Atari projects such as Space Rocks because the original ARM compiler we used for the Harmony/Melody didn't have a Mac version. I haven't done that in a long time as we switched to a different compiler that supported Mac.

When I bought my Mac Studio in 2023 I stopped using VirtualBox as it only worked on Intel CPUs.  Looks like they now offer an Apple Silicon version, though has some limitations:

QuoteArm Host Limitations
The following limitations apply when using an Arm platform host:

  • Virtual machines must use an Arm-based guest operating system. Running an x86-based guest operating system on an Arm host platform is not supported.
  • Only VMSVGA is supported as a graphics controller.
  • Unattended installation isn't available.
  • The following System page settings aren't available for Arm guests:
    • Motherboard tab: Chipset, TPM
    • Processor tab: Extended Features such as Enable PAE/NX, Enable Nested VT-x/AMD-V

And apparently ARM versions of Windows are not yet supported, just ARM versions of Linux.

alex_79

Maybe you can open an issue on github. I think Stephen Anthony isn't very active on AA either these days, but he definitely is on github (at least in the Stella repo).

SpiceWare

Just noticed on GitHub that work on the Harmony Cart program has resumed. Looks like about 15 commits since November 30th.

alex_79


Bomberman94

Quote from: alex_79 on 19 Dec 2025, 12:31 AMVersion 2.0 has been released yesterday:

https://github.com/sa666666/harmonycart/releases/tag/release-2.0

Does it also include an update for the Harmony cartridge itself? 🤔

alex_79

Quote from: Bomberman94 on 19 Dec 2025, 01:16 AMDoes it also include an update for the Harmony cartridge itself? 🤔
No, the included bios images are 1.06 for NTSC and 1.05 for PAL/PAL60, which have been around for a few years.

SpiceWare

Quote from: alex_79 on 19 Dec 2025, 12:31 AMVersion 2.0 has been released yesterday:

https://github.com/sa666666/harmonycart/releases/tag/release-2.0

Thanks!

I've family arriving tomorrow for the holidays so will hopefully find some time today for a quick test while I'm finishing getting the house ready for guests. If not it'll be sometime after Christmas before I can try it out.

SpiceWare

#14
Had a little bit of time so installed it, but when I try to run it I get a warning dialog of:

"HarmonyCart.app" is damaged
and can't be opened. You should
move it to the Trash.

I've encountered security blocks from macOS before and know how to address those, but this is something different.

Out of time for now, will look into it more after Christmas.