diff options
| author | Sean Anderson <seanga2@gmail.com> | 2022-10-30 19:21:41 -0400 |
|---|---|---|
| committer | gatecat <gatecat@ds0.me> | 2022-12-07 10:32:38 +0100 |
| commit | df99b4ff6c5ce88ce1a731dc8682ab1875b8c237 (patch) | |
| tree | 7a716a63e581e71f0a9b2711a906a1faee2f6c46 /generic/viaduct/example/example.cc | |
| parent | 603b60da8dcadf23eec8609ffc128f8f191c1122 (diff) | |
| download | nextpnr-df99b4ff6c5ce88ce1a731dc8682ab1875b8c237.tar.gz nextpnr-df99b4ff6c5ce88ce1a731dc8682ab1875b8c237.tar.bz2 nextpnr-df99b4ff6c5ce88ce1a731dc8682ab1875b8c237.zip | |
ice40: Add debugs to isBelLocationValid for SB_IO
When there is a constraint conflict while placing IOs, the user gets an
error message such as
ERROR: Bel 'X0/Y27/io1' of type 'SB_IO' is not valid for cell 'my_pin' of type 'SB_IO'
While this identifies the problematic cell, it does not explain why
there is a problem. Add some verbose messages to allow users to
determine where the problem is. This can result in something like
Info: Net '$PACKER_VCC_NET' for cell 'my_pin' conflicts with net 'ce' for 'ce_pin'
which provides something actionable.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
Diffstat (limited to 'generic/viaduct/example/example.cc')
0 files changed, 0 insertions, 0 deletions