You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to directly generate LFS files on the computer and write them into the device's flash to add files to the device's LFS, as the network download speed of the device is slow and inconvenient for debugging.
I use the littlefs Python library to generate LFS files, and this is the link to this library https://github.com/jrast/littlefs-python
After testing, it was found that there were a few successful attempts to mount and read the files inside. Most of the time, after writing to the lfs file, the device will mount fail, or the mount will succeed but the file cannot be read.
I noticed that the LFS file generated by the library starts recording directly from Super Block 3, while the device's LFS starts recording from Super Block 2, which should be the biggest difference. Then I first perform repeated write operations on the device, and wait until the operation record starts using Super Block 3 before writing the library generated LFS file to flash. However, it has no effect and still fails.
What is the difference that caused the mounting failure? Or what should I do?
Attached below are the LFS files generated by the library and the device, hoping to be helpful bin.zip
The text was updated successfully, but these errors were encountered:
I want to directly generate LFS files on the computer and write them into the device's flash to add files to the device's LFS, as the network download speed of the device is slow and inconvenient for debugging.
I use the littlefs Python library to generate LFS files, and this is the link to this library https://github.com/jrast/littlefs-python
After testing, it was found that there were a few successful attempts to mount and read the files inside. Most of the time, after writing to the lfs file, the device will mount fail, or the mount will succeed but the file cannot be read.
I noticed that the LFS file generated by the library starts recording directly from Super Block 3, while the device's LFS starts recording from Super Block 2, which should be the biggest difference. Then I first perform repeated write operations on the device, and wait until the operation record starts using Super Block 3 before writing the library generated LFS file to flash. However, it has no effect and still fails.
What is the difference that caused the mounting failure? Or what should I do?
Attached below are the LFS files generated by the library and the device, hoping to be helpful
bin.zip
The text was updated successfully, but these errors were encountered: