Pausing the Nios II

Create an sopc custom component ip that is an avalon slave.

The nios cpu just does an dummy access to this slave but this ip module rises waitrequest so the nios cpu will "sleep" or be stalled.

All you need is to gain access to the interupts so each irq will be recognized and the waitrequest will go to the ready state and nios will continue.

or you need some other kind of signals that tells when to continue, even if it is just a timer that could also be part of that ip.

This is very tricky with the irq's and has some pitfalls but it works and reduces the dynamic power consumption