From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Haas Date: Sat, 19 Mar 2016 10:35:49 +0100 Subject: [U-Boot] [PATCH] Add CONFIG_GMAC_TX_DELAY=4 for OlinuXino Lime2 In-Reply-To: <56ED1C96.30708@redhat.com> References: <1458020499-9506-1-git-send-email-haas@computerlinguist.org> <20160315180914.GA1878@excalibur.cnev.de> <56E91A12.8080506@computerlinguist.org> <56E9278F.7060801@redhat.com> <20160316203642.GC1817@excalibur.cnev.de> <56EA4097.3010500@computerlinguist.org> <56EA8C5E.1070701@redhat.com> <56EC78F7.80507@computerlinguist.org> <56ed1046.857ac20a.dc7f4.ffffb08e@mx.google.com> <56ED1C96.30708@redhat.com> Message-ID: <56ED1D75.50008@computerlinguist.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 03/19/2016 10:32 AM, Hans de Goede wrote: > Hi, > > On 19-03-16 09:39, Fran?ois-David Collin wrote: >> Hi, >> >> As I?m banging my head on this too, please allow me to provide some >> details >> I got two stable situations : >> The Lime2 is connected directly to the Gbit interface of my laptop, >> speed are OK: > > Michael Haas' work to debug this by looking at the phy registers > seems to be the most promising so-far, the clk reg and axp209 > registers all seem to be identical between good and bad setups. > > Can you try to: > > 1) Stop the boot in u-boot (press a key on the serial console) > 2) Bring up the network, e.g. type "dhcp" then ctrl+c when it tries > to tftp > 3) Do: "mii read 1 0x11" in u-boot and record the output ? > > Regards, > > Hans I am currently (as I write this email) looking at the full set of registers for the PHY, including the additional pages: setenv miipagedump 'for page in 0x0 0x01 0x02 0x03 0x04 0x05 0x06 0x07; do echo "page $page"; mii write 1 0x1f $page; run miidump; done; mii write 1 0x1f 0x00' setenv miireadable 'setenv x 0x0; while test $x -le 5; do echo $x; mii dump 1 $x; setexpr x $x + 1; done' setenv miidump 'setenv x 0x0; while test $x -le 31; do echo $x; mii read 1 $x; setexpr x $x + 1; done' setenv pmicdump 'i2c md 0x34 0xff' setenv clkdump 'md 0x1c20164' setenv doboot 'run pmicdump; run clkdump; setenv bootargs console=ttyS0,115200 rootwait panic=10; setenv autoload no;dhcp; run miireadable; run miipagedump; setenv serverip 192.168.1.170;tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr;source ${scriptaddr}' No results as of yet, but I have yet to do a run where I successfully dump all extpages.. the script was off before hand. Some registers were different between working and non-working runs, but these were mostly reserved. I will be posting a full log later on. Interesting: 01c20224 is 14888022 for broken runs and 14888021 on working runs - but I have not verified this extensively. I'm hanging out as 'laga' in #u-boot. Michael Another