summaryrefslogtreecommitdiffstatshomepage
path: root/lib/utils/pyexec.c
diff options
context:
space:
mode:
authorMaureen Helm <maureen.helm@nxp.com>2019-12-30 17:46:17 -0600
committerDamien George <damien.p.george@gmail.com>2020-02-07 11:24:06 +1100
commit7a5752a7489f6be1c7307455b33119888392a09d (patch)
tree7938aafce6d38865ae5aa28fe33be5581d04ce6a /lib/utils/pyexec.c
parent86a66960f9a3538de9d48abb719975741569495f (diff)
downloadmicropython-7a5752a7489f6be1c7307455b33119888392a09d.tar.gz
micropython-7a5752a7489f6be1c7307455b33119888392a09d.zip
zephyr: Enable littlefs.
Enables the littlefs (v1 and v2) filesystems in the zephyr port. Example usage with the internal flash on the reel_board or the rv32m1_vega_ri5cy board: import os from zephyr import FlashArea bdev = FlashArea(FlashArea.STORAGE, 4096) os.VfsLfs2.mkfs(bdev) os.mount(bdev, '/flash') with open('/flash/hello.txt','w') as f: f.write('Hello world') print(open('/flash/hello.txt').read()) Things get a little trickier with the frdm_k64f due to the micropython application spilling into the default flash storage partition defined for this board. The zephyr build system doesn't enforce the flash partitioning when mcuboot is not enabled (which it is not for micropython). For now we can demonstrate that the littlefs filesystem works on frdm_k64f by constructing the FlashArea block device on the mcuboot scratch partition instead of the storage partition. Do this by replacing the FlashArea.STORAGE constant above with the value 4.
Diffstat (limited to 'lib/utils/pyexec.c')
0 files changed, 0 insertions, 0 deletions