ETISS initialize exposes configuration options that are not used by the neither core nor architecture. This leads to false feedback to users implying such options exists "out of the box". Some examples:
etiss.enable_dmi the "direct memory interface" seems to be something from for systemc wrapper of the CPUCore - no usage in standalone ETISS
etiss.log_pc is only checked in the example bare etiss processor to activate an additional plugin
vp.sw_binary_ram no usage, deprecated since existing SystemWrappers now rely on ELF files
vp.sw_binary_rom ""
The ETISS-Core should only expose options that it can also handle. While options like etiss.log_pc are used in the example, the example should expose its "extending" features, but not the Core.
ETISS initialize exposes configuration options that are not used by the neither core nor architecture. This leads to false feedback to users implying such options exists "out of the box". Some examples:
etiss.enable_dmithe "direct memory interface" seems to be something from for systemc wrapper of the CPUCore - no usage in standalone ETISSetiss.log_pcis only checked in the example bare etiss processor to activate an additional pluginvp.sw_binary_ramno usage, deprecated since existing SystemWrappers now rely on ELF filesvp.sw_binary_rom""The ETISS-Core should only expose options that it can also handle. While options like
etiss.log_pcare used in the example, the example should expose its "extending" features, but not the Core.Related code sections, where options are defined: https://github.com/tum-ei-eda/etiss/blob/36902d32ae760aa3c413ca06189e6515bc28d79c/src/ETISS.cpp#L721-L753