Armandas Jarušauskas

It looks like the issue is caused by using bracket comments. I have updated the description.

Have you considered adopting [semantic versioning](https://semver.org/) (i.e. increment the major version number when making API breaking changes)?

@h2zero I couldn't find any references to `esp_nimble_hci_and_controller_init` in the code. Though I'm happy to make any additional changes, as required.

@h2zero Sorry about the delay. I finally had some time to check this. Indeed, with the original initialization code, I was getting a `E (2391) BLE_INIT: controller init failed` error...

Sure. I am using the `espflash` command, as described [here](https://github.com/esp-rs/esp-idf-template?tab=readme-ov-file#flash). My project is using `std`, but how does that affect the flashing tool? `--no-stub` didn't help, but it did work...

Also just want to add that I haven't explicitly configured the partitions, but V2 tool had no problem with it, so from usability perspective, the new tool should not break...

This belongs to [avrlibc](https://github.com/avrdudes/avr-libc).

I had the same problem. Not sure if that's the best way to solve this, but what I did is implement my own `ReadWithTimeout` trait, based on the `Read` trait...

I went on and tested the `atmega2560-usart_spi-feedback` example. I tested USART1, USART2 and USART3 and they all work. USART0 is connected to USB, so I did not test that. My...

@Rahix I was wondering if it would make sense to re-export configuration structs and enums defined in `spi` from `usart_spi`?