Closed jerabaul29 closed 11 months ago
Does the fact that it is named here:
mean that it is supported? :)
STM32U5[78] are tested working on actual hardware. I later added STM32U5[9A] based on ST's XMLs but I haven't checked anything beyond "it compiles" (I haven't been able to get my hands on a U5[9A] board yet). They seem to be very similar just with added peripherals, so if we're lucky it'll Just Work. If we're not lucky it might require some small fixes :)
I will try to look a bit into this in the days to come, and to report my experience (I am a n00b on these toolchains, so learning on the way) at: https://github.com/jerabaul29/embassy_experiments .
For now it seems like the main issue is that probe-rs is not supporting this chip family yet, will see what probe-rs answers :) : https://github.com/probe-rs/probe-rs/issues/1792 .
@gauteh FYI :) .
since my last comment embassy-stm32 has been tested working on nucleo-u5a5zj by both another person and me, it's up and running fine. There might still be missing bits of course, but the basics are there.
I know that "older" stm32u5 processors are supported (I have a NUCLEO-U575ZI-Q https://www.st.com/en/evaluation-tools/nucleo-u575zi-q.html using the STM32U575ZIT6Q and I am able to run embassy programs on it just fine so far). Do you know if some of the "brand new" stm32u5 processors, such as the STM32U5A5ZJ used in the NUCLEO-U5A5ZJ-Q https://www.st.com/en/evaluation-tools/nucleo-u5a5zj-q.html (released Q2 2023) are supported too? I will buy one of these, I can also test / report how things go when I get it :) .