Sim'n Tonic Forums

(please follow this template when submitting a new bug report, feel free to remove sections if they are not relevant)


Short description of the issue:

The updater is not finding the Firmware to update to

Setup (devices connected and how):

Just Nome II plugged direct into USB C on Mac mini

Steps to Reproduce:

Run the firmware uploader

Expected Behavior:

Find version 4.6 as I am on 4.5

Actual Behavior:
Cnnoth find any firmware

Nome generation (I or II) and Firmware version:

Nome II FW 4.5

More info:

Thank you for reporting this, but unfortunately I doubt this is solvable by code.

The problem is the one mentioned in the error message: the update software failed to connect to the internet to get the list.
More precisely, it failed to read the webpage https://fw.simntonic.com/ - can you try this in a browser? It should write something like "DEVICEIDLIST:..."

This could be caused by a firewall blocking the access, maybe the page is cached wrongly (then refresh in your browser and then try again) or maybe your mac has not given permission to the app to access the internet (if so you would get a popup asking you for the permission usually).

Alternatively, can you try the upgrade using the Config Tool or the U-SYNC Daemon. They use exactly the same library to update your Nome, but if it's a permissions issue then they might have the right permission.

With the url in Safari I do get the following..

DEVICEIDLIST:1:midronome;16:nome2

But none of the Simntonic apps can get there. I'll try on a different Mac, on my old Mac Pro it finds in, on the new Mac mini M4 it's not, Firewall was turned off.

What permissions should your apps have access to? I have seen no popup to give access.

Had this same issue-- Using the U-Sync Daemon worked for me!!

Custa1200 wrote: ↑02 Jun 2025, 16:14 But none of the Simntonic apps can get there. I'll try on a different Mac, on my old Mac Pro it finds in, on the new Mac mini M4 it's not, Firewall was turned off.

Huh interesting - I'll investigate. Thanks for the info!

Beanhat wrote: ↑02 Jun 2025, 23:21 Had this same issue-- Using the U-Sync Daemon worked for me!!

Thanks for the info. Would you mind trying again on the normal update software? If it works it will simply say that you are up to date.

@Custa1200 -> unfortunately I cannot reproduce this at all, I tried on multiple machines all on macOS 15.5. Do you have any "unusual" setting for Internet, like a VPN or a proxy?
The app does the same as Safari, really

Regarding the permissions, that was just a guess - on all my tests I've never had to give access. But could you maybe go to the System Settings > Privacy & Security and look around there if you see any warning or if you see that the app is blocked somehow.

But in any case - you could upgrade using your old Mac Pro, right?

Simon

Anyone solve this?
I'm on am M2 Mac and I'm running a KS version of Midronome, but I can't update FW and the Config app won't run as I'm on old FW and it throws the same error when you ask it to update FW.
I'm stuck?

Duffdaddy wrote: ↑09 Jun 2025, 12:49 Anyone solve this?
I'm on am M2 Mac and I'm running a KS version of Midronome, but I can't update FW and the Config app won't run as I'm on old FW and it throws the same error when you ask it to update FW.
I'm stuck?

Hi This sounds like a different issue - or do you get the same error message?

If you have an old firmware (3.0 or older), you will need to update the bootloader first . The software update tool should inform you about that but maybe the "failed to download firmware list" issue happens before it has time to check your Midronome.

Simon wrote: ↑10 Jun 2025, 09:17

Duffdaddy wrote: ↑09 Jun 2025, 12:49 Anyone solve this?
I'm on am M2 Mac and I'm running a KS version of Midronome, but I can't update FW and the Config app won't run as I'm on old FW and it throws the same error when you ask it to update FW.
I'm stuck?

Hi This sounds like a different issue - or do you get the same error message?

If you have an old firmware (3.0 or older), you will need to update the bootloader first . The software update tool should inform you about that but maybe the "failed to download firmware list" issue happens before it has time to check your Midronome.

I get exactly the same error. Identical.
I'm on FW v4. Update again?
I have run the update procedure and when the Midronome has UPG on screen I run U-Sync / Update and get exactly the same error.
I'm on a Mac on OSX 15.5 (24F74)

Oh I see - then yes on FW 4.0 you already have the new bootloader.
And yes the error should be the same on the U-SYNC Daemon or using the Updater or even the Config Tool - they all use the same mechanism for the update.

I will continue the efforts in investigating this, it's partcularly difficult since I cannot reproduce the issue at all, on any of the machines I have here.

I assume that just like for the others, the page https://fw.simntonic.com/ loads fine for you too?

Duffdaddy wrote: ↑10 Jun 2025, 11:55 I get exactly the same error. Identical.

Could you please check your firewall settings and your antivirus settings?
When you go in "Privacy & Security" on MacOS settings, do you see anything at the bottom (like "this application has been blocked")?

And how do you run the App - directly from the dmg file or did you copy it into a local folder first?

Thank you
Simon

EDIT: please check as well if you are using a VPN, and in Settings > Network > Your network (for example "Wi-Fi") > Details > Proxies, check that no Proxy is setup.

No security issues, nothing blocked. App is installed on HD, not running from DMG. No antivirus or proxy running.
I can access the FW link in my browser too, so that's not at issue.

Duffdaddy wrote: ↑15 Jun 2025, 10:12 No security issues, nothing blocked. App is installed on HD, not running from DMG. No antivirus or proxy running.
I can access the FW link in my browser too, so that's not at issue.

Thanks for checking (note that on all my tests the tool runs fine when run directly from the DMG - but I thought it was worth a shot).

I'm very sorry about this, I've tried many different machines and configuration and I cannot reproduce it at all.
I've also investigated a lot, trying to "blind guess" what the issue could be. I've made a new version for you, which you can download here.

This version has a small change which could be the issue (from the blind guessing), so if we are very lucky the problem is gone.
If not could you please try the following:

1. Copy the .app in your Downloads folder
2. Then open the Terminal app, and type (including the quotes):

   Code: Select all

   "./Downloads/Sim_n Tonic Firmware Update.app/Contents/MacOS/Sim_n Tonic Firmware Update" 

3. Then try to update as you did before

This will launch the app from the terminal and the terminal will show you the log with a bit more information. Could you please copy/paste what it writes?

Thank you

I've solved this by doing the update on my PC. Just wouldn't work on my MacBook and I can't find out why. Sorry.

Duffdaddy wrote: ↑02 Jul 2025, 02:48 I've solved this by doing the update on my PC. Just wouldn't work on my MacBook and I can't find out why. Sorry.

That's more than fair - sorry about this.

If anybody else has a similar issue, please try this:

Simon wrote: ↑16 Jun 2025, 23:28I've made a new version for you, which you can download here.

This version has a small change which could be the issue (from the blind guessing), so if we are very lucky the problem is gone.
If not could you please try the following:

1. Copy the .app in your Downloads folder
2. Then open the Terminal app, and type (including the quotes):

   Code: Select all

   "./Downloads/Sim_n Tonic Firmware Update.app/Contents/MacOS/Sim_n Tonic Firmware Update" 

3. Then try to update as you did before

This will launch the app from the terminal and the terminal will show you the log with a bit more information.

Cool cool. Very frustrating. Especially when there's no obvious reason.
Had a similar issue recently with the new install of Reason 13. Just wouldn't run.
Turned out the updated version of ReCycle was causing Reason to fail to launch, even if you didn't have ReCycle running.
There was a patch for ReCycle that fixed it but could I find this anywhere on their site. Nope. Facebook User group was the solution.