In our current workflow using FileX, we are able to successfully generate pre-baked FAT16 flash images on our Linux development host using standard system tools (such as dd). We then write these pre-populated filesystem images directly to our storage media during production flashing.
We are now incorporating LevelX into our architecture and want to achieve a similar workflow where we can pre-populate a FAT16 filesystem within a LevelX-managed framework on our host development machine before production flashing.
Questions for the Development Team:
-
Is there an official, standalone host-side utility (Linux or Windows command-line) provided by the ThreadX/LevelX ecosystem that can format and inject files into a LevelX NOR image structure?
-
If no native tool exists, is the recommended best practice to compile a host-side (PC) simulation using lx_nor_simulator.c and use FileX APIs to write the initial asset files to a backing file?
-
Are there any hidden pitfalls we should be aware of regarding sector sizes, page alignment, or block overhead when relying on a host-simulated LevelX backing file for direct production flashing?
Thank you,
Aaron
In our current workflow using FileX, we are able to successfully generate pre-baked FAT16 flash images on our Linux development host using standard system tools (such as dd). We then write these pre-populated filesystem images directly to our storage media during production flashing.
We are now incorporating LevelX into our architecture and want to achieve a similar workflow where we can pre-populate a FAT16 filesystem within a LevelX-managed framework on our host development machine before production flashing.
Questions for the Development Team:
Is there an official, standalone host-side utility (Linux or Windows command-line) provided by the ThreadX/LevelX ecosystem that can format and inject files into a LevelX NOR image structure?
If no native tool exists, is the recommended best practice to compile a host-side (PC) simulation using lx_nor_simulator.c and use FileX APIs to write the initial asset files to a backing file?
Are there any hidden pitfalls we should be aware of regarding sector sizes, page alignment, or block overhead when relying on a host-simulated LevelX backing file for direct production flashing?
Thank you,
Aaron