Hello,
To manage and persist data processed by the Pico, it's essential to utilize a storage medium. In a general computer OS, this requirement is fulfilled by the presence of a storage medium coupled with a unified API (such as `open(2)`, `read(2)`, `write(2)`, etc.) presented through the file system. However, given that the Pico operates without an OS as a microcontroller, users aiming to achieve a similar functionality must piece together their own building blocks.
Motivated by the absence of a succinct guide for pico-sdk newbies on this topic, I've prepared a draft document.
https://gist.github.com/oyama/4596eca4c ... d1e55e94ca
I'm seeking feedback to enhance its content and utility. You are also welcome to provide references to them if you already have them.
Regards,
To manage and persist data processed by the Pico, it's essential to utilize a storage medium. In a general computer OS, this requirement is fulfilled by the presence of a storage medium coupled with a unified API (such as `open(2)`, `read(2)`, `write(2)`, etc.) presented through the file system. However, given that the Pico operates without an OS as a microcontroller, users aiming to achieve a similar functionality must piece together their own building blocks.
Motivated by the absence of a succinct guide for pico-sdk newbies on this topic, I've prepared a draft document.
https://gist.github.com/oyama/4596eca4c ... d1e55e94ca
I'm seeking feedback to enhance its content and utility. You are also welcome to provide references to them if you already have them.
Regards,
Statistics: Posted by 0yama — Thu Apr 11, 2024 7:26 am — Replies 0 — Views 15