Building a Tiny CLI Shell for Tiny Firmware | Interrupt

Thank you for this post, @tyler! I love the follow-up step of wrapping this into invoke scripts :slight_smile:

Among other opportunities you mentioned

receive files from a device’s file system

Are you aware of a standard way of doing this (e.g. file size and suggested file name upfront, transfer of multiple files at once, maybe even compression)? In the past, we were particularly struggling with log messages being interleaved with logs from unrelated sources. In our system, logs (e.g. crash dumps of processes) could even produce a file “spontaneously” at the same time one would interact with the CLI. We ultimately decided to store those files away instead of logging them (and later fetching them using a different method).

I recognize that this could be too unrelated to your use-case. In that case, would you recommend trying to isolate the CLI output from everything else during an interaction to make the CLI use-case itself as simple as possible?