logisim-evolution/logisim-evolution

Synthesis of Duplicate Imports

Closed

#1,663 opened on Feb 8, 2023

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Java (505 forks)batch import
bughelp wantedpri std

Repository metrics

Stars
 (3,695 stars)
PR merge metrics
 (Avg merge 3d 18h) (47 merged PRs in 30d)

Description

I have a design where I have imported 2 projects that use common custom circuits. The design simulates and executes ok. When I synthesize the design, I get '"XXXXXX". This is not allowed, please make sure all sheets have a unique name'. The board is set to use Vivado (if that matters). Question - is this by design? If so, it limits the utility of reusable components...is there a workaround?

This seems like a limitation that could be avoided if the DRC looked to see if the circuits are identical (and/or imported) and only generated the one definition.

Contributor guide

Research direction
Investigate the DRC (Design Rule Check) logic that produces the duplicate sheet name error during synthesis. Trace the code path that checks for duplicate imports and consider adding a comparison of circuit contents to allow identical circuits.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65