Timothy Normand Miller wrote: > > Here's another option that I like to use: > > The reset into the CPU is not the global reset but rather a bit in a > config register. The global reset causes this reset to be asserted > (by initializing the register to zero), and the CPU doesn't wake until > we change that bit. This way, we can start and stop it at will. > Moreover, the synthesizer will treat the registered reset as any other > async reset, so we don't use any extra logic for it. Of course, with > this approach, there is no "pause". Stopping it kills the state and > causes it to completely restart.
Since we are planning on using the CPU to help control a number of activities on the board, we need to make sure that at no point will we need the CPU to assist in performing an activity related to it's reset or program upload. Patrick M _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
