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
When crashing, print the count of execution steps. Together with a cli flag like --steps=$count, this could easily be used to triage bugs
The current way of handling the address map (memory::default_hifive()) does not feel "Rust 🦀". It would be nice if the whole memory access logic could be expressed as a single match addr statement (or similar).
Current work tries to have the "address bus" as a trait that must be implemented by a given board.
A student pitched the idea of a "heat map for memory access". That sounds cool.
The way mmapped periphery needs a thread to function is not ideal. Either make threading a feature (after all, periphery is async by nature) or find an other solution. Chrysn mentioned interior mutability as an option.
Works well with threads and the peekable channel
Printing of the registers names / instruction names is very long and a bit ugly code. Are there better solutions?
--steps=$count, this could easily be used to triage bugsmemory::default_hifive()) does not feel "Rust 🦀". It would be nice if the whole memory access logic could be expressed as a singlematch addrstatement (or similar).