Colin Schmidt
Colin Schmidt
Option 1 seems bad because of all the potential options and the tying of the general infrastructure to a specific simulator. I think option 2 seems very reasonable to me....
Actually even with a command like this ``` /simv-freechips.rocketchip.system-DefaultConfig +verbose +max-cycles=1000000 output/rv64ui-p-add ``` I still get this failure message at the end of the output: ``` terminate called after throwing...
I've made a strawman permissive PR on fesvr here https://github.com/riscv/riscv-fesvr/pull/41
Does anyone have an opinion on my proposal?
I think a good solution (at least to help migration) would just be another chisel 3 compatibility warning/error when you do this. Any bulk connects to a bundle after any...
Also explaining what to do when `+init_write` isn't enough.
This behavior really shouldn't depend on `CONFIG` (aside from not including JTAG would cause it to not accept this option). So, to confirm, you can pass the exact same arguments...
You two seem to be reporting conflicting information: in one case `SmallNVDLARocketConfig` does work with jtag and in the other it doesn't. There was a modification of the argument parsing...
Ok. I've confirmed this issue, thanks for the help narrowing it down. As a quick workaround, wrapping that flag in `+permissive` and `+permissive-off` works for me. ``` ./simulator-chipyard-TinyRocketConfig +permissive +jtag_rbb_enable=1...
Thanks @jackkoenig I'll test with that branch and this firrtl branch