Some OS's (plus maybe some differences in file browsers?) send data out of order. Should just use UF2 block count to determine where to write in flash instead of order the data is sent in.
Basic idea will be to erase all necessary flash when we get the "first" (first one we get, not block 0), then write. Only potential hangup will be if the OS gets mad at the large delay at the beginning, since flash erases take a relatively long time.
Some OS's (plus maybe some differences in file browsers?) send data out of order. Should just use UF2 block count to determine where to write in flash instead of order the data is sent in.
Basic idea will be to erase all necessary flash when we get the "first" (first one we get, not block 0), then write. Only potential hangup will be if the OS gets mad at the large delay at the beginning, since flash erases take a relatively long time.