public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@de.bosch.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AR8031 Ethernet on mx6
Date: Mon, 17 Sep 2012 10:44:37 +0200	[thread overview]
Message-ID: <5056E2F5.4040008@de.bosch.com> (raw)
In-Reply-To: <CAOMZO5CN-_6X_dJ8eozWm5UR1htkp6j4PpT+BwY17a0yf3caXg@mail.gmail.com>

On 15.09.2012 05:06, Fabio Estevam wrote:
> Hi Jason,
> 
> I don't have a mx6qarm2 and would like to ask you if you could please
> confirm that Ethernet is functional on mx6qarm2 running the latest
> U-boot.
> 
> I am trying to get Ethernet working on mx6qsabresd, which also uses
> the same AR8031 PHY, but it is not working yet.
> 
> AR8031 is supposed to output a 125MHz clock to mx6q, but I see a 25MHz
> clock instead.
> 
> I do the same PHY init as in mx6qarm2.
> 
> Any ideas/suggestions are appreciated.

Trying the recent mainline U-Boot (a6f0c4faa4c65a7b7048b) on an ARM2 
board we get [1] after manually setting an ethaddr and the IP addresses.

Sometimes U-Boot seems to hang after 'MMC:   FSL_SDHC: 0, FSL_SDHC: 1' 
but this might be an other issue.

Best regards

Dirk

[1]

U-Boot 2012.07-00490-ga6f0c4f (Sep 17 2012 - 10:01:46)

CPU:   Freescale i.MX6Q rev1.0 at 792 MHz
Reset cause: POR
Board: MX6Q-Armadillo2
DRAM:  2 GiB
WARNING: Caches not enabled
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
In:    serial
Out:   serial
Err:   serial
Net:   FEC
Hit any key to stop autoboot:  0
MX6QARM2 U-Boot > printenv
baudrate=115200
bootargs=console=ttymxc3,115200 root=/dev/nfs ip=dhcp nfsroot=:,v3,tcp
bootcmd=mmc dev ${mmcdev};if mmc rescan ${mmcdev}; then if run 
loadbootscript; then run bootscript; else if run loi
bootdelay=3
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc3
ethact=FEC
ethaddr=00:19:B8:00:E5:4E
fdt_high=0xffffffff
initrd_high=0xffffffff
ipaddr=172.17.0.1
loadaddr=0x10800000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loaduimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm
mmcdev=1
mmcpart=2
mmcroot=/dev/mmcblk0p3 rootwait rw
netargs=setenv bootargs console=${console},${baudrate} root=/dev/nfs 
ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
netboot=echo Booting from net ...; run netargs; dhcp ${uimage}; bootm
script=boot.scr
serverip=172.17.0.6
stderr=serial
stdin=serial
stdout=serial
uimage=uImage
Environment size: 1125/8188 bytes
MX6QARM2 U-Boot > tftpboot ${loadaddr} uImage
Using FEC device
TFTP from server 172.17.0.6; our IP address is 172.17.0.1
Filename 'uImage'.
Load address: 0x10800000
Loading: 
################################################################# 
   #################################################################
#################################################################
#############################################################
done
Bytes transferred = 3756664 (395278 hex)
MX6QARM2 U-Boot >

  parent reply	other threads:[~2012-09-17  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15  3:06 [U-Boot] AR8031 Ethernet on mx6 Fabio Estevam
2012-09-15  5:32 ` Dirk Behme
2012-09-15 19:23   ` Fabio Estevam
2012-09-15 19:26     ` Marek Vasut
2012-09-15 20:38       ` Eric Nelson
2012-09-17  8:44 ` Dirk Behme [this message]
2012-09-17 13:21   ` Fabio Estevam

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=5056E2F5.4040008@de.bosch.com \
    --to=dirk.behme@de.bosch.com \
    --cc=u-boot@lists.denx.de \
    /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