From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Beaglebone Black Ethernet Failures
To: meta-ti@lists.yoctoproject.org
From: "Dave Tucker" <theaethereal@gmail.com>
X-Originating-Location: Washington, US (154.3.44.17)
X-Originating-Platform: Linux Firefox 86
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Wed, 10 Mar 2021 05:27:22 -0800
Message-ID: <u0TL.1615382842912667990.O2ud@lists.yoctoproject.org>
Content-Type: multipart/alternative; boundary="sYL5DjBOmP45TVSr6MFU"

--sYL5DjBOmP45TVSr6MFU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I have been using a Beaglebone Black for a project for years.=C2=A0 I recen=
tly upgraded from Dunfell to Gatesgarth and again began experiencing a prob=
lem with the ethernet interface failing to come online 10% of the time, a p=
roblem which can only be fixed by a power cycle (not a reboot).=C2=A0 This =
is a well known problem documented by this thread ( https://groups.google.c=
om/g/beagleboard/c/9mctrG26Mc8 ) going back over 7 years.=C2=A0 It's a hard=
ware problem, but it does have a software fix.=C2=A0 But that fix must have=
 been left out of recent meta-bbb builds.=C2=A0 I believe previous fixes ha=
ve been something like this patch ( https://github.com/RobertCNelson/bb-ker=
nel/blob/607ae2e36477357a4bb222f285fd7460d5230ab9/patches/net/0009-cpsw-sea=
rch-for-phy.patch ).=C2=A0 That old patch targets the 3.15 kernel and I bel=
ieve Gatesgarth is using 5.10.=C2=A0 Should I expect that patch to work unm=
odified on 5.10?=C2=A0 I don't know low level kernel mechanics well enough =
to understand what it's really doing.=C2=A0 If that patch won't work, does =
anyone know how I could proceed to get ethernet working on the Beaglebone B=
lack with current versions of Yocto?

Dave

--sYL5DjBOmP45TVSr6MFU
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I have been using a Beaglebone Black for a project for years.&nbsp; I recen=
tly upgraded from Dunfell to Gatesgarth and again began experiencing a prob=
lem with the ethernet interface failing to come online 10% of the time, a p=
roblem which can only be fixed by a power cycle (not a reboot).&nbsp; This =
is a well known problem documented by <a title=3D"Beaglebone Black Ethernet=
 Phy Not Detected on Boot" href=3D"https://groups.google.com/g/beagleboard/=
c/9mctrG26Mc8" target=3D"_blank" rel=3D"noopener">this thread</a> going bac=
k over 7 years.&nbsp; It's a hardware problem, but it does have a software =
fix.&nbsp; But that fix must have been left out of recent meta-bbb builds.&=
nbsp; I believe previous fixes have been something like <a href=3D"https://=
github.com/RobertCNelson/bb-kernel/blob/607ae2e36477357a4bb222f285fd7460d52=
30ab9/patches/net/0009-cpsw-search-for-phy.patch" target=3D"_blank" rel=3D"=
noopener">this patch</a>.&nbsp; That old patch targets the 3.15 kernel and =
I believe Gatesgarth is using 5.10.&nbsp; Should I expect that patch to wor=
k unmodified on 5.10?&nbsp; I don't know low level kernel mechanics well en=
ough to understand what it's really doing.&nbsp; If that patch won't work, =
does anyone know how I could proceed to get ethernet working on the Beagleb=
one Black with current versions of Yocto?<br /><br />Dave

--sYL5DjBOmP45TVSr6MFU--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from fllv0016.ext.ti.com (fllv0016.ext.ti.com [198.47.19.142])
 by mx.groups.io with SMTP id smtpd.web11.11645.1615393429403762213
 for <meta-ti@lists.yoctoproject.org>;
 Wed, 10 Mar 2021 08:23:49 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@ti.com header.s=ti-com-17q1 header.b=NgI0fXko;
 spf=pass (domain: ti.com, ip: 198.47.19.142, mailfrom: nm@ti.com)
Received: from fllv0035.itg.ti.com ([10.64.41.0])
	by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 12AGNmqp084112;
	Wed, 10 Mar 2021 10:23:48 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com;
	s=ti-com-17Q1; t=1615393428;
	bh=oUjLxNMRldVrRaQn3mSdPqaXQ/ItxIVTS9plxasjWAU=;
	h=Date:From:To:CC:Subject:References:In-Reply-To;
	b=NgI0fXkoKN6+qexxzP6xshyJzcrQLvyTxRsHb1Hg7PRDAImunsP4gGSsptbV2ssDc
	 lQ2VvJh29ySaeM9dXXeKs1tKQzqCHiRSF8dS+aNU+qbTCQCMWnYSkUz24rYttAeprk
	 0IZEIQBkYmBX2QVNoe4atlYbzRyHVZ/eQVWcFWkM=
