ISSUES.md 1.7 KB
Newer Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# Maximum number of FIUs/Test cases

While the code within FIJI does not impose limitations on the number
of Fault Injection Units (FIUs) test cases in configuration files,
the GUI framework used for FIJI Setup and FIJI EE (Tk) as of 2017
contains some bugs that might make it impossible to display a high
number of GUI elements on screen. Some installations have been affected
by this and could not display more than about 300 FIUs.
The only known workaround is to edit the configuration files by hand for
all FIUs greater than this limit.


# No support for multiple instances of the same module

Currently FIJI does only support single instances of modules. However,
no netlist observed so far uses multiple instances of a single module.

Additionally, FIJI prints the driver path only as "module/pathname"
which is inconsistent with the full hierarchical path of the net itself.

What could be done:

* Print out the full hierarchical path of the driver.
  However, this might lead the user to think that FIJI actually supports
  multiple instances of a module.
* Check for duplicate modules when loading a netlist.
* Check for duplicate modules when validating a driver (by searching for
  a duplicate of the respective module at runtime or by comparing it
  with a list of duplicate modules created at netlist load time).
* Add support for duplicate modules.
  This would require to instrument the copy of a module.


# Verilog vs. VHDL

While FIJI expects Verilog netlists as input, many files generated by
it such as the top wrapper, FIC and FIUs are coded in VHDL only. Thus
any tools that have to process the instrumented netlist and these
generated files together (e.g., for synthesis) have to support both,
Verilog and VHDL.