I too am exploring a “better” way to import files from my development PC into the Pico’s file system. As one approach, I’d like to introduce a method in which Pico is temporarily booted with firmware designed for file operations.
https://github.com/oyama/pico-drive-sync
In this setup, the firmware is loaded into RAM and executed only once, leaving the original firmware stored in flash intact. In this example, a somewhat intricate method is employed to mount the littlefs deployed in flash onto the PC; however, if FAT is used instead, the implementation should be much simpler.
Furthermore, if you deploy the file system with the same layout as MicroPython, you can leverage file transfer tools provided for MicroPython—such as Thonny (https://thonny.org).
https://github.com/oyama/pico-drive-sync
In this setup, the firmware is loaded into RAM and executed only once, leaving the original firmware stored in flash intact. In this example, a somewhat intricate method is employed to mount the littlefs deployed in flash onto the PC; however, if FAT is used instead, the implementation should be much simpler.
Furthermore, if you deploy the file system with the same layout as MicroPython, you can leverage file transfer tools provided for MicroPython—such as Thonny (https://thonny.org).
Statistics: Posted by 0yama — Sun Feb 02, 2025 7:11 am