https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266840
--- Comment #3 from Tomoyuki Sakurai <trombik1...@gmail.com> --- (In reply to Hans Petter Selasky from comment #2) i understand what is going on (i think). the board is a development board. https://github.com/WeActStudio/WeActStudio.CH552CoreBoard when a button is pressed and the dev board is plugged into a machine, the bootloader, which accepts firmware, runs. Oct 6 04:23:18 t480s kernel: ugen0.6: <vendor 0x4348 product 0x55e0> at usbus0 after 10 sec, it runs the user application (probably, an example firmware). the Oct 6 04:23:27 t480s kernel: ugen0.6: <vendor 0x4348 product 0x55e0> at usbus0 (disconnected) Oct 6 04:23:27 t480s kernel: ugen0.6: <Deqing CH55xduino> at usbus0 Oct 6 04:23:27 t480s kernel: umodem0 on uhub0 Oct 6 04:23:27 t480s kernel: umodem0: <CDC Serial> on usbus0 Oct 6 04:23:27 t480s kernel: umodem0: data interface 0, has no CM over data, has no break Oct 6 04:23:27 t480s kernel: umodem0: Can't setup transfer Oct 6 04:23:27 t480s kernel: device_attach: umodem0 attach returned 6 my understanding is that, if vendor and product ID are defined and added to umodem_host_devs in umodem.c, it should work when the bootloader is running. am I correct? -- You are receiving this mail because: You are the assignee for the bug.
