Ah, this brings up a good point about the Programmer application. The 404 is simply for the README of additional information. A lot of the DaisySP examples don’t have READMEs yet, but they’re very simple examples that generate sound based around one of the DaisySP modules.
I’ll start populating READMEs for those examples, and also fix up the 404 display message to simply say that additional information about the example is not available. As long as the “File Location” field updates you can still program the example to your Daisy even if there is no additional info.
As for your arm-none-eabi-gcc issues, I haven’t personally seen that issue, but it looks like it could be a binary incompatibility with your machines architecture. Can you describe the machine you’re trying to run (processor architecture, distro, etc.)?
Also, there are a lot of places with the toolchain on the internet, looking at the arm developer site, this is most likely the toolchain you want It’s the x86_64 linux binaries.