Honored Contributor
Honored ContributorHi Jan,
SIGALRM is not the right solution when you have strict timing requirements. This is true not just on Nios II. <div class='quotetop'>QUOTE </div> --- Quote Start --- From the kernel description I made my issue, that there is no chance to get exact timing only in kernel user space. There is also problem with modifying kernel, because I can not just write my own timer driver, due to the fact, that my process must be always handled by kernel process manager which works with default (big) jiffy step.[/b] --- Quote End --- I still don't understand why you cannot take advantage of the second Nios timer in the core. In fact, I think this is the best solution for you. <div class='quotetop'>QUOTE </div> --- Quote Start --- The only way I see is the jiffy redesign to be much more smaller (< 1ms), but I am not experienced to do this..[/b] --- Quote End --- you can just change the HZ value in head file include/nios2-nommu/param.h. One jiffy will be 1ms if HZ is 1000. This might make the generation of the signal more accurate, but this will not make the delivery of it faster. Besides, your system will have an interrupt overhead...
