chisel2-deprecated
chisel2-deprecated copied to clipboard
I implemented and tested out both varieties of overriding bulk connects, letting `:=` override `` and letting `` override ``, and I think a good case can be made for...
A while ago, I added a check that elaborates the declared fields of a class and examines whether methods share names with fields to determine whether they are `val` accessors...
A common issue with users is that Mem their designs are not being properly inferred to have the right ports. (For example, not merging related R and W ports into...
Looks like the Tester expects that every node peek'd / poke'd needs to have a corresponding name in the emulator. Naturally, sliced bits of a multibit wire wouldn't actually "exist"...
Sometimes, we want to use the operators in the when statements like: io thisIo when(thatCond) { io thatIo } However, the current Chisel doesn't support it, emitting reassignment errors. I...
Previously, failure to specify the default for a wire (when using whens and similar) would give an error message indicate, at the very least, the name of the offending wire....
An arbiter has many producers trying to talk to a consumer. A work distributor has one (or more?) producers trying to talk to multiple consumers.
``` scala package Rs232 import Chisel._ class Transmitter extends Module { val io = new Bundle { val serOut = UInt(OUTPUT, 1) val outData = Decoupled(UInt(width = 8)).flip val counterInit...
It seems somewhat weird to have two nearly identical ways of starting Chisel. Related to issue #309, it leads to divergent behaviors.
It seems improper (or, at least, not properly documented) that the configuration object is only constructed when ChiselMain.run is used and not ChiselMain.apply. The reason in code for this is...