Received: from DFLE111.ent.ti.com (dfle111.ent.ti.com [10.64.6.32])
	by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 12AGNmP1106447
	(version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL);
	Wed, 10 Mar 2021 10:23:48 -0600
Received: from DFLE106.ent.ti.com (10.64.6.27) by DFLE111.ent.ti.com
 (10.64.6.32) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Wed, 10
 Mar 2021 10:23:47 -0600
Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE106.ent.ti.com
 (10.64.6.27) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2 via
 Frontend Transport; Wed, 10 Mar 2021 10:23:47 -0600
Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153])
	by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 12AGNlFa018682;
	Wed, 10 Mar 2021 10:23:47 -0600
Date: Wed, 10 Mar 2021 10:23:47 -0600
From: "Nishanth Menon" <nm@ti.com>
To: Dave Tucker <theaethereal@gmail.com>
CC: <meta-ti@lists.yoctoproject.org>,
        Grygorii Strashko
	<grygorii.strashko@ti.com>
Subject: Re: [meta-ti] Beaglebone Black Ethernet Failures
Message-ID: <20210310162347.qoefefbcagky3srn@boxcar>
References: <u0TL.1615382842912667990.O2ud@lists.yoctoproject.org>
MIME-Version: 1.0
In-Reply-To: <u0TL.1615382842912667990.O2ud@lists.yoctoproject.org>
User-Agent: NeoMutt/20171215
X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 05:27-20210310, Dave Tucker wrote:
> I have been using a Beaglebone Black for a project for years.=A0 I recent=
ly upgraded from Dunfell to Gatesgarth and again began experiencing a probl=
em with the ethernet interface failing to come online 10% of the time, a pr=
oblem which can only be fixed by a power cycle (not a reboot).=A0 This is a=
 well known problem documented by this thread ( https://groups.google.com/g=
/beagleboard/c/9mctrG26Mc8 ) going back over 7 years.=A0 It's a hardware pr=
oblem, but it does have a software fix.=A0 But that fix must have been left=
 out of recent meta-bbb builds.=A0 I believe previous fixes have been somet=
hing like this patch ( https://github.com/RobertCNelson/bb-kernel/blob/607a=
e2e36477357a4bb222f285fd7460d5230ab9/patches/net/0009-cpsw-search-for-phy.p=
atch ).=A0 That old patch targets the 3.15 kernel and I believe Gatesgarth =
is using 5.10.=A0 Should I expect that patch to work unmodified on 5.10?=A0=
 I don't know low level kernel mechanics well enough to understand what it'=
s really doing.=A0 If that patch won't work, does anyone know how I could p=
roceed to get ethernet working on the Beaglebone Black with current version=
s of Yocto?
>=20
> Dave


Probably addressed in u-boot instead by [1] ?

[1] https://source.denx.de/u-boot/u-boot/-/commit/20c37fb1bfb9f20804645b219=
9699cd815a4d55c


--=20
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5=
 849D 1736 249D

From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: Beaglebone Black Ethernet Failures
To: meta-ti@lists.yoctoproject.org
From: "Dave Tucker" <theaethereal@gmail.com>
X-Originating-Location: Troutville, Virginia, US (73.251.55.174)
X-Originating-Platform: Windows Firefox 86
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Thu, 11 Mar 2021 14:18:02 -0800
References: <20210310162347.qoefefbcagky3srn@boxcar>
In-Reply-To: <20210310162347.qoefefbcagky3srn@boxcar>
Message-ID: <15557.1615501082424309597@lists.yoctoproject.org>
Content-Type: multipart/alternative; boundary="uRHhVMOv5BmZ7DQvgTW3"

--uRHhVMOv5BmZ7DQvgTW3
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I applied this patch and it failed to compile after that, I assume because =
I'm running a later version of u-boot.=C2=A0 But more importantly, it looks=
 like this fix is already included in the u-boot source code.=C2=A0 I see a=
ll the code in board.c about fixing the ethernet phy on the beaglebone fami=
ly.=C2=A0 But I'm still having this ethernet issue so it's failing to fix t=
he problem.

--uRHhVMOv5BmZ7DQvgTW3
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I applied this patch and it failed to compile after that, I assume because =
I'm running a later version of u-boot.&nbsp; But more importantly, it looks=
 like this fix is already included in the u-boot source code.&nbsp; I see a=
