will-v-pi

That CI failure is why I'm thinking this change doesn't want to have the check action, as the only change has been in the SDK so we don't really need...

> Hmmm, something that's just occurred to me: if a change was made to a comment in one of the `.c` files, I guess that might result in no change...

Also added a test build of pico-examples using latest clang, which would have caught this

This is due to the `.map` file being added by a linker script argument, so it is generated when compiling/linking, which on Ninja (and probably other generators too) is done...

Yes, this is all correct - it is the number of words of the block hashed, including the header word - `block_words_hashed` should probably be "Number of words of block...

> The problem I encountered is, that the bootloader often fails with other binaries than the hello_serial example. Can you share any of these other binaries, as this sounds like...

I've managed to reproduce this with the hello_usb example, and it seems to be an issue in `picotool encrypt` when there is a gap between the `.text` and `.rodata` sections...

Transfering this over to picotool, as that's where the elf2uf2 functionality is now I believe that I have fixed this (in a different way to raspberrypi/pico-sdk#329) for the `picotool uf2...

Picotool doesn’t require a built SDK, it just requires some of the SDK header files, so you should be able to build picotool first and then build the SDK. I’m...

Additionally, if you’re looking into packaging pico-sdk and picotool then I’d be happy to answer any other questions you have about them