Update for new pac

[usbalbin]

No description provided.

[astapleton]

Hey @usbalbin. I think we've got some duplicated work here. I've got some unpublished branches that update the stm32-rs dependency and bring in changes to support the rest of the H5 family (notably adding all the peripheral clock enable definitions and add the rest of the GPIOs). Those changes do depend on an updated version of the stm32h5 crate. However, the upstream stm32-rs crate is changing quite rapidly at the moment, so targeting the nightly might be quite disruptive to PRs.

@burrbull you previously published a stm32h5-staging crate, but I see you've since un-published/yanked/deleted it. I was wondering whether you have an idea when new stm32-rs pac crates will be published, or whether you could re-publish the stm32h5-staging crate from master?

[astapleton]

One of the branches I was working on, for reference: https://github.com/stm32-rs/stm32h5xx-hal/tree/as/peripheral-rec-all-h5

[burrbull]

i did not yank anything. it is still on crates.io

[burrbull]

i can release a new staging version as most of update/refactoring work is done

[usbalbin]

One of the branches I was working on, for reference: https://github.com/stm32-rs/stm32h5xx-hal/tree/as/peripheral-rec-all-h5

I am happy to try rebasing over that if it would be helpful.

[usbalbin]

i can release a new staging version as most of update/refactoring work is done

In that case, I can update this(or a rebased version of this) to depend on that :)

[burrbull]

https://crates.io/crates/stm32h5-staging/0.17.0

[astapleton]

i did not yank anything. it is still on crates.io

Huh. I must have used the wrong name earlier. Thanks for updating it!

[astapleton]

i can release a new staging version as most of update/refactoring work is done

In that case, I can update this(or a rebased version of this) to depend on that :)

Yeah, how about you update this to depend on the staging crate and then I can rebase the RCC reset/enable changes on top?

[usbalbin]

i can release a new staging version as most of update/refactoring work is done

In that case, I can update this(or a rebased version of this) to depend on that :)

Yeah, how about you update this to depend on the staging crate and then I can rebase the RCC reset/enable changes on top?

Done

[astapleton]

Looks good! Thanks!