As I mentioned in a couple of firmware-related threads - I was looking into automating the SPI FW image building and I've come up with an initial version of the script, which does the thing for me without the need of going through the BSP step-by-step and mess up with calling all specific tools from specific places in a specific way 🙂 I hope it's going to be useful for the community and I'm willing to support and develop it if there's an interest.
One current limitation worth mentioning is that it doesn't build the Linux part for yet (that "bitbake image-spi" thing). You'll need to provide the script with the respective files. If this whole thing takes off and there's a demand for that - that could be added later.
By default it builds the BSP v0.8.0 for those who want the bleeding edge, but you can easily reconfigure it by commenting/uncommenting a few lines at the beginning of the script (see comments there).
You can find it on the GitHub and you're more than welcome to use it, test it, break it, like it or hate it 🙂 as well as report bugs and share your success stories!
https://github.com/alext-mkrs/galileo-fw alext-mkrs/galileo-fw · GitHub
And one more thing - to Clanton team, if you read this - it would help a ton if you could stick to the same naming convention for EDK tools package (tarball itself and the dir inside) - that would make the build configuration more elegant and easy.
Sysimage and spi-flash-tools are just fine, but the EDK one has different names between the BSP versions (0.7.5 and 0.8.0) and in addition - the directory name inside the tarball doesn't match the name of the tarball itself, which requires inelegant workarounds in the code 🙂
For everyone's information, I have updated my FW building script, the no-longer-working link to 0.8.0 was removed, and additional logic needed for 0.9.0 added.
As an additonal bonus, by removing some unnecessary EDK build steps I have shortened a build time (only one out of four EDK configuration-target combinations is being built, namely PLAIN-RELEASE). I haven't specifically measured it, but it's quite noticeable, because EDK building is the longest piece.
As always - please make sure you know what you're doing when messing up with firmware to avoid unexpected results, keep in mind that the only officially validated with Arduino IDE firmware version is 0.7.5 and... have fun tinkering with your board! 🙂
Your feedback as to the script's functionality is more than welcome.
Good point! They have too many switches in gcc, I wouldn't even think they have such a special one beyond standard "--version".
Thanks, I'll update the script, submitted an enhancement request for myself: https://github.com/alext-mkrs/galileo-fw/issues/3 Use "-dumpversion" switch instead of "--version" to determine GCC version · Issue # 3 · alext-mkrs/galileo-fw · GitHub