Use all-public classes instead of structs, they have a proper initialization using their constructor and init lists.
Adding API layer and HAL place holder function for flashing new firmwares.
Will fill in the acutal functionality when I have internet conn. again... :)
Fix some compiler warnings, add suprafluid braces... :)
Add (yet) empty dictionaries file to "utils"
This is part of issue #11
Include dictionaries in api.cc, add some comments to the dict file.
Part of issue #11
API CHANGE: initDUT now accepts the parameter sets agreed on in yesterday's meeting
Rewrite of the initDUT function to parse the input correctly and initialized the DUT struct.
Currently missing are both sanity checks for incoming data as well as the actual programming
of the devices via _hal.
This is part of issue #10.
one could also think about a "_dirty" flag for the DUT, set when changes are written to it,
reset as soon as the parameters have been programmed successfully.
Move testpxar executable to its own directory ("debug") in order
not to disturb development of the main executable.
Make testpxar aware of the changed API interface. Now initializing the DUT with the proper command (hopefully the final syntax...)
DUT: Add possibility to mask pixels.
DUT: add info() function printing, well, info. (the current state of the DUT)