Skip to content

[hw,dv] Rationalise I/O pads of top_chip_asic#51

Merged
elliotb-lowrisc merged 1 commit intolowRISC:mainfrom
elliotb-lowrisc:pads
Mar 4, 2025
Merged

[hw,dv] Rationalise I/O pads of top_chip_asic#51
elliotb-lowrisc merged 1 commit intolowRISC:mainfrom
elliotb-lowrisc:pads

Conversation

@elliotb-lowrisc
Copy link
Contributor

The input and output signals for some bidirectional interfaces seem to initially have been connected to different I/O pads in top_chip_asic for some unknown reason.
Also one pad had different interfaces connected to the input vs. output.

Correct this and reduce the number of pads to match.

The input and output signals for some bidirectional interfaces
seem to initially have been connected to different I/O pads in
`top_chip_asic` for some unknown reason.
Also one pad had different interfaces connected to the input vs. output.

Correct this and reduce the number of pads to match.
Copy link
Contributor

@marnovandermaas marnovandermaas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks reasonable to me from a code review. Once you're happy with testing this, feel free to merge.

@elliotb-lowrisc elliotb-lowrisc merged commit 97f5872 into lowRISC:main Mar 4, 2025
1 check passed
@elliotb-lowrisc elliotb-lowrisc deleted the pads branch March 4, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants