UF2, to my knowledge, is just a container for pages of data with some metadata attached. When the bootloader gets a UF2 block sent from PC, it checks where to write it to and then flashes the data directly to that page in the chip. I agree, that function is not using any flash storage other than what the code resides in. Seems that functionality could remain in place - when a file is written, check each block for the UF2 magic and if so - flash it.
I'll check out circuitpy bootloader. I was looking at the mass storage examples from Atmel and others to get a better understanding on how an actual flash drive services requests. Seems reasonable, but not that small.
Yep circuitpy flash drive emulation is very slick. But damn is that code a massive tangle!
I'll check out circuitpy bootloader. I was looking at the mass storage examples from Atmel and others to get a better understanding on how an actual flash drive services requests. Seems reasonable, but not that small.
Yep circuitpy flash drive emulation is very slick. But damn is that code a massive tangle!
Last edited by electronrancher,









