Dario Nieuwenhuis

First step is to add the registers to [stm32-data](https://github.com/embassy-rs/stm32-data). See the ADC peripherals for C0 [have no `registers` field](https://github.com/embassy-rs/stm32-data-generated/blob/main/data/chips/STM32C031K6.json#L42) (compare it [with G0](https://github.com/embassy-rs/stm32-data-generated/blob/main/data/chips/STM32G031K8.json#L219) which does). follow the steps in the...

This is sort of intended. The CDC ACM class we have now is "low level", it reads/writes USB packets from the endpoint. Reading an USB packet with a too small...

You really can't rely on the packet length. For example a write of 72 bytes from the host will be fragmented as two packets of 64 bytes and 8 bytes....

IMO the low-level CDC ACM is working as intended. See the warnings in the [docs](https://docs.embassy.dev/embassy-usb/git/default/class/cdc_acm/struct.CdcAcmClass.html): "read_packet must be called with a buffer large enough to hold max_packet_size bytes.". If we...

The meat for sending/receiving HCI packets over SPI is here https://github.com/raspberrypi/pico-sdk/tree/master/src/rp2_common/pico_cyw43_driver/cybt_shared_bus The issue is that will get us only "send/receive HCI packets to the bluetooth controller". We then need a...

I saw your PR, pretty excited to see progress on this! :star_struck: > and I need the clm loaded first are you sure that's needed? Intuitively I'd say the wifi...

they aren't, the datasheet has some details, plus the fact that there's two firmwares.

the datasheet literally says there's 2 cores. I think the bluetooth core starts on its own. In a more standard setup (ie not Pico's weird bluetooth-over-SPI) you talk to it...

See #2865 for latest status. Help is needed to finish it, contributors welcome!

done in https://github.com/embassy-rs/embassy/pull/2865 It uses the [TrouBLE](https://github.com/embassy-rs/trouble) bluetooth stack.