Date: Wed, 17 Apr 2019 22:26:01 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: "freebsd-arm@freebsd.org" <arm@freebsd.org> Subject: Re: i2c almost working for me, was Re: i2c still not working for me Message-ID: <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> In-Reply-To: <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il> References: <12F641C3-9FAA-4A3A-BA18-A7302F3A0F5E@cs.huji.ac.il> <20190409095819.c560dbc156c46e5ca0244e3e@bidouilliste.com> <23A47048-642A-481C-B7BE-B61E55F82955@cs.huji.ac.il> <20190409171604.GA4581@bluezbox.com> <FCA4E00E-455A-46BF-AD78-E20E1E997BFC@cs.huji.ac.il> <6119CE3B-6042-4DDC-82BE-B0C0C7ADA838@cs.huji.ac.il> <5D4799BC-08DF-4F3D-81A4-C2D938F4AF93@cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Apr 2019 09:16:02 +0300 Daniel Braniss <danny@cs.huji.ac.il> wrote: >=20 >=20 > > On 11 Apr 2019, at 09:56, Daniel Braniss <danny@cs.huji.ac.il> wrote: > >=20 > > if no device is connected, I2CRDWR hangs,=20 > > it also happens with i2c(8) -s, only reboot helps. > >=20 > > ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed param=3D2a > > iichb1: TWSI_WRITE: Writing 0 to 18 > > iichb1: TWSI_WRITE: Writing 2a to 14 > > iichb1: TWSI_WRITE: Writing 40 to c > > iichb1: TWSI_WRITE: Writing c4 to c > > iichb1: twsi_transfer: transmitting 2 messages > > iichb1: TWSI_READ: read f8 from 10 > > iichb1: twsi_transfer: status=3Df8 > > iichb1: twsi_transfer: msg[0] flags: 0 > > iichb1: twsi_transfer: msg[0] len: 9 > > iichb1: TWSI_WRITE: Writing e4 to c > >=20 > > and now it?s hung > [?] I don't see that on my OrangePi One or Pine64-LTS. >=20 > even with a working device, this happens sometimes: >=20 > my app gets ENXIO from the ioctl(fd, I2CRDWR, &data) and on the console: > ? > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 38 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 > gic0: Spurious interrupt detected: last irq: 29 on CPU2 >=20 > the good news: my app is killable :-) I would need more details for this. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190417222601.c037efe0cb48987c81032bac>