Brian Pugh

we should also really have some wear leveling with savestates; but that'll semi come-for-free once we use a filesystem.

where did you get this example from? It seems like quite an old version. Make sure you're running up to date `esp_littlefs`, as well as an up to date example.

After initializing the littlefs filesystem (like in the demo code), you can access folders like you would like in normal C code. E.g. https://stackoverflow.com/questions/1271064/how-do-i-loop-through-all-files-in-a-folder-using-c

hi @eldendiss thanks for all the findings! I'll try and work on this soon. As you've noticed, `mklittlefs ` certainly needs some attention.

Addressed some comments; will wait to write up examples until we determine if we want to change the interface.

@amirgon I believe I have addressed all the feedback, with the `register` command being the only item remaining.

so maybe this is actually a misunderstanding of `ToTensor` https://github.com/Jittor/jittor/blob/9e58fac49f3ebed8419fdb7c3faf5355f5f615b6/python/jittor/transform/__init__.py#L398 I would have expected it to mirror pytorch's `ToTensor` and convert PIL/numpy data into a jittor tensor, but it seems...

thanks, i'll check that out and raise an issue in that repo if my report is still valid.

ok so I cannot open issues in that repo for some reason. Basically I believe the issue is this: 1. When `port_sleep_until_interrupt` (or `port_idle_until_interrupt` in newer circuitpython) is called, `sd_app_evt_wait`...

I have implemented something similar here: https://github.com/BrianPugh/makerdiary-m60-config The important bits are (might need some imports depending on how you organize your code): ``` from time import sleep charger_in = digitalio.DigitalInOut(microcontroller.pin.P0_03)...