DRA78XEVM: NMI interrupt cannot be triggered

Hao Chen

Part Number: DRA78XEVM

Hello,

We are trying to use NMI interrupt for DRA78x.

NMI is enabled via register "CTRL_CORE_NMI_DESTINATION_1" already.

If we try to trigger NMI via NMI pin (connect it to GND), NMI ISR can NOT be triggered.

If we trigger NMI manually via register "ICSR" (bit "NMIPENDSET"), NMI ISR can be triggered.

Is there any other setting we need to do?

Thanks in advance.

0 kcastille over 3 years ago

Hello,

Can you provide the 32-b value of the the register CTRL_CORE_PAD_NMIN? Namely want to make sure that bits 15:0 set to 0x0 and bit 18 also set to 0?

Thanks,

Kyle

0 Hao Chen over 3 years ago in reply to kcastille

Hi Kyle,

Thanks a lot for supporting.

For "bit 15:0" and "bit 18", they are RESERVED.

May I know the reason to check these bits?

On the other hand, we have tried 0 for "NMIN_PULLTYPESELECT" and 0 for "NMIN_PULLUDENABLE", seems not working as well.

Note: We have 10K pull-up at NMI input.

0 Stanley Liu over 2 years ago in reply to Hao Chen

Hi,

Could you try the followings?

A test might be done at the DSP to see if NMI can be triggered by external signal. This would give some info if the issue is at the M4 boundary or before it.
A test to write a 0xFF (not just 1) in the IPU_Cx fields to see if the behavior changes.
A BSDL read of the pad state could happen during their pull down attempt to see if the value is making it in

Regards,
Stanley

0 Hao Chen over 2 years ago in reply to Stanley Liu

Hello Stanley,

Thanks for helping.

Regarding to point 3:

- BSDL (Boundary Scan Description Language) read: do you mean to use JTAG tool (e.g., Lauterbach, XDS) to read?

- CTRL_CORE_PAD_NMIN cannot be configured as GPIO, which register shall we read?

Thanks.

+1 Stanley Liu over 2 years ago in reply to Hao Chen

According to customer offline update, setting BIT7 to 1 in IPU_Cx field fixed the problem.

0 Hao Chen over 2 years ago in reply to Stanley Liu

Thanks Stanley for supporting us.

Processors forum