Hey Wenli,
I've tried calling you quite a few times with no success, so I've just sent you an email with as much information as I could put together without discussing a few details with you first.
It might be useful to update the rest of the users though anyway:
Essentially, I don't believe there is actually an issue with using many interrupts, I believe it's how much information you are trying to pass with those interrupts. Your code currently raises an interrupt every time there is any information on the ports! This is simply too much for the controller to handle. The FPGA code has loops running at high speeds and sending up too many interrupt requests basically. One of your loops does have some code in another loop to only raise an interrupt when an EOS is found, and this is a lot better than what your other loops are doing. You should work towards this kind of functionality with the other loops as well, however you should remember you have a limited number of DMA FIFOs.
Also, your AI and AO do not need interrupts, you can eliminate those. Have a look at examples for AI/AO on FPGA.
Your code probably sends a lot of requests and inundates your controller, so it needs to be a bit smarter and only raise an interrupt when there is a complete message (for example).
I hope this helps a little,
Kind Regards,
Michael S.
Applications Engineer
NI UK & Ireland