ll the code in board.c about fixing the ethernet phy on the beaglebone fami=
ly.&nbsp; But I'm still having this ethernet issue so it's failing to fix t=
he problem.

--uRHhVMOv5BmZ7DQvgTW3--

From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: Beaglebone Black Ethernet Failures
To: meta-ti@lists.yoctoproject.org
From: "Dave Tucker" <theaethereal@gmail.com>
X-Originating-Location: Troutville, Virginia, US (73.251.55.174)
X-Originating-Platform: Windows Firefox 86
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Thu, 11 Mar 2021 14:19:34 -0800
References: <15557.1615501082424309597@lists.yoctoproject.org>
In-Reply-To: <15557.1615501082424309597@lists.yoctoproject.org>
Message-ID: <24755.1615501174442330946@lists.yoctoproject.org>
Content-Type: multipart/alternative; boundary="maFSCE7GvsLx57YFQ04e"

--maFSCE7GvsLx57YFQ04e
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Actually, looking back at it, this was a commit, not a patch.=C2=A0 So yes,=
 it is in the u-boot code already.=C2=A0 But it's failing to perform someho=
w.

--maFSCE7GvsLx57YFQ04e
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Actually, looking back at it, this was a commit, not a patch.&nbsp; So yes,=
 it is in the u-boot code already.&nbsp; But it's failing to perform someho=
w.

--maFSCE7GvsLx57YFQ04e--

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141])
 by mx.groups.io with SMTP id smtpd.web12.159.1615502244661427911
 for <meta-ti@lists.yoctoproject.org>;
 Thu, 11 Mar 2021 14:37:24 -0800
Authentication-Results: mx.groups.io;
 dkim=fail reason="body hash did not verify" header.i=@ti.com header.s=ti-com-17q1 header.b=bR5tKt1V;
 spf=pass (domain: ti.com, ip: 198.47.19.141, mailfrom: nm@ti.com)
Received: from lelv0265.itg.ti.com ([10.180.67.224])
	by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 12BMbNah073253;
	Thu, 11 Mar 2021 16:37:23 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com;
	s=ti-com-17Q1; t=1615502243;
	bh=Pzif2EcBxh6Iiyy6O5eFgy2PUco9SVHfZcaXrdll8zo=;
	h=Date:From:To:CC:Subject:References:In-Reply-To;
	b=bR5tKt1VMqL+QPt4l2uTl599ylKSBkJc/XOvCvguWWF+PojGY+ynQMW4KFHpp9lpo
	 WfSA1v+mcftVJtfk3oNmcJWoHhS8NC6yJsdTem5LHtac0S3JvuTdNYRRZZtwaTB1jU
	 BPzhU6vgGz83haA7tbfg28oPz7dEyXkejf/1Qe/4=
Received: from DFLE105.ent.ti.com (dfle105.ent.ti.com [10.64.6.26])
	by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 12BMbN7G047009
	(version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL);
	Thu, 11 Mar 2021 16:37:23 -0600
Received: from DFLE108.ent.ti.com (10.64.6.29) by DFLE105.ent.ti.com
 (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 11
 Mar 2021 16:37:23 -0600
Received: from lelv0327.itg.ti.com (10.180.67.183) by DFLE108.ent.ti.com
 (10.64.6.29) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2 via
 Frontend Transport; Thu, 11 Mar 2021 16:37:23 -0600
Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153])
	by lelv0327.itg.ti.com (8.15.2/8.15.2) with ESMTP id 12BMbNhX022731;
	Thu, 11 Mar 2021 16:37:23 -0600
Date: Thu, 11 Mar 2021 16:37:23 -0600
From: "Nishanth Menon" <nm@ti.com>
To: Dave Tucker <theaethereal@gmail.com>
CC: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti] Beaglebone Black Ethernet Failures
Message-ID: <20210311223723.qmvmcap3yjn2mzwu@opulently>
References: <15557.1615501082424309597@lists.yoctoproject.org>
 <24755.1615501174442330946@lists.yoctoproject.org>
MIME-Version: 1.0
In-Reply-To: <24755.1615501174442330946@lists.yoctoproject.org>
User-Agent: NeoMutt/20171215
X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180
X-MIME-Autoconverted: from 8bit to quoted-printable by fllv0015.ext.ti.com id 12BMbNah073253
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 14:19-20210311, Dave Tucker wrote:
> Actually, looking back at it, this was a commit, not a patch.=A0 So yes=
, it is in the u-boot code already.=A0 But it's failing to perform someho=
w.

