Closed carlosedp closed 1 year ago
This seems to be a bug in SBY which slipped through the automated tests after some recent refactoring. The SBY commit 9a14f4d238 is the latest one before that refactoring and should still work.
Thanks @jix ... got an image from the beginning of august and it worked!
On some image (during august too) I got the error:
SBY 14:07:17 [insn_auipc_ch0] prep: ERROR: No such command: formalff (type 'help' for a command overview)
~Want me to open an issue over SBY there referencing this one?~
That No such command: formalff
error means that the used Yosys version is too old for the used SBY version. In general SBY requires an up to date Yosys version.
Ah ok.. so it's probably a mismatch midways in the container image .
The one I'm using(gcr.io/hdl-containers/formal@sha256:ff660de17fb8847f01fb33c1b4bd8bf08eebfd9e3fdaa9dd844a71f7c54b42a7
) works fine and I'll wait for this fix to bump it.
I'm trying to add riscv-formal to my core and while running it, I'm getting:
My config is:
This also happens to existing cores like vexriscv or picorv32.
I'm running yosys and sby from
gcr.io/hdl-containers/formal
container which uses:Latest SBY from https://github.com/YosysHQ/sby.