I recently upgraded to macOS 26.0, and most of the times when I flash my Daisy Patch Rev3 with the STM debug probe the flashing process gets stuck here:
** Programming Started ** Info : Device: STM32H74x/75x Info : flash size probed value 128k Info : STM32H7 flash has a single bank Info : Bank (0) size is 128 kb, base address is 0x08000000 Info : Padding image section 1 at 0x0800e9c4 with 28 bytes (bank write end alignment) Warn : Adding extra erase range, 0x0800e9e0 .. 0x0801ffff
I am saying most of the times as the issue is not 100% reproductible. As far as I have experienced, I can do a fresh new firmware update upon plugging the Daisy, then if I try to re-build and flash, the process gets stuck.
Unplugging and plugging Daisy back to the computer does not always solve the issue. Sometimes it does, sometimes not and I can’t find a way to properly reproduce the problem.
Did anybody encounter something similar? I did not experience this issue with older macOS but it’s a pain to downgrade.
We haven’t upgraded to Tahoe but can’t imagine how it can mess with flashing to Daisy.
One of the engineers may upgrade soon and see if something similar is encountered.
Was there something else that changed in your setup around the time the upgrade happened?
After reading the comments above and trying to further troubleshoot, I run into another issue - the STLINK was not being seen by my mac. This was not the case when I wrote the original post.
I tried all sorts of toolchain reinstall procedures, macOS update again to Tahoe 26.0.1, USB cable and USB port swaps, and then the STLINK was again seen by the computer.
Then I tried to flash the Daisy and I did not experience any failure. I tried again several times and everything went smoothly. I really cannot tell where the original issue was, but thank you for your support anyway.
I did the update today, just to see if anything new came up. Seems okay to me.
One thing that I have noticed with the Apple silicon Macs, regardless of OS, is that the USB-C ports seem to have extremely finnicky, and inconsistent behavior with the ST-Link Debug probes. In my case, this happens on the ports on the mac, or when using a dock, or other USB-C hubs.
This is observed as either init-failed errors, stalling in the middle of programming, etc. So it’s possible this is what you were running into.
What I have found to be a reliable solution is to use a cheap USB 2.0 hub, and a USB-C to USB-A connector between the ST-Link and the macbook ports. Connected this way, I don’t think I have had any of the reliability issues come back.