> Regarding or1ksim, though, In my opinion what would be the best > solution to all of this is keeping track of the register accesses > after "power up" on the simulator and printing out a big error message > if accesses to any register which should be initialised (basically > just the GPRs) are accessed without. This would mean wrapping them in > some accessor function and checking against a "read_before_written" > bit once after or1ksim bringup. > > That's a really good idea, given it doesn't slow down or1ksim execution too much, but I guess some clever C folks can solve that.
-- Olof Kindgren ______________________________________________ ORSoC Website: www.orsoc.se Email: [email protected] ______________________________________________ FPGA, ASIC, DSP - embedded SoC design
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
