Yeah, even a small part such as the cc1310 from Texas Instruments (a sub-GHz wireless SOC for <10USD MOQ-1) is a triple-core device. One Cortex-M3 as the main core, a Cortex-something as the radio core, and a Sensor Controller (I'm guessing msp430-derived) as a low-power helper core. For the latter, you actually compile a binary blob that you push to it in firmware, and the format is not ARM.

Quite complex stuff.

Vendor tools for STM provide almost exactly what you wish for for the clock diagram.

Example: http://www.emcu.it/STM32clk/STM32clk.html

I haven't used the STM Cube configurator for a while, but last time I did it was almost at FPGA software levels of user-unfriendlieness. If you changed the indentation on a magic comment in your code and then adjusted one of the clocks, CUBE would clobber your existing code and silently delete it.

Yes, Cube autogenerates a lot of code and will overwrite things that don’t follow the inserted markers.

The original article even includes an example of using Cube to configure the clocks and then use those configurations together with Rust.

I agree that it isn’t ideal at all and kinda wonky. But more links in the datasheets would be nice.