You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2023. It is now read-only.
- See #36
On branch scarv/skywater/dev
Your branch is up-to-date with 'origin/scarv/skywater/dev'.
Changes to be committed:
modified: .travis.yml
new file: scarv-cpu.core
Changes not staged for commit:
modified: external/embench-iot (modified content, untracked content)
modified: external/riscv-formal (untracked content)
- See #36
On branch scarv/skywater/dev
Your branch is up-to-date with 'origin/scarv/skywater/dev'.
Changes to be committed:
modified: .travis.yml
Changes not staged for commit:
modified: external/embench-iot (modified content, untracked content)
modified: external/riscv-formal (untracked content)
This didn't go well. I need to do some more reading about how to use FuseSoC properly and the relevant use cases. At the moment for the scarv-soc, git submodules might just be the easiest way to go.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FlowIssue with the flow scripts/environment.skywaterAssociated with project skywater.
Add FuseSoC support.
The text was updated successfully, but these errors were encountered: