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
It would be nice if the etherbone+litex functionality in wishbone tool was extracted into a library (crate?) that other tools could build on the top of.
Functionality which makes sense to me;
Reading & Writing to wishbone busses
Reading & Writing to LiteX CSR registers, including loading the CSR names and info from .csv or .json files.
Setting up triggers, watching the triggering and reading the data from LiteScope.
The text was updated successfully, but these errors were encountered:
The basic wishbone peek/poke functionality should be pulled out into its own crate. This will also require separating configuration data out -- right now config is one big giant struct that individual bridges refer to.
We now have a new crate called wishbone-bridge that is documented on docs.rs. This supports the first point.
Is there a specification for how a .json file looks? Right now the csr.csv parsing is mostly hand-rolled in https://docs.rs/wishbone-bridge/1.0.0/wishbone_bridge/ and I think it could be improved. Support for json could be added at the same time.
For LiteScope support, I'd need to know what triggers look like.
It would be nice if the etherbone+litex functionality in wishbone tool was extracted into a library (crate?) that other tools could build on the top of.
Functionality which makes sense to me;
.csv
or.json
files.The text was updated successfully, but these errors were encountered: