Yocto build script

Hi everybody,

I made a build script using Docker that lets you compile the sources to a .syx file under Linux.

https://gitlab.com/jacobvosmaer/yocto-build

Sharing here in case others want to use it.

I am not an Arduino expert so use at your own risk!

I just tested in on macOS and it works there too. Yay!

I will update the title of the topic to indicate that this is not just for Linux.

It should work on Windows too but I can't test that myself. I don't know how easy/hard it is to use Docker on Windows. If Docker works, the script should work too.

This is cool, thanks!

I just put the Yocto source up on GitHub (https://github.com/HomoElectromagneticus/Yocto_808), I wonder if there is a way to integrate the code there with this build system?

I'm working on that right now.

https://gitlab.com/jacobvosmaer/yocto-f ... lab-ci.yml

It's not quite done yet.

It works now. You can download the .syx file in a zip with https://gitlab.com/jacobvosmaer/yocto-f ... ?job=build

It builds in under a minute.

Looks like it's working on Windows 7 x64 via Docker Toolbox!

For your second command...

Code: Select all

# In the yocto-build directory
docker run -v /path/to/yocto-build:/yocto yocto

...I had to adjust the syntax for the path basically like described here: https://stackoverflow.com/questions/402 ... ot-working

Code: Select all

"So I used the command
docker run --publish=7474:7474 --volume=/c/Users/USERNAME/neo4j_test/data:/data neo4j
isntead of
docker run --publish=7474:7474 --volume=C:/Users/USERNAME/neo4j_test/data:/data neoj
and it is working now."

YMMV

That's great! So you had to replace

Code: Select all

C:

with

Code: Select all

/c

and that was it?

Yes, that was it. Depends on where you place your yocto-build folder, of course. Looks like it's simpler if you place it in your home folder (e.g. pointing to "c:\Users\[your username]\yocto-build\" would be a convenient "~/yocto-build" in Docker Toolbox).

However, is it normal that both the hex and syx files built by this script from the unchanged "official" source are about 3kb smaller than the "official" hex and syx you can download from e-licktronic? My Yocto wasn't accepting the syx. I tried sending it at different speeds but the Yocto seems to ignore the upload and revert to the existing firmware. Then I saw the size difference. Any thoughts?

I have noticed that size difference too and I don't know why it is. Might be because of a different -O optimization level on avr-gcc, I don't know what Arduino uses.

How do you know the Yocto is ignoring the new firmware?

I've had issues too where new firmware seemed to be accepted by the bootloader but nothing changed. But in each case that turned out to be because of MIDI problems on the sending side. For example the delay between sysex messages (I use 200ms).