Benedek wish: on-demand c2usb state dump.

[kareltucek]

Story: Trying to get full streaming c2usb logs of issues is complicated. Partly because we pull those logs over usb, which means that with too low logging level, any usb log causes more usb logs, resulting in a flood which may or may not interfere with UHK operation. However, we often get into situation where we have a partly-operational that is sufficiently operational to run a macro or a zephyr command on-demand

Wish: I would like to have a function that I can call, which prints c2usb state, including any relevant debug information.

@benedekkupper what do you think? Would it be useful to hunt those recent usb stack issues?

[benedekkupper]

I'd first proceed with the SDK update, it could be that some of the current bugs get resolved with that. If you have the chance it would be great if you could try to help me out in #1524 with the new BLE connection issues.

[kareltucek]

Will try to. Do you have any pointers as to what exactly I should dig into?

[benedekkupper]

As you reported, the BLE HID pairing fails with different hosts. In general you should get the BLE side working between all links, and check regressions in other zephyr subsystems (so general test of all functionality). I asked copilot whether the migration guides were hiding any hints on why these new problems show up, but it didn't give useful info.