Interesting. I'd suggest reaching out to linux-omap@vger.kernel.org and
cc beagle list to see what the recommendation is. The rationale of doing
in u-boot is that kernel folks dont like modifying device tree blobs
after kernel has started booting up..

If a patch is known, then usually stable-kernel rules should kick in and
should help percolate the patch back to 5.10 and other stable kernels.

I was glancing through kernelci.org upstream test logs[1] and i had'nt
noticed anything specific on this failure, so it will be interesting to
get a wider viewpoint.. Do be sure to paste the full bootlog (all the
way from u-boot's first print) in pastebin.ubuntu.com or a similar site
when sending the report to the kernel mailing list.

https://kernelci.org/soc/omap2/job/stable/kernel/v5.10.23/plan/baseline-n=
fs/

--=20
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DD=
B5 849D 1736 249D

From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54])
 by mx.groups.io with SMTP id smtpd.web08.2005.1615510740554770358
 for <meta-ti@lists.yoctoproject.org>;
 Thu, 11 Mar 2021 16:59:00 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@gmail.com header.s=20161025 header.b=dNXiYZIF;
 spf=pass (domain: gmail.com, ip: 209.85.208.54, mailfrom: robertcnelson@gmail.com)
Received: by mail-ed1-f54.google.com with SMTP id bf3so5625904edb.6
        for <meta-ti@lists.yoctoproject.org>; Thu, 11 Mar 2021 16:59:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:references:in-reply-to:from:date:message-id:subject:to
         :cc;
        bh=tvNMnt7I6BxNX8ElWHl5NgRvIm7phEELZ2y37rg22mU=;
        b=dNXiYZIFrytG0/tItG03IX1eYqYxR315VVghV6c0mh+WHDHYQ5fUJxl2rABJRhc2qA
         LH2LCPgzMvIpJFqUCm0MeY4NlKWTAaqR1xLaD5CxyQqwuGFdgRXiS6zQtCpT2+4AI/Em
         CXaC+eyfxkRmURcN2NxKWQXUiTwyU01fwIdtkCAceykrHvny8igUxauuj/ulMbLUD40F
         Ii6py6VoIL05T/JR27NM7J2f8LHz/9QnN6jnvBLhQe5XaOLqmOLgzSkLR2PiJzv9cGp6
         6LaXRpRyvP3AgwHOSLn3dbX4ehjC3Fa5SyB1EeqeI2Nf6XVs6wRUrwl1H2Tb2hRnmh6F
         6tlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=tvNMnt7I6BxNX8ElWHl5NgRvIm7phEELZ2y37rg22mU=;
        b=d07VUdSjOGQ0zhoz3/fBTg01qKcxN5vFLh6/i7riENs78A+8rUJrMWJMHFMD8k0Kjp
         yrA+o4z7HHTlMWtBj+hbS7LorkLBsz3rtwbqwyfgga/nLWhoDqIymrizFaqYmQhKoCbr
         ol16tNdH+0c6vHHRPSE6OsadoICfL8sgQFpFThP9ZTD/ayprA/8MlTQkfb5sqRZp77Hp
         AwuGYhugEZienTvhCLD7Ppmtod7zCqVIVNsIom0AToaCUDCjtLoZR+H/J0uKlsju7r48
         it5702FLEJEXheUV0puZbntuCTOxl1ckLu7tDk7bY7vhmJG7cqsRLiKr89NT7V8izp8T
         eHbg==
X-Gm-Message-State: AOAM5334+asKB0rcGvhstiqKGVcJ9emwCU13aKSSQr5eSUZqP5Fy7zUk
	2R9AvYlohwFrpUToXqaDwUg4lyangn8OeA8teqA=
X-Google-Smtp-Source: ABdhPJwut5JtZI155yU0ITy3v59XEDX5eHJtabmAaFlCmMGV40SUyTKft6yrQMPdWvb/GGdczvIaekr6E70izmUj+00=
X-Received: by 2002:aa7:c0c7:: with SMTP id j7mr11298883edp.298.1615510738994;
 Thu, 11 Mar 2021 16:58:58 -0800 (PST)
