Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block diagram includes pinmux and other updates #355

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

marnovandermaas
Copy link
Contributor

For example SRAM is 128 KiB, there's no DMA, there's no CHERIoT Debug module, etc.

Re-do of this PR: #264 addressing the comments of @HU90m.

Copy link
Member

@HU90m HU90m left a comment

Choose a reason for hiding this comment

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

Nits:

  1. The USB device connects to a different USB port. Connecting it to the same hub may cause confusion.
  2. The debug module is connected to the crossbar. My suggestion was to reroute it's connection so it isn't going under the USB.

For example SRAM is 128 KiB, there's no DMA, there's no CHERIoT Debug
module, there is a user USB etc.
@marnovandermaas
Copy link
Contributor Author

1. The USB device connects to a different USB port. Connecting it to the same hub may cause confusion.

I've added a user USB now which should hopefully help this.

2. The debug module is connected to the crossbar. My suggestion was to reroute it's connection so it isn't going under the USB.

I actually decided to remove the debug module because it's not really user visible.

@marnovandermaas marnovandermaas merged commit 564ba01 into lowRISC:main Nov 22, 2024
3 checks passed
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.

3 participants