As per subject, I'm asking if is it possible to "embed" or "hardcode" the configuration options (that are in the config.txt inside the SD card) inside the firmware, similarly to configuration of Marlin-like firmwares.
I understand the pros of having a very easy to read and modify config.txt file; it is highly customizable and the operation of the smoothieboard is very easy also for newbie of the 3D printing.
My concern regards the use of a configured machine to a third party user that, not only does not need, but also Must not modify/delete this file.
Deleting accidentally the file from the SD results in the machine not booting up and, for example, an uncorrect modification of the parameters can lead to damage to the machine.
My idea is that once the config was done, it has to be part of the firmware or locked in some way, so the user can manage the SD card without worry (can delete, format the card etc..).
I'm not asking to change the approach or to modify the firmware philosophy, only if there is an easy and alternative way to do this :-)