MIME-Version: 1.0
References: <15557.1615501082424309597@lists.yoctoproject.org> <24755.1615501174442330946@lists.yoctoproject.org>
In-Reply-To: <24755.1615501174442330946@lists.yoctoproject.org>
From: "Robert Nelson" <robertcnelson@gmail.com>
Date: Thu, 11 Mar 2021 18:57:27 -0600
Message-ID: <CAOCHtYjagGkpX0EkZXDr_PrL4DHqkdYkXdhzraG1=+b+5xOASA@mail.gmail.com>
Subject: Re: [meta-ti] Beaglebone Black Ethernet Failures
To: Dave Tucker <theaethereal@gmail.com>
Cc: meta-ti@lists.yoctoproject.org
Content-Type: text/plain; charset="UTF-8"

On Thu, Mar 11, 2021 at 4:19 PM Dave Tucker <theaethereal@gmail.com> wrote:
>
> Actually, looking back at it, this was a commit, not a patch.  So yes, it is in the u-boot code already.  But it's failing to perform somehow.

For the am335x target, u-boot supports two path's, legacy "board" path
and newer "device tree" path.. That fixup only applies if your build
of u-boot uses the new "device tree" path..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: Beaglebone Black Ethernet Failures
To: meta-ti@lists.yoctoproject.org
From: "Dave Tucker" <theaethereal@gmail.com>
X-Originating-Location: Troutville, Virginia, US (73.251.55.174)
X-Originating-Platform: Windows Firefox 86
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Fri, 12 Mar 2021 06:11:42 -0800
References: <CAOCHtYjagGkpX0EkZXDr_PrL4DHqkdYkXdhzraG1=+b+5xOASA@mail.gmail.com>
In-Reply-To: <CAOCHtYjagGkpX0EkZXDr_PrL4DHqkdYkXdhzraG1=+b+5xOASA@mail.gmail.com>
Message-ID: <2543.1615558302870675945@lists.yoctoproject.org>
Content-Type: multipart/alternative; boundary="6pLiUyax3acKtvm4Sp4G"

--6pLiUyax3acKtvm4Sp4G
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Robert,

Thank you so much for the reply.=C2=A0 Do you know of a reference that exp=
lains this distinction between board and devicetree paths?=C2=A0 My google-=
fu is failing me.

I am loading a dtb file, but I don't know if that means I'm on the "device=
tree path".=C2=A0 I've configured u-boot to load from a uEnv.txt which look=
s like this, and that loads the dtb from the first partition, and I know th=
at part works:

bootfile=3DzImage
fdtfile=3Dam335x-boneblack.dtb
loadaddr=3D0x80007fc0
fdtaddr=3D0x80F80000
console=3DttyO0,115200
mmcroot=3D/dev/mmcblk1p2
mmcrootfstype=3Dext4
loadfdt=3Dfatload mmc 1:1 ${fdtaddr} ${fdtfile}
loaduimage=3Dfatload mmc 1:1 ${loadaddr} ${bootfile}
mmc_args=3Dsetenv bootargs console=3D${console} ${optargs} root=3D${mmcroo=
t} rootfstype=3D${mmcrootfstype}
fdtboot=3Drun mmc_args; bootz ${loadaddr} - ${fdtaddr}
uenvcmd=3Dmmc rescan; run loaduimage; run loadfdt; run fdtboot

Thank you so much,

Dave

--6pLiUyax3acKtvm4Sp4G
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<p>Robert,<br /><br />Thank you so much for the reply.&nbsp; Do you know of=
 a reference that explains this distinction between board and devicetree pa=
ths?&nbsp; My google-fu is failing me.</p>
<p>I am loading a dtb file, but I don't know if that means I'm on the "dev=
icetree path".&nbsp; I've configured u-boot to load from a uEnv.txt which l=
ooks like this, and that loads the dtb from the first partition, and I know=
 that part works:</p>
<p>bootfile=3DzImage<br />fdtfile=3Dam335x-boneblack.dtb<br />loadaddr=3D0=
x80007fc0<br />fdtaddr=3D0x80F80000<br />console=3DttyO0,115200<br />mmcroo=
t=3D/dev/mmcblk1p2<br />mmcrootfstype=3Dext4<br />loadfdt=3Dfatload mmc 1:1=
 ${fdtaddr} ${fdtfile}<br />loaduimage=3Dfatload mmc 1:1 ${loadaddr} ${boot=
file}<br />mmc_args=3Dsetenv bootargs console=3D${console} ${optargs} root=
=3D${mmcroot} rootfstype=3D${mmcrootfstype}<br />fdtboot=3Drun mmc_args; b=
ootz ${loadaddr} - ${fdtaddr}<br />uenvcmd=3Dmmc rescan; run loaduimage; ru=
n loadfdt; run fdtboot</p>
<p>Thank you so much,<br /><br />Dave</p>

--6pLiUyax3acKtvm4Sp4G--