Electrical – Problem with the reset circuit for a MCU

Not having used either of those devices in particular I'll leave this as a bit of a list of some generic reasons I can think of why using a seperate supervisor can still be useful:

• You may want a trip voltage that is different to those offered by the microcontroller. For example that STM32 has a 2.8V odd minimum threshold, maybe you have other logic that stops operating below 3V for example and need a reset to reinitalize it.

• Some microcontrollers have power-on reset and brown out detection logic that doesn't work well with very slow rise and fall times. Not sure about the STM32 in particular but that's a common reason for using one.

• While it sounds like it's not used in this application the watchdog output could be used to physically power cycle the system and/or trigger an external alarm. This may be important to protect against some sort of latch-up condition (although that would normally be a design problem).

• Some of these functions could be useful while the CPU is asleep, for example the watchdog might be used to signal that an bus no longer has activity and force the CPU to wake up rather than reset.

Whether it's worthwhile really depends on the overall design. For example a solar-powered datalogger in a remote location might have to deal with very slow rise and fall times and it might be vital that the system recovers from any situation reliably. A counter-example is a consumer USB product where it's likely to be a waste of time because the first thing most people will do is try to unplug it and plug back in.

Your layout is entirely lacking in decoupling capacitors. The MCU won't run with that layout and the clock probably won't even oscillate.