From owner-freebsd-arm@freebsd.org Tue Apr 27 12:11:06 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D4A0B5E6CF4 for ; Tue, 27 Apr 2021 12:11:06 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FV0wV3Qr3z3tlg; Tue, 27 Apr 2021 12:11:06 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from amy (j1a01-1-78-205-69-41.fbx.proxad.net [78.205.69.41]) by mx.blih.net (OpenSMTPD) with ESMTPSA id b8cba790 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 27 Apr 2021 12:11:03 +0000 (UTC) Date: Tue, 27 Apr 2021 14:11:03 +0200 From: Emmanuel Vadot To: Mark Murray Cc: freebsd-arm Subject: Re: I2C/IIC working on RPI4 8GB? Message-Id: <20210427141103.1c4d2e4d81e04ff7417761d2@bidouilliste.com> In-Reply-To: References: <1C2DD11C-B1F6-4C2A-9AB0-5F1553520FF5@FreeBSD.org> <20210426161138.a8f44b6e1134f73a411be57d@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FV0wV3Qr3z3tlg X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2021 12:11:06 -0000 On Tue, 27 Apr 2021 08:52:39 +0100 Mark Murray wrote: > On 26 Apr 2021, at 15:11, Emmanuel Vadot wrote: > > > > On Sun, 25 Apr 2021 13:32:00 +0100 > > Mark Murray wrote: > > > >> Hi All, > >> > >> Does anyone here have IIC/I2C working on a CURRENT (I'm running latest) FreeBSD? > >> > >> I've never seen it work; Last time I had working IIC was on an RPI3. > >> > >> There is a /dev/iic0, and I have a known working RTC on it, but the scan just times out: > >> > >> [root@grasshopper ~]# i2c -s > >> Hardware may not support START/STOP scanning; trying less-reliable read method. > >> > >> Scanning I2C devices on /dev/iic0: > >> > >> > >> I suspect something not-quite-right in DTS land, but I lack the knowledge to investigate. I've done some random stumbling around in the dark with overlays and the like, but I've either seen the above error, or a total lack of /dev/iic0. > >> > >> Thanks! > >> > >> M > >> -- > >> Mark R V Murray > >> > > > > I2C is disabled by default. > > You need to copy i2c0.dtbo (or i2c1 I don't know which one maps to > > the pins you want to use) in the ESP partition and add "i2c" to the > > dtoverlay line in config.txt > > I want to use the i2c on the "regular" pins, GPIO2 and GPIO3, AKA physical pins 3 and 5. > > I looked at all the i2c[0-6].dtbo overlays in /usr/ports/sysutils/rpi-firmware. Only 1 had "pins = <2, 3>", so I used that one. I presume the 2,3 refers to GPIO pin numbers, not physical pin numbers? > > Same result as before - long timeout, no I2C. > > M > -- > Mark R V Murray > No they probably refer to the pin number of the SoC (but that might be the same as the "gpio number" in the pinouts naming of the hat connector. I don't have any rpi* here to help you more so hopefully someone else can/will. -- Emmanuel Vadot