will-v-pi

> If the Bazel checks are getting in your way, you can add the two new files to a `filegroup` (which will silence the error) and file an issue+leave a...

> > A Wi-Fi firmware partition is detected as having the ID 0x123456789abcdef0, and the UF2 family_is for Wi-Fi firmware blobs is 0x12345678 - these should probably both be changed...

> Would MicroPython be able to use the same Wifi firmware partition as C-SDK code? (or is that another one of my stupidly naive questions? 😆 ) Yes, they definitely...

I've noticed an issue with the Risc-V build of the firmware UF2 - for some reason the compilation is putting a programme header in the ELF with offset of `0x0000`...

I've now got it working for Risc-V by storing copies of the firmware ELFs in the SDK, and then copying those into the build when necessary. It also needs increased...

Rebased onto develop, which contains the `rom_pick_ab_update_partition` function

> However when I check by picotool, I see following number set as partition ID: This looks like a bug in your build of picotool - for me it shows...

That use case will work fine - the embedded partition table in these binaries will be ignored when they’re booted from partitions by the bootloader (as opposed to when they’re...

> > That use case will work fine - the embedded partition table in these binaries will be ignored when they’re booted from partitions by the bootloader (as opposed to...

Would we want to use the next family ID for this then (`0xe48bff5c`), and add a define into the SDK and picotool for it (`WIFI_FIRMWARE_FAMILY_ID`)?