Identify the source of the interrupt(NMI)?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Identify the source of the interrupt(NMI)?

ソリューションへジャンプ
1,980件の閲覧回数
vaibhav_sharma
Contributor III

Microcontroller: MPC5777C

Interrupt sources-

1. [EXTERNAL] SBC is triggering interrupt on the NMI line of controller handled by IVOR1.

2. [INTERNAL] FCCU NMI test raises a NMI request handled by IVOR1 too.

Both are being routed to core0. The status bit is the same, i.e., SIU_EISR.B.NMI0 & NMI bit in the MCSR register, for both the cases. So, is there any other status bit by which I can identify the exact cause of that NMI interrupt.

Same is the case for machine check exception handled by IVOR1-> 

1. SRAM single bit error generates it.

2. Illegal memory access by any of the bus master can generate it.

For this, the single status bit MCP is available in the MCSR register. 

ラベル(1)
0 件の賞賛
返信
1 解決策
1,842件の閲覧回数
davidtosenovjan
NXP TechSupport
NXP TechSupport

a) The only way how to distinguish is to examine all sources you have configured to possibly generate NMI (i.e. in this case FCCU registers), and if it is not FCCU fault, then you may suppose it is external NMI line.
Better option is to configure external NMI line to invoke IVOR0 (pay attention to SIU_DIRER register).

b) Single bit ECC error does not cause machine check. It must be multi-bit ECC error. For that there several flags in MCSR register (IF/LD/ST/BUS_IRERR/DRERR/WRERR)

元の投稿で解決策を見る

0 件の賞賛
返信
1 返信
1,843件の閲覧回数
davidtosenovjan
NXP TechSupport
NXP TechSupport

a) The only way how to distinguish is to examine all sources you have configured to possibly generate NMI (i.e. in this case FCCU registers), and if it is not FCCU fault, then you may suppose it is external NMI line.
Better option is to configure external NMI line to invoke IVOR0 (pay attention to SIU_DIRER register).

b) Single bit ECC error does not cause machine check. It must be multi-bit ECC error. For that there several flags in MCSR register (IF/LD/ST/BUS_IRERR/DRERR/WRERR)

0 件の賞賛
返信