Generated a HSI based configuration with cube and we're getting somewhere. The app still hangs somewhere but it's past the rng init now.
ooooh wait a minute lol, I probably need to supply memory.x…
anyway, thanks! This seems to work for init, I'll take the rest of my issues to the embassy room:

    let mut config = Config::default();
    {
        use embassy_stm32::rcc::*;
        config.rcc.pll_src = PllSource::HSI;
        config.rcc.pll = Some(Pll {
            prediv: PllPreDiv::DIV8,
            mul: PllMul::MUL96,
            divp: Some(PllPDiv::DIV2),
            divq: Some(PllQDiv::DIV4),
            divr: None,
        });
        config.rcc.ahb_pre = AHBPrescaler::DIV2;
        config.rcc.apb1_pre = APBPrescaler::DIV2;
        config.rcc.apb2_pre = APBPrescaler::DIV1;
        config.rcc.sys = Sysclk::PLL1_P;
        config.rcc.mux.clk48sel = mux::Clk48sel::PLL1_Q;
    }
    let p = embassy_stm32::init(config);

    let mut rng = Rng::new(p.RNG, Irqs);
    let mut seed = [0; 8];
    let _ = rng.async_fill_bytes(&mut seed).await;
    info!("rng initialized");

In reply to @dngrs:matrix.org
you mean my previous code, just change Bypass to Oscillator?

In reply to @burrbull:matrix.org
Just import SpiCommon trait and mark it as impl Into<SPI1:Sck>. See https://github.com/stm32-rs/stm32f4xx-hal/blob/403fddbdab864699143ae54becd124beeda69569/src/spi.rs#L464

In reply to @jo_we:matrix.org
if i have a SPI::Nss pin, and i select the SPI device to let software handle the Nss pin (via CR1 register on stm32f407, bit SSM), is it possible to manually set the pin SPI::Nss high and low? I cant seem to find a working into()-Call that keeps my abstraction, and not require me to set the type to a specific pin?

In reply to @jo_we:matrix.org
hm but if i take a Pin<Output<PushPull>>>, i cannot verify that i get a pin specifically designed to be an NSS pin (according to the datasheet). thats what i want to achieve. I want a pin via function parameter from which i know that its intended usage is as SPI::Nss, which I'll have to set high or low manually

In reply to @jo_we:matrix.org
hm but if i take a Pin<Output<PushPull>>>, i cannot verify that i get a pin specifically designed to be an NSS pin (according to the datasheet). thats what i want to achieve. I want a pin via function parameter from which i know that its intended usage is as SPI::Nss, which I'll have to set high or low manually

yes, for sure, I know that i can use any output pin for datasheet, however the hal defines via SPI::Nss spezializations which pins the datasheet assigns as Nss intended use. for example for spi3 (Implementation of SpiCommon)

        <Nss, PushPull> for [
            PA4<6>,

            PA15<6>,
        ],

id like my function parameter to be limited to these pins all while switching them manually internally

yes, for sure, I know that i can use any output pin for NSS, however the hal defines via SPI::Nss spezializations which pins the datasheet assigns as Nss intended use. for example for spi3 (Implementation of SpiCommon)

        <Nss, PushPull> for [
            PA4<6>,

            PA15<6>,
        ],

id like my function parameter to be limited to these pins all while switching them manually internally

yes, for sure, I know that i can use any output pin for NSS, however the hal defines via SPI::Nss spezializations which pins the datasheet assigns as Nss intended use. for example for spi3 (Implementation of SpiCommon) under src/gpio/alt/f4.rs

        <Nss, PushPull> for [
            PA4<6>,

            PA15<6>,
        ],

id like my function parameter to be limited to these pins all while switching them manually internally

yes, for sure, I know that i can use any output pin for NSS, however the hal defines via SPI::Nss spezializations which pins the datasheet assigns as Nss intended use. for example for spi3 (Implementation of SpiCommon) under src/gpio/alt/f4.rs

        <Nss, PushPull> for [
            PA4<6>,

            PA15<6>,
        ],

id like my function parameter to be limited to these pins all while switching them manually internally

In reply to @jo_we:matrix.org
is anything like that possible?