Test Node.isTiedToVcc()

[eddieh-xlnx]

[github-actions[bot]]

Unit Test Results

  43 files    43 suites   6m 1s :stopwatch: 575 tests 566 :heavy_check_mark: 8 :zzz: 1 :x: 588 runs  579 :heavy_check_mark: 8 :zzz: 1 :x:

For more details on these failures, see this check.

Results for commit 4aec8514.

:recycle: This comment has been updated with latest results.

[clavin-xlnx]

Although I can recognize the confusion, it looks like RapidWright is faithfully reporting what Vivado is reporting regarding VCC connectivity:

Vivado% link_design -part xcvu440-flga2892-2-e
#...
Vivado% report_property [get_nodes LAGUNA_TILE_X161Y659/VCC_WIRE]
Property           Type    Read-only  Visible  Value
#...
IS_BAD             bool    true       true     0
IS_COMPLETE        bool    true       true     1
IS_GND             bool    true       true     0
IS_INPUT_PIN       bool    true       true     0
IS_OUTPUT_PIN      bool    true       true     0
IS_PIN             bool    true       true     0
IS_VCC             bool    true       true     0
#... 
Vivado% report_property [get_nodes LAGUNA_TILE_X161Y659/VCC_WIRE0]
Property           Type    Read-only  Visible  Value
#...
IS_BAD             bool    true       true     0
IS_COMPLETE        bool    true       true     1
IS_GND             bool    true       true     0
IS_INPUT_PIN       bool    true       true     0
IS_OUTPUT_PIN      bool    true       true     0
IS_PIN             bool    true       true     0
IS_VCC             bool    true       true     1
#...

Should we close this PR or deviate from Vivado?

[clavin-xlnx]

Interestingly, the PIP Junction IS_VCC is set to 1, but strangely the node is not:

[eddieh-xlnx]

Ah, that's frustrating. I suppose RapidWright should only be reporting what Vivado gives up rather than embellishing its own meanings. Looks like I can't rely on this property then!