Date: Wed, 24 Apr 2019 13:02:11 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: Ian Lepore <ian@freebsd.org>, "freebsd-arm@freebsd.org" <arm@freebsd.org> Subject: Re: i2c almost working for me, was Re: i2c still not working for me Message-ID: <20190424130211.7a575f57150882eb3dfabc76@bidouilliste.com> In-Reply-To: <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@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> <20190417222601.c037efe0cb48987c81032bac@bidouilliste.com> <DDDAC739-D68F-4843-BF89-3044ED442F69@cs.huji.ac.il> <64b5598e2c8c7265f89a31b1f191cb1be318788a.camel@freebsd.org> <CD499934-6E4E-4416-9B73-F3B8AB9A916D@cs.huji.ac.il> <20190419100502.5546770a5795c20e3f4fa9db@bidouilliste.com> <0FDE4A01-D79E-4AFE-BA4C-3F39C4360AF8@cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Apr 2019 11:35:09 +0300
Daniel Braniss <danny@cs.huji.ac.il> wrote:
>
>
> > On 19 Apr 2019, at 11:05, Emmanuel Vadot <manu@bidouilliste.com> wrote:
> >
> > On Fri, 19 Apr 2019 10:20:47 +0300
> > Daniel Braniss <danny@cs.huji.ac.il <mailto:danny@cs.huji.ac.il>> wrote:
> >
> >>
> >>
> >>> On 18 Apr 2019, at 17:19, Ian Lepore <ian@freebsd.org> wrote:
> >>>
> >>> On Thu, 2019-04-18 at 10:12 +0300, Daniel Braniss wrote:
> >>>>> On 17 Apr 2019, at 23:26, Emmanuel Vadot <manu@bidouilliste.com>
> >>>>> wrote:
> >>>>>
> >>>>> On Tue, 16 Apr 2019 09:16:02 +0300
> >>>>> Daniel Braniss <danny@cs.huji.ac.il <mailto:danny@cs.huji.ac.il>>
> >>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On 11 Apr 2019, at 09:56, Daniel Braniss <danny@cs.huji.ac.il>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>> if no device is connected, I2CRDWR hangs,
> >>>>>>> it also happens with i2c(8) -s, only reboot helps.
> >>>>>>>
> >>>>>>> ichb1: twsi_reset: Using IIC_FASTEST/UNKNOWN mode with speed
> >>>>>>> param=2a
> >>>>>>> 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=f8
> >>>>>>> iichb1: twsi_transfer: msg[0] flags: 0
> >>>>>>> iichb1: twsi_transfer: msg[0] len: 9
> >>>>>>> iichb1: TWSI_WRITE: Writing e4 to c
> >>>>>>>
> >>>>>>> and now it?s hung
> >>>>>>
> >>>>>> [?]
> >>>>>
> >>>>> I don't see that on my OrangePi One or Pine64-LTS.
> >>>>
> >>>> well, mine is are Nanopi Neo, maybe it?s a dts issue?
> >>>> I also have a orangepi-zero but it will take me some time to make
> >>>> a sdcard
> >>
> >> I managed to boot my OrangePi Zero, and i2c -s has no issues, does not hang.
> >> still, with the latest (r346368) my NanoPi Neo hangs when no i2c device is present,
> >> so what is the difference? or where can I look?
> >
> > Are you using the same i2c controller on both ?
> yes, and have tested with several controllers and nanopies,
>
> > Could you paste somewhere the overlays or dts patches ?
> cat ./allwinner/dts/12/h3-i2c.dtso
> /dts-v1/;
> /plugin/;
>
> //#include "sun8i-h3-nanopi-neo.dts"
>
> / {
> compatible = "allwinner,sun8i-h3";
> };
>
> &i2c0 {
> ##frequency = <50000>;
> status = "okay";
> };
>
> &i2c1 {
> ##frequency = <50000>;
> status = "okay";
> };
>
>
And you have hang on both i2c0 and i2c1 ?
Also please note that i2c1 pins aren't routed on this PCB, I don't
think that this could/should make the i2c controller hangs but ...
--
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?20190424130211.7a575f57150882eb3dfabc76>