Suggestion

[epsi1on]

First of all thanks and congrats for the innovative project. Currently the compiled firmware (I mean /build/rp2daq.uf2 file) is placed inside the project files. I would like to suggest you to publish the compiled binary file as a release file. I think this is how usually the binary files are published in github. also the version control would be easier and files can be visible from release section: https://github.com/FilipDominec/rp2daq/releases

[FilipDominec]

Thanks, I will do it like yuo describe. Currently, the automatic push of new binary firmware on every ABI change is inefficient.

[FilipDominec]

Done. For the latest current version of the released pre-compiled firmware, please always refer to the link:

https://github.com/FilipDominec/rp2daq/releases/latest/download/rp2daq.uf2

Note however that the binary message format may and will differ between versions as I add new firmware features in the git repository now and then.

If you wish to communicate with a given version of firmware, you absolutely have to refer to the corresponding version of the C source code.

https://github.com/FilipDominec/rp2daq/releases/latest/

I also updated README.md to reflect this.

Thanks for your suggestion.

[epsi1on]

Wonderful. I should put a check for firmaware version in scope. Does the returned firmaware version from PICO do change for each individual release? I mean the 34 bytes after 0x01,0x00,0x01 which send from RPI to PC, does it change for each release? can i use it for firmware version detection?

[FilipDominec]

It should represent the latest date the firmware ABI was updated (breaking binary compatibility), but haven't been overly conscientious about it in previous months.

Anyway, the latest release as well as current git version of rp2daq return human-readable 6-byte string "231005".

[epsi1on]

ok, thanks