Date: Thu, 28 Apr 2022 00:47:06 +0200 From: Axel Rau <Axel.Rau@chaos1.de> To: hardware@freebsd.org Subject: [RESOLVED] Re: Accessing I2C-Bus via ELV USB-I2C Message-ID: <0d980857-704a-6edd-07c3-aa31548ee03c@Chaos1.DE> In-Reply-To: <996df5c0-ffa7-f1bf-a9e2-6dd47d7b49e6@Chaos1.DE> References: <996df5c0-ffa7-f1bf-a9e2-6dd47d7b49e6@Chaos1.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
The application daemon speaks twi over the serial line (/dev/cuaU0) Everything works perfectly. Thanks, Axel Am 27.04.22 um 23:08 schrieb Axel Rau: > Next journey starts: >=20 > For the home2l project, I need a supported I2C interface via USB. > I got this one: > https://de.elv.com/elv-usb-ic-interface-usb-i2c-092255?fs=3D1805459039 > Unfortunately it shows up as a serial device on FreeBSD: >=20 > ugen0.2: <Silicon Labs ELV USB-I2C-Interface> at usbus0, cfg=3D0 = md=3DHOST=20 > spd=3DFULL (12Mbps) pwr=3DON (500mA) >=20 > =C2=A0 bLength =3D 0x0012 > =C2=A0 bDescriptorType =3D 0x0001 > =C2=A0 bcdUSB =3D 0x0110 > =C2=A0 bDeviceClass =3D 0x0000=C2=A0 <Probed by interface class> > =C2=A0 bDeviceSubClass =3D 0x0000 > =C2=A0 bDeviceProtocol =3D 0x0000 > =C2=A0 bMaxPacketSize0 =3D 0x0040 > =C2=A0 idVendor =3D 0x10c4 > =C2=A0 idProduct =3D 0xea60 > =C2=A0 bcdDevice =3D 0x0100 > =C2=A0 iManufacturer =3D 0x0001=C2=A0 <Silicon Labs> > =C2=A0 iProduct =3D 0x0002=C2=A0 <ELV USB-I2C-Interface> > =C2=A0 iSerialNumber =3D 0x0003=C2=A0 <B5AAP0EEUK6A3CIZ> > =C2=A0 bNumConfigurations =3D 0x0001 >=20 > In loader.conf, I have: > uslcom_load=3D"YES" > iic_load=3D"YES" > iicbus_loa >=20 > But the i2c utility does not show a new bus. >=20 > From dmesg: > root@axels-bsdbox:~ # dmesg | grep iic > ig4iic0: <Intel Sunrise Point-H I2C Controller-0> mem=20 > 0xdf230000-0xdf230fff irq 16 at device 21.0 on pci0 > ig4iic0: Using MSI > iicbus0: <Philips I2C bus (ACPI-hinted)> on ig4iic0 > iic0: <I2C generic I/O> on iicbus0 > ig4iic1: <Intel Sunrise Point-H I2C Controller-1> mem=20 > 0xdf22f000-0xdf22ffff irq 17 at device 21.1 on pci0 > ig4iic1: Using MSI > iicbus1: <Philips I2C bus (ACPI-hinted)> on ig4iic1 > iic1: <I2C generic I/O> on iicbus1 > root@axels-bsdbox:~ # dmesg | grep I2C > ig4iic0: <Intel Sunrise Point-H I2C Controller-0> mem=20 > 0xdf230000-0xdf230fff irq 16 at device 21.0 on pci0 > iicbus0: <Philips I2C bus (ACPI-hinted)> on ig4iic0 > iic0: <I2C generic I/O> on iicbus0 > ig4iic1: <Intel Sunrise Point-H I2C Controller-1> mem=20 > 0xdf22f000-0xdf22ffff irq 17 at device 21.1 on pci0 > iicbus1: <Philips I2C bus (ACPI-hinted)> on ig4iic1 > iic1: <I2C generic I/O> on iicbus1 > ugen0.2: <Silicon Labs ELV USB-I2C-Interface> at usbus0 > uslcom0: <ELV USB-I2C-Interface> on usbus0 >=20 > They provide a (linux) driver ("Treiber") which seems to implement the=20 > I2C protocoll on top of the serial interface. > Do we have such a driver on FreeBSD, or exist other supported I2C=20 > devices to be plugged into USB? >=20 > Any help appreciated, > Axel =2D-=20 PGP-Key: CDE74120 =E2=98=80 computing @ chaos claudius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0d980857-704a-6edd-07c3-aa31548ee03c>