AP_Bootloader: Increment BL Protocol Version

[meee1]

This is required to identify boards that are not running the most current bootloader, and prompt for an upgrade. If there is another way to detect this, please let me know

[WickedShell]

I don't know of a better way, but I'd really like to get a git hash with a command to query it stuck in, if possible.

[peterbarker]

On Mon, 6 Jul 2020, WickedShell wrote: I don't know of a better way, but I'd really like to get a git hash with a command to query it stuck in, if possible.

I did actually do some work on that: #14768

[tridge]

instead of a git hash, a year, month, day as a uint32_t may be more useful. The GCS could then check if it is later than a specific date.

[WickedShell]

@tridge I'm good with both, but I'd really like the hash, just so I can tell if my custom bootloader was flashed or not... The hash may also more helpful if someone is flashing in a factory setting and compiled it locally from the tree. The date is definitely better for telling about updates, but the hash is needed for tracking reasons of what was actually flashed.

[auturgy]

Reproducible builds generally get killed by time stamps. I’d prefer to see us go with a hash.

…

On 8 Jul 2020, at 1:56 am, WickedShell ***@***.***> wrote:  @tridge I'm good with both, but I'd really like the hash, just so I can tell if my custom bootloader was flashed or not... The hash may also more helpful if someone is flashing in a factory setting and compiled it locally from the tree. The date is definitely better for telling about updates, but the hash is needed for tracking reasons of what was actually flashed. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.