Hello, I have disabled uftdi, that way the ftdi device is attach using the
ugen driver.Openocd works now. But because there is no tty emulation (ucom is
not used), I can't use "cu" anymore. Some people have previously tried to make
every usb device attached using both ugen and the more specific
mcmer-open...@tor.at (Marcus MERIGHI), 2017.09.25 (Mon) 15:32 (CEST):
> robert.d...@yahoo.fr (Robert Dazi), 2017.09.24 (Sun) 22:28 (CEST):
> > Hi,I have a software (openocd) that needs to serially communicate
> > with a board, but it can't because libusb throws
> > LIBUSB_ERROR_NOT_SUPPORTED.
>
> You might try to tell the kernel *not* to attach the device to ucom(4).
It will attach like uftdi or other * found in ucom man page.
Dmesg is really needed!
robert.d...@yahoo.fr (Robert Dazi), 2017.09.24 (Sun) 22:28 (CEST):
> Hi,I have a software (openocd) that needs to serially communicate
> with a board, but it can't because libusb throws
> LIBUSB_ERROR_NOT_SUPPORTED.
> To access a usb device using libusb, libusb provides a function
> returning a
> But my device is bound to cuaU1, and not to any ugen.
You didn't provide a dmesg. It may be that you are using an USB to
serial adapter to connect to this board.
See 'man ucom' and maybe you can send here a dmesg.
Hi,I have a software (openocd) that needs to serially communicate with a
board, but it can't because libusb throws LIBUSB_ERROR_NOT_SUPPORTED.
To access a usb device using libusb, libusb provides a function returning a
list of devices. But this function fills a field of the device structure onl
6 matches
Mail list logo
