UARTs do not appear on startup if probe is connected

[rgrr]

"lsusb" etc knows about it, but the udev rules does not seem to be executed on startup so the CDC-ACMs do not appear.

Replugging is required to get in dmesg

[    5.488267] usb 1-8: New USB device found, idVendor=2e8a, idProduct=000c, bcdDevice= 1.23
[    5.488270] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.488272] usb 1-8: Product: YAPicoprobe CMSIS-DAP
[    5.488273] usb 1-8: Manufacturer: RaspberryPi
[    5.488275] usb 1-8: SerialNumber: E6614C775B1D4D35

... no udev activity here

[  130.183400] usb 1-8: USB disconnect, device number 2
[  133.076729] usb 1-8: new full-speed USB device number 4 using xhci_hcd
[  133.469047] usb 1-8: New USB device found, idVendor=2e8a, idProduct=000c, bcdDevice= 1.23
[  133.469055] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  133.469058] usb 1-8: Product: YAPicoprobe CMSIS-DAP
[  133.469061] usb 1-8: Manufacturer: RaspberryPi
[  133.469063] usb 1-8: SerialNumber: E6614C775B1D4D35
[  133.526289] hid-generic 0003:2E8A:000C.0006: hiddev3,hidraw5: USB HID v1.11 Device [RaspberryPi YAPicoprobe CMSIS-DAP] on usb-0000:02:00.0-8/input1
[  133.548118] cdc_acm 1-8:1.2: ttyACM0: USB ACM device
[  133.551122] cdc_acm 1-8:1.6: ttyACM1: USB ACM device
[  133.551160] usbcore: registered new interface driver cdc_acm
[  133.551162] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  133.597050] cdc_ncm 1-8:1.4: MAC-Address: fe:77:5b:1d:4d:35
[  133.597215] cdc_ncm 1-8:1.4 eth0: register 'cdc_ncm' at usb-0000:02:00.0-8, CDC NCM (NO ZLP), fe:77:5b:1d:4d:35
[  133.597263] usbcore: registered new interface driver cdc_ncm
[  133.600028] usbcore: registered new interface driver cdc_wdm
[  133.601717] usbcore: registered new interface driver cdc_mbim
[  133.606563] cdc_ncm 1-8:1.4 enxfe775b1d4d35: renamed from eth0

First cdc_acm activity in 133.5...

After sleep, the same effect applies:

[  843.546119] usb 1-8: USB disconnect, device number 5
[  845.788620] usb 1-8: new full-speed USB device number 6 using xhci_hcd
[  846.181088] usb 1-8: New USB device found, idVendor=2e8a, idProduct=000c, bcdDevice= 1.23
[  846.181097] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  846.181101] usb 1-8: Product: YAPicoprobe CMSIS-DAP
[  846.181104] usb 1-8: Manufacturer: RaspberryPi
[  846.181107] usb 1-8: SerialNumber: E6614C775B1D4D35
[  846.243413] hid-generic 0003:2E8A:000C.0007: hiddev3,hidraw5: USB HID v1.11 Device [RaspberryPi YAPicoprobe CMSIS-DAP] on usb-0000:02:00.0-8/input1
[  846.249172] cdc_acm 1-8:1.2: ttyACM0: USB ACM device
[  846.301051] cdc_ncm 1-8:1.4: MAC-Address: fe:77:5b:1d:4d:35
[  846.301299] cdc_ncm 1-8:1.4 eth0: register 'cdc_ncm' at usb-0000:02:00.0-8, CDC NCM (NO ZLP), fe:77:5b:1d:4d:35
[  846.306926] cdc_acm 1-8:1.6: ttyACM1: USB ACM device
[  846.317479] cdc_ncm 1-8:1.4 enxfe775b1d4d35: renamed from eth0

[rgrr]

the /dev/ttyACM* also do not appear

[rgrr]

it seems that updating TinyUSB to 0.18.0 in pico-sdk solves this