fvm.drom2psl package

Submodules

• fvm.drom2psl.basiclogging module
  • error()
  • info()
  • warning()
• fvm.drom2psl.definitions module
  • CONFIG
  • STRETCH
  • STRING
  • TYPE
• fvm.drom2psl.generator module
  • create_parser()
  • format_arguments_suffix_implication()
  • format_group_arguments()
  • format_group_arguments_in_call()
  • generator()
  • main()
• fvm.drom2psl.interpret module
  • adapt_value_to_hdltype()
  • assign_datatypes()
  • check_wavelane()
  • classify_value()
  • data2list()
  • exclude_data_types()
  • expand_concatenations()
  • flatten()
  • gen_sere_repetition()
  • get_clock_value()
  • get_group_arguments()
  • get_group_name()
  • get_signal()
  • get_signal_value()
  • get_type()
  • get_wavelane_data()
  • get_wavelane_name()
  • get_wavelane_type()
  • get_wavelane_wave()
  • is_empty()
  • is_pipe()
  • list_elements()
  • list_signal_elements()
  • process_concatenation()
  • process_value()
  • remove_parentheses()
  • remove_psl_operators()
  • split_concatenation()
• fvm.drom2psl.traverse module
  • traverse()
  • traverse_dict()
  • traverse_edge()
  • traverse_list()
  • traverse_other()
  • traverse_signal()

Module contents

Convert .json wavedrom files to .psl sequences

In order for this to be usable, we are assuming a number of things in the input .json files:

1. That the clock is the first signal that appears in the wavedrom

2. That only the clock carries the repeat zero-or-more symbol ‘|’

3. That the user has defined the datatype of any ‘data’ in a ‘type’ field in the wavelane, for example:

   {name: 'dat', wave: 'x.3x', data: 'data', type: 'std_ulogic_vector(31 downto 0)'},
   

4. That, if we have two top-level groups, then we are describing some relation between two sequences and thus a sample property will be generated in the PSL file relating the two sequences