Simulink Real-Time fail to boot up on target machine due to "Spurious Interrupt"

Hi,

Our research lab has been developing control algorithms for a quadrupedal robot in Simulink Real-Time on a Intel i7 SBC (single-board computer) serving as target machine. It has been a great experience and provided good real-time performance.

Thrilled to see that Matlab 2017b included support for the Intel i210 driver, I tried to replace the current SBC with a newer one which had an Intel Atom E3845 processor and two Intel i210 Ethernet controllers. But when it booted up, I was greeted with an error message saying "Spurious Interrupt............." (see the figure below), then the computer just went completely frozen.

The tech guys from the manufacturer indicated that the cause might be "the Interrupt Service Routine (ISR) in one of the drivers doesn’t clear the interrupt status register properly after servicing the interrupt (or no ISR for one of the devices in the system), and that causes spurious interrupt keeps coming back."

Could you please provide a hint on why this happens and if possible, how to fix it? Please let me know if further info is needed.

Thanks!

Chad

[Robbin van Hoek]

Did you manage to solve the error? We are currently encountering a similar problem.

[Chuanzheng Li]

Hi,

Might be a bit late for you, but upgrading to Matlab 2018a solved my problem...