Replies: 1 comment 1 reply
-
Uhh, I'm not very familiar with the json output but AFAIK it is often used with nextpnr so if it was wrong it would be obvious pretty quickly. Taking a look at your example and comparing the RTLIL with the json we get
The |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to generate a circuit from a verilog file using the following yosys script
topEntity.txt
(The topEntity.v file was generated by Clash, it implements the shift rows step of an AES encryption.)
I am trying to create a circuit file using the to_blif or to_json command but it seems like some errors are introduced there. When simulating the out.blif or out.json files they give the wrong results.
I also tried write_verilog out.v and simulated out.v using iverilog and the result is correct, so it seems like the synth command is not introducing any issues.
Since I am simulating the blif and json circuits with my own code there could be an error in the interpretation of the formats on my side but looking at the out files themselves I can already see mistakes. For example here is an excerpt from the json output:
The first 8 bits of the first input are not supposed to move, therefore
"result_0": {
"direction": "output",
"bits": [ 98, 99, 100, 101, 102, 103, 104, 105, ...
is wrong it should be
"result_0": {
"direction": "output",
"bits": [ 2, 3, 4, 5, 6, 7, 8, 9, ...
Beta Was this translation helpful? Give feedback.
All reactions