SRAM parity flag not set in NMI handler

[awalti]

Hi all

I'm trying to distinguish between the interrupt sources in the NMI handler on a STM32G031 - particularly the RAM parity error.

I have everything in place and I can provoke a parity error. The NMI ISR is called as expected, but if the SYSCFG_CFGR2_SPF is checked in the ISR it is never set (and neither are the other 3 potential NMI sources).

Am I not understanding correctly how this works? Is this flag getting automatically reset upon entry into the ISR (The manual is not totally clear here. For the other flags it explicitly mentions that they need to be cleared manually)?

Thanks for any pointers

A

[Billy OWEN]

Hi @awalti​ 

The forum moderator had marked your post as needing a little more investigation and direct support. An online support case has been created on your behalf, please stand by for just a moment and you will hear from us.

Regards,

Billy

[waclawek.jan · Accepted solution]

Do you have SYSCFG clock set in RCC (by setting RCC_APBENR2.SYSCFGEN)?

JW

[awalti]

Well, that seems to have done the trick. Thank you!

This information seems to be quite well hidden in the Ref Manual.

[awalti]

Thanks also to ST support which came up with the same solution but I can't seem to add a comment there.