Memory map comparison

Although I specified a stm32u575 and a stm32u585 feature in makecrates.py, the generated crate only has a stm32u5 features.

makecrates.py:

CRATE_DOC_FEATURES = {
    # ...
    "stm32u5": ["rt", "stm32u575", "stm32u585"],
}

stm32u5/Cargo.toml

[features]
default = ["rt"]
rt = ["cortex-m-rt/device"]
stm32u5 = []

Is this correct / okay? Or should I change something about it?
cc @adamgreig

Memory map comparison

I got it to generate the two device features stm32u575 and stm32u585 by duplicating the YAML patch file. I am not sure if this is correct, but hopefully someone knowledgeable can take a look. As far as I can see the PR is ready for review now 😄

I am still unsure how I can test if the generated PAC actually works. I do have the board at home. Is there some basic example I can run to test this PR?

I am still unsure how I can test if the generated PAC actually works. I do have the board at home. Is there some basic example I can run to test this PR?

Typically I do make form -j 32 then try to compile the PAC in a binary, using stm32u5.path = "/home/me/stm32-rs/stm32u5" in Cargo.toml.

For a basic example try enabling the GPIO clock in RCC, setting a GPIO as an output, then blinking it.

Memory map comparison

Memory map comparison

Please, don't break history. Rebase. No merge in PR.

@burrbull said:

Please, don't break history. Rebase. No merge in PR.

Okay. I just used the "resolve conflict" button from GitHub.

Hello together,
what is the status of this? @Urhengulas can you rebase your branch?
Kind regards!

Memory map comparison

Hello together, what is the status of this? @Urhengulas can you rebase your branch? Kind regards!

Just did

Build succeeded:

• CI