Why use that name that doesn't include the baud like the others?
It seems be yet another inconsistent ambiguous file name for a pre-built bootloader.
And since the .lst file is not there, it is particularly difficult to tell what is in that .hex image.
Why can't we use better more descriptive file names that are all consistent with each other?
I'd like to use my previous recommendation for all the bootloader names so people know how they were built and what the heck is in them.
i.e here are the names I suggested for the existing bootloaders in the repo at this point in time:
It would also be good to add the other B7 bootloader that I gave you:
So SB users could re-burn their blinking led bootloader that came with the board.
And bobuino uses could also have a blinking bootloader if they wanted it.
Given all the issues and confusion over the bootloaders and their contents, I'm not understanding the reluctance to use better and more consistent names for the pre-built bootloaders so people can look at the file and tell what they are going to get.
Also, what I've noticed is that when building optiboot with the newer compiler tools, the .lst file is not very useful as the code is optimized differently and the objdump tool no longer inserts the C code for main() which is pretty much all the code. So unless you weed through the actual machine code you can't tell how the code was built.
So when using the newer tools, using the more descriptive names becomes even more important.
Once things are properly renamed you could avoid needing some pre-built bootloaders to save on files.
You could get away with just doing 8Mhz and 20Mhz prebuilt bootloaders.
The 8Mhz 57.6k B7 led bootloader is the same as the 16Mhz 115.2k B7 led bootloader so the boards.txt could use that instead of having to supply both.
In other words you don't need both the 16Mhz and 8Mhz versions of prebuilt bootloaders since they can be shared for the two clock rates since the 8Mhz baud rates can be used to get 16Mhz 57.6, 115.2 and 1M or they could all be called 16Mhz bootloaders which also get 28.8, 57.6 and 500k at 8Mhz
But I still strongly believe that the key to removing so much of the confusion and issues is to name the files consistently with better names that include build parameters.
And if addtional NOled bootloaders are wanted/needed just add them.