Description
Currently, when performing a "Trace to Driver" operation (e.g., from the 'Netlist Hierarchy' panel or a canvas element), the viewer flattens the resulting driver logic and intermediate stages. The hierarchical nesting of modules and sub-modules is lost, making it difficult to understand the design's context and logic flow within complex, multi-level designs.
This feature requests that the schematic canvas and relevant trace tables maintain the full design hierarchy when displaying the trace results. It will be useful for the user to see bounding boxes representing parent modules nested around their children and leaf primitives, and the netlist paths should reflect this hierarchy.
For example, tracing from a terminal pin like uio_out[7] should render the driver path without flattening any internal modules.
Modules involved in the trace path (e.g., tt_um_essen, m_jtag_tap, m_2x2_systolic_mac) are displayed as nested bounding boxes.
The 'Hierarchical Element Trace' table successfully lists the full nested path for all elements in the trace, including intermediate hierarchy.
The user can drill down into a nested module block to view its internal trace without losing context of the parent.
Implementation Reference image
Environment Details (Preserved from original report)
- Hardware: Laptop 16 (AMD Ryzen AI 300 Series)
- OS: Ubuntu 25.10 (Questing Quokka)
- Browser: Google Chrome 154.0.8037.57
Description
Currently, when performing a "Trace to Driver" operation (e.g., from the 'Netlist Hierarchy' panel or a canvas element), the viewer flattens the resulting driver logic and intermediate stages. The hierarchical nesting of modules and sub-modules is lost, making it difficult to understand the design's context and logic flow within complex, multi-level designs.
This feature requests that the schematic canvas and relevant trace tables maintain the full design hierarchy when displaying the trace results. It will be useful for the user to see bounding boxes representing parent modules nested around their children and leaf primitives, and the netlist paths should reflect this hierarchy.
For example, tracing from a terminal pin like uio_out[7] should render the driver path without flattening any internal modules.
Modules involved in the trace path (e.g., tt_um_essen, m_jtag_tap, m_2x2_systolic_mac) are displayed as nested bounding boxes.
The 'Hierarchical Element Trace' table successfully lists the full nested path for all elements in the trace, including intermediate hierarchy.
The user can drill down into a nested module block to view its internal trace without losing context of the parent.
Implementation Reference image
Environment Details (Preserved from original report)