Alex Martens

This was the intent - to maintain compatability between the stm32wle5x and stm32wl5x. I think compatibility within the the series is more important than compatibility with other STM micros. Is...

https://github.com/rust-embedded/svd2rust/issues/16 That seems to be the latest on aliases. Not very promising. As an alternative we could strip the "c1" from the dual core stm32wl5x and have it be implicit....

> I think it's turned two cases into three unless we renamed IMR for all compatible MCUs: > > * case 1: Single core > * case 2: Single core,...

I am not sure about the other ones, I don't know those series as well.

Looks like the underscore got stripped from the patched file for some reason, which is odd because it didn't get stripped for the multi-core WL's Edit: Found it. https://github.com/stm32-rs/stm32-rs/blob/eddd89e6d16808a827dfbbc61c349835f277d9d1/svd/extract.sh#L15 One...

> 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...

Does the branch `issue/29` fix this? I am on a new PC without integrated bluetooth, cannot test this myself until I get a dongle.

The last person said: > I thought Bleak would ask BlueZ over DBus whether the connection exists already but I am okay to do it myself. Would you know how...

Huh, it appears the python socket interface will also just work. All that looks pretty spartan though, and I don't know as much about host-side BLE as I would like...

What `monitorcontrol` version? Can you re-run with debug logging on, like this? ```py import logging import monitorcontrol logging.basicConfig(level=logging.DEBUG) for monitor in monitorcontrol.get_monitors(): with monitor: print(monitor.get_input_source()) ``` This it what it...