From owner-freebsd-arm@FreeBSD.ORG Thu May 1 15:38:47 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C08BF677; Thu, 1 May 2014 15:38:47 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 373741905; Thu, 1 May 2014 15:38:47 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id f8so929792wiw.3 for ; Thu, 01 May 2014 08:38:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wjF+bTqpJe4Gtlh7wv0aldvQ20uKOfnmxgposdMcKOk=; b=YQLqcf6pRXVYBuEgzG0rhyUeZXq8EXUKJAFBt8eMBPGAo2dut9dEeYR2Y90h2p/PxP Coe4ay/gBCwaUWd2H/CJjLDVd8fDTH+/4ggwA3U/9JXauke5ZLf+mhuuHnWW94BFJHCj 1YZxTlTNC2U4DlLXu6L21/RHFRMaZnBzrYD6+eKnS8TWOxZXtnY92renRDld995OBoc1 BWoJWFu535Jl2T57GcrdL8OAQLXsfnaW7CkHP1hBfPqg2WtG3t32lvsdyaXes3dyAGwy H+Orj71wn3CgnY9asHgqO8SYfsMbIY4jnNmliZ7dvYZrUMOo+SV9ttVGfxVTzbuXYNi5 HFww== MIME-Version: 1.0 X-Received: by 10.180.100.129 with SMTP id ey1mr2688223wib.60.1398958725499; Thu, 01 May 2014 08:38:45 -0700 (PDT) Received: by 10.217.10.195 with HTTP; Thu, 1 May 2014 08:38:45 -0700 (PDT) In-Reply-To: References: <93181B67-1944-4DDD-A595-455D2AE9B110@grondar.org> <1CFC3564-65F0-4DC8-950C-3D53BBB2761C@FreeBSD.org> Date: Thu, 1 May 2014 11:38:45 -0400 Message-ID: Subject: Re: i2c on RPI-B not working From: Winston Smith To: Rui Paulo Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm , Mark R V Murray X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2014 15:38:47 -0000 On Wed, Apr 30, 2014 at 7:49 PM, Winston Smith wrote: > 1) Hopefully, you'll have more luck with the i2cscan.c tool I wrote than I did! > 2) Does anyone know why I'm not detecting any i2c devices on the BBB? I fixed the i2cscan.c tool and it's able to detect the various i2c devices (including the EEPROM at 0x50) on the BBB's I2C0 bus: root@beaglebone:~ # ./i2cscan /dev/iic0 Checking device: /dev/iic0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- 24 -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- I have updated the pastebin for this: http://pastebin.com/RxpRCyJU