The virtual hardware is among other purposses meant
to be used for debugging firmware issues.
The flag -Os optimizes out specific information that makes
proper debugging difficult in some situations.
Also, the virtual hardware does not come with restrictions
in terms of PROGMEM. That's why space efficiency is not needed there.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
Some parts were moved over from Kaleidoscope-Hardware-Virtual.
The virtual hardware is now a drop in for the real
pluggable USB interface.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
Consumer code can access the command line via
an additional callback of the virtual hardware.
This makes it possible to access the name of
the executable that is currently executed.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
By this means it is possible to simplify running automatic
simulation based testing with virtual firmare builds.
If a firmware sketch defines a test function it will
be executed.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
Through a command line parameter, the virtual
firmware executable can be instructed to execute
a testing function instead of processing
stdin/stdout I/O.
This can be used to attach an external
testing interface.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
