When building the virtual boards, we want to have the base core as
`keyboardio:arduino`, instead of `arduino:arduino`, because we provide the base
ourselves. To this end, instead of symlinking `avr/boards.txt` and
`virtual/boards.txt`, generate the latter from the former.
Once we have other architectures, such as SAMD, we can concat all the boards.txt
files and do the same `base.core` replacements.
This is a pre-requisite for keyboardio/Kaleidoscope#851.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
A linker .map file will be created as an additional build artifact.
This map file can be used for debugging symbol issues or for
firmware post-processing.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
This change adds a build recipe that pastes a header and footer file
to the preprocessed sketch file.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
Those members cause compiler warnings when using recent
compilers. The members are unused and can be safely removed as
they are inaccessible to derived classes.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
Only the virtual device knows about the size of its
EEPROM storage. Including device headers in the virtual
core is not intended (and technical not possible).
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
This file was introduced during an earlier stage of the
work on implementing a general virtual hardware. After
Kaleidoscope's device API redesign it is no more required.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
This makes the build much simpler as the FQBN
can now e.g. be given as keyboardio:virtual:model01
and the build process will automatically find the
virtual arduino core in virtual/cores/arduino
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
This considers improvements that already had been considered for the avr
architecture.
Signed-off-by: Florian Fleissner <florian.fleissner@inpartik.de>
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>
