Honored Contributor
Honored ContributorHi dsl,
Thanks for your reply. --- Quote Start --- I don't have any external devices that are time-critical enough to require the cost of taking an interrupt. The code's idle loop checks the device registers directly (instead of looking at state set by an ISR). --- Quote End --- Could you show me an example of checking the device register during the idle loop? I think if we want to check the register, we have to keep checking it except we apply an interrupt to sign if there is any changes in the register's content. Hmm...currently I have some problems with my design : 1. Somehow the SignalTap couldn't detect the trigger that I've set (I set the interrupt signal as the trigger). The interrupt signal's clock was 150 MHz, and I set 300 MHz as the sampling frequency for the SignalTap. Few days my SignalTap still could catch the trigger, now I don't know why it became like this. I'm sure that I didn't do any critical hardware modification related with SignalTap function. When I checked the SignalTap instantaneously it showed that there was IRQ signal change, so in actual the trigger really occured but the SignalTap couldn't catch it. :confused: 2. The IRQ keeps coming, even I try to clear it. It seems that the IRQ signal only clear within 1 clock, then it keeps active. About the possibility of interrupt redundancy (when the first interrupt isn't completely cleared, the second interrupt occur), I have tried to prevent it by setting large number of data that have to be processed before the interrupt occur. Any other idea about this? To find what causes this interrupt problem becomes more difficult, because the SignalTap can't detect the IRQ signal..:( Please anyone....help me to figure out how to solve this interrupt problem ... :( Thanks
