From: Frank Wunderlich <frank-w@public-files.de>
To: Trent Piepho <trent.piepho@igorinstitute.com>
Cc: Oleksij Rempel <linux@rempel-privat.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
barebox@lists.infradead.org
Subject: Aw: Re: change r2pro dts to public hw version (was "Board code with 2 dts" )
Date: Mon, 11 Apr 2022 11:00:55 +0200 [thread overview]
Message-ID: <trinity-9f11e583-37b9-4f74-ad3b-0c3fa278e1ed-1649667655332@3c-app-gmx-bap51> (raw)
In-Reply-To: <CAMHeXxP3OeqMFDL_Ry81X80vjKu-G8FDHtwrDJprKOmFc-pTEg@mail.gmail.com>
Hi,
it turned out that my problem is not wrong setting...it was the load method.
i loaded barebox by uboot like it's documented here:
https://www.barebox.org/doc/latest/user/barebox.html#starting-barebox
except i have loaded files via fatload and not tftp.
if i flash barebox and boot directly into it, network works (also with first version of dts with rx-delay/tx-delay and rgmii phy_mode).
barebox@BPI R2PRO:/ dhcp eth1
eth1: 1000Mbps full duplex link detected
WARNING: eth1: No MAC address set. Using random address 92:26:6a:9c:ec:d5
T T T eth1: DHCP client bound to address 192.168.0.104
barebox@BPI R2PRO:/ ping 192.168.0.10
PING 192.168.0.10 (192.168.0.10)
host 192.168.0.10 is alive
so imho there are 2 possible rootcauses
- uboot has initialized anything (clocks/pinctrl/...) which barebox cannot change afterwards (due to missing reset)
- barebox skips any initialization step if it is chainloaded
i have now tested both configurations (rgmii+delays and rgmii-id without delay-properties, but delays set in driver). linux is already updated in next to the rgmii+delays part, so i would send this as update to barebox.
regards Frank
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-04-11 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 17:23 Board code with 2 dts Frank Wunderlich
2022-03-22 17:34 ` Ahmad Fatoum
2022-03-23 7:47 ` Aw: " Frank Wunderlich
2022-03-23 8:03 ` Ahmad Fatoum
2022-04-08 11:03 ` change r2pro dts to public hw version (was "Board code with 2 dts" ) Frank Wunderlich
2022-04-08 17:00 ` Oleksij Rempel
2022-04-08 17:19 ` Frank Wunderlich
2022-04-09 8:04 ` Oleksij Rempel
2022-04-09 8:35 ` Aw: " Frank Wunderlich
2022-04-09 16:01 ` Oleksij Rempel
2022-04-09 17:08 ` Trent Piepho
2022-04-10 7:41 ` Oleksij Rempel
2022-04-10 8:28 ` Frank Wunderlich
2022-04-10 9:28 ` Trent Piepho
2022-04-10 15:00 ` Oleksij Rempel
2022-04-10 20:36 ` Trent Piepho
2022-04-11 9:00 ` Frank Wunderlich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-9f11e583-37b9-4f74-ad3b-0c3fa278e1ed-1649667655332@3c-app-gmx-bap51 \
--to=frank-w@public-files.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=linux@rempel-privat.de \
--cc=trent.piepho@igorinstitute.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox