m-kru
m-kru
Based on Fusesoc + Vivado experience, but it is probably the same for other back ends. Names of generated project files follows this pattern: {CORE_NAME}_{VERSION}.extension. When working with multiple targets...
In my humble opinion it would be nice, if fusesoc could provide `fmt` command to format single `.core` file or all `.core` files under working directory if path to a...
To bring in the core with generator one needs to artificially add fileset like this: ```yaml filesets: agwb_dep: depend: - wzab::addr_gen_wb generate: smx_tester: generator: addr_gen_wb parameters: infile: ../top_3_feb_c.xml targets: default:...
Related to https://github.com/olofk/fusesoc/issues/471
I am not sure if it applies to all tools, but for Vivado FuseSoc does not use any parallelism capabilities (Vivado `-jobs` parameter). I wanted to improve this, so I...
This behavior results from 2 facts: 1. When sources are exported, they are copied to the `src/` directory which is located in the `build/core/` directory, not in the `build/core/target/` directory....
Almost always when I set `toplevel` within the target it has the same name as the target itself. Example: ```yaml tb_start_after_reset: default_tool: ghdl toplevel: tb_start_after_reset filesets: - rtl - tb_start_after_reset...
I want to describe some quite big HDL library as FuseSoc library. As I do not expect the maintainers of the library to accept my pull request adding `.core` files,...
`fusesoc fetch core` can fetch files for remote core. However, if this core has other remote cores in its dependencies, it would be nice to have an option to automatically...
If user removes `my_lib` directory from `.local/share/fusesoc`, but leaves entry for that library in `fusesoc.conf`, and then runs `fusesoc update` , `my_lib` is not fetched (is not downloaded to the...