Jeff Epler 3d66ed27ce
oofatfs: enable use of random volume IDs
This may help address #7409 if the underlying cause is the deterministic
volume ID. However, not all boards have working urandom (samd21
at least does not) so a couple of fallbacks are attempted when it fails.

I verified that on a pico_w, each `storage.erase_filesystem()` gives
a distinct 32-bit volume ID (pico_w's urandom can never fail)
2023-01-03 17:18:29 -06:00
..
2018-08-07 14:58:57 -07:00
2022-08-03 16:19:40 -05:00
2022-04-18 14:09:36 +00:00
2022-11-21 16:24:05 -08:00
2022-08-04 16:06:27 -07:00
2021-03-18 16:55:42 -07:00
2021-03-15 19:27:36 +05:30
2022-11-21 16:24:05 -08:00