Closed joernalraun closed 3 years ago
Do you want to verify the integrity only for the binary files in the repository (hex, bootloader, ...).
Do we plan to place the bootloader to the repository ...?
Yes, my intention was to ensure that we all talk about the same file version when talking about the Hex files. It can be quite hard, as multiple versions share the same name. This way we can be sure that we talk about the same file. The bootloader does not need to be included, but as this is a file we have been talking about a bit it might make sense to add it for a complete overview. However, this is also up for discussion. :)
Yes, my intention was to ensure that we all talk about the same file version when talking about the Hex files. It can be quite hard, as multiple versions share the same name. This way we can be sure that we talk about the same file.
All the HEX and JS files are here: https://github.com/rzbrk/CalliopEO_AstroPi/tree/main/testcases/testfiles. You could create a markdown file containing a table with name of hex file, the md5 and maybe a short description and the link to the testcases.
The bootloader does not need to be included, but as this is a file we have been talking about a bit it might make sense to add it for a complete overview. However, this is also up for discussion. :)
Is the bootloader proprietary, isn't it?
Is the bootloader proprietary, isn't it?
Yes, it is!
Is the bootloader proprietary, isn't it?
Yes, it is!
Should we then really put the bootloader into the repo?
We just wanted to mention which bootloader is used in the program description with a link to the official file on calliope and the md5 sum.
I added a chapter in the program description mentioning the bootloader version: https://github.com/calliope-edu/CalliopEO_AstroPi/blob/main/ProgramDescription.md#514-bootloader
Showing the individual md5 hashes should help to make sure that files are correct and the same.