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

fusesoc initialization error #416

Open
SaiRitish opened this issue Feb 1, 2023 · 1 comment
Open

fusesoc initialization error #416

SaiRitish opened this issue Feb 1, 2023 · 1 comment

Comments

@SaiRitish
Copy link

SaiRitish commented Feb 1, 2023

Hello ^^

So, I am trying to run microwatt on Arty a7. (final goal)

But I am not able to run "fusesoc init" for some reason

It says:
usage: fusesoc [-h] [--version] [--cores-root CORES_ROOT] [--config CONFIG] [--monochrome] [--verbose] [--log-file LOG_FILE] {fetch,core,tool,list-cores,core-info,gen,list-paths,library,run} ...
fusesoc: error: argument {fetch,core,tool,list-cores,core-info,gen,list-paths,library,run}: invalid choice: 'init' (choose from 'fetch', 'core', 'tool', 'list-cores', 'core-info', 'gen', 'list-paths', 'library', 'run')

And I was like: How can the command not exist, because it is documented at many places TwT

Could be a silly mistake that I have made, or something to do with the new fusesoc version? I'm not sure, but any help is appreciated. :)

@gromero
Copy link
Contributor

gromero commented Aug 9, 2024

@SaiRitish Hi.

init subcommand for fusesoc was removed since fusesoc 2.0. Now 'library add' is sufficient. So if you want to build microwatt, instead of this sequence:

$ source /opt/Xilinx/Vivado/2019.1/settings64.sh
$ pip3 install --user -U fusesoc
$ fusesoc init
$ fusesoc fetch uart16550
$ fusesoc library add microwatt /path/to/microwatt

Use this one:

$ source ~/Xilinx/Vivado/2024.1/settings64.sh
$ pip3 install --user -U fusesoc
$ fusesoc library add microwatt /home/gromero/git/microwatt/
$ fusesoc fetch uart16550

I tested it on Ubuntu 22.04 with Vivado 2024.1 webpack.

I'll send a patch updating the README.md, but feel free to test and submit the patch yourself.

Cheers.

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

No branches or pull requests

2 participants