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
The way the wrapper scripts are, it's not possible to call the scripts without setting an environment variable as the Toplevel name that ends generating the output binary and header.
The ideal way would be able to pass it as an argument and use the env var as a fallback in case no argument is present. This way it's much easy to integrate the pipeline with tools like FuseSoc and Edalize.
carlosedp
changed the title
Not possible to call the wrapper by passing the file name
Not possible to call wrapper scripts by passing the file name
Sep 21, 2021
The way the wrapper scripts are, it's not possible to call the scripts without setting an environment variable as the Toplevel name that ends generating the output binary and header.
The ideal way would be able to pass it as an argument and use the env var as a fallback in case no argument is present. This way it's much easy to integrate the pipeline with tools like FuseSoc and Edalize.
The scripts are mainly:
https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/quicklogic-upstream-rebase/quicklogic/common/toolchain_wrappers/symbiflow_write_binary
https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/quicklogic-upstream-rebase/quicklogic/common/toolchain_wrappers/symbiflow_write_bitheader
The text was updated successfully, but these errors were encountered: