BOR vs PVD Detection Logic

[SPati.7]

1. We have seen PVD triggers when there is transient load of 1A added on the 3.3Vdc (loaded additional to our design through electronic load) and it triggers when the transient load dips the 3.3V for duration of ~450 micro seconds.
2. We have seen BOR triggers when there is transient load of 1A added on the 3.3Vdc (loaded additional to our design through electronic load) and it triggers when the transient load dips the 3.3V for duration of ~196 micro seconds.

Why there is difference in detection logic? What is lowest pulse or transient dip the voltage detection logic will detect?

Is there any filtering in the PVD detection circuit internal to MCU? Is it same with BOR detection circuit?

1. We see PVD programming has some amount of filtering for any transient glitches and its detection circuit behaves bit differently than BOR detection circuit, Why there is a difference?
2. Is it BOR reset triggers, when the VDD has some glitch or the BOR detection circuit will look for some stabilized time to which the VDD threshold will be monitored to trigger a reset?

What is the timing, or a transient response to which BOR & PVD will be immune to..?

@Fred​ and @Jocelyn RICARD​ Can you please forward this query to the Expert in this Voltage Monitoring ??

@Community member​  Can you able to help here ??

I tried going through manuals, but still not clear on difference of the above two behavior ??

[Tesla DeLorean]

Not really my area of interest

At some point you run out of electrons. Perhaps ensure the entire supply doesn't collapse faster than you can detect it and react to it.

Perhaps work with the local FAE responsible for your account, to understand the nuances of the implementation. Perhaps post as an Online Support Request

PVD would likely want different criterion so you can react in time.

The reset mechanisms want to ensure the synchronous logic doesn't get into indeterminate states, as this is a form of attack, beyond ensuring correct operation.

STM32H7 ?

[SPati.7]

Thanks for quick reply @Community member​ .

Its STM32F765NIH6 MCU.