From owner-freebsd-arm@freebsd.org Wed Aug 3 20:52:45 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AA18BAE105 for ; Wed, 3 Aug 2016 20:52:45 +0000 (UTC) (envelope-from bmcgover@cisco.com) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (Client CN "rcdn-iport.cisco.com", Issuer "HydrantID SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 630A81D71 for ; Wed, 3 Aug 2016 20:52:45 +0000 (UTC) (envelope-from bmcgover@cisco.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1280; q=dns/txt; s=iport; t=1470257565; x=1471467165; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=B9pGBDdEH9Rtrm2R5eiyPp7NmpeKpcZwSvvOnbY5J6g=; b=RR/5FTs3yGy4YTztizBB7VBit9/xPy92gFaBsVj93mV6m5o6ae0+nADc vyW3evyHnIJwfkOZrRrgukG/L2TicJrRtQ7XUH7KwuGT7Dy+hyhW0h4VT 8HJ4Bh2aQIa+1ftXTohsgasmQg58rqfaSTd+auA0QxCHS64+EEZ+eu35v 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AgC1WKJX/4oNJK1dg0WBWbkqgX2Hb?= =?us-ascii?q?DgUAQEBAQEBAV0cC4RlOlEBPkInBBuIKZ9tn2IBAQEHAQEBAQEihiqOaAWOF4s?= =?us-ascii?q?dAY53j0eQJgEeNoN6iEl/AQEB?= X-IronPort-AV: E=Sophos;i="5.28,467,1464652800"; d="scan'208";a="136610358" Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Aug 2016 20:52:43 +0000 Received: from XCH-RTP-002.cisco.com (xch-rtp-002.cisco.com [64.101.220.142]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u73KqhjP027688 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 3 Aug 2016 20:52:43 GMT Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-002.cisco.com (64.101.220.142) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 3 Aug 2016 16:52:43 -0400 Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1210.000; Wed, 3 Aug 2016 16:52:43 -0400 From: "Brian McGovern (bmcgover)" To: "freebsd-arm@freebsd.org" Subject: Beaglebone Black ADC with 11-BETAs? Thread-Topic: Beaglebone Black ADC with 11-BETAs? Thread-Index: AQHR7cj6ivaCCqu7Z02Zdd8OVreSBw== Date: Wed, 3 Aug 2016 20:52:42 +0000 Message-ID: <91547185801847a4951c4456d9d1dfb2@XCH-RTP-005.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.131.65.20] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2016 20:52:45 -0000 Its been 6+ months since I've worked with a BBB and the analog inputs. "Bac= k in the day", I used the interface as described by ti_adc(4) man page. How= ever, the last couple of days, I've built up an image using the code that i= s on the 11.0 release path. The problem I'm seeing is that the ADC controll= er appear to be disabled in this builds... root@beaglebone:~ # dmesg | grep adc ti_adc0: mem 0x44e0d000-0x44e0dfff disabled on simplebu= s0 ti_adc0: scheme: 0x1 func: 0x730 rtl: 0 rev: 0.1 custom rev: 0 ... and the sysctl interface seems to be similarly truncated.... root@beaglebone:~ # sysctl -a | grep adc dev.ti_adc.0.clockdiv: 2400 dev.ti_adc.0.%parent: simplebus0 dev.ti_adc.0.%pnpinfo: name=3Dtscadc@44e0d000 compat=3Dti,am3359-tscadc dev.ti_adc.0.%location:=20 dev.ti_adc.0.%driver: ti_adc dev.ti_adc.0.%desc: TI ADC controller dev.ti_adc.%parent:=20 I noticed in the /boot/msdos/bboneblk.dts file that tscadc@44e0d000 had a s= tatus =3D "disabled". I changed it to "okay" per other nodes, recompiled it= to bboneblk.dtb via dtc, rebooted, and still no joy. Is the boot process using these files, or is the device tree built in to th= e kernel (meaning I have to make fixes elsewhere and re-run the build)?=