From: "Mylene Josserand" <Mylene.Josserand@navocap.com>
To: barebox mailist <barebox@lists.infradead.org>
Subject: [help] PHY driver : Unable to find a PHY (unknown ID?)
Date: Fri, 4 Jan 2013 10:09:05 +0100 [thread overview]
Message-ID: <CA78C307B8F06747967D122FC656B15377433D@SERVEUR0.nvp.local> (raw)
Hi everyone !
I am new in compiling Barebox (with OE-core) and I need your help.
I am using the master branch (maybe I need to checkout a tag ?). The
ethernet of my board is a SMSC LAN8700 and the microchip is iMX27.
I have configured the new source of barebox to use the Phylib and MII
drivers. When my barebox starts, I have an error about the PHY driver :
"
Unable to find a PHY (unknown ID?)
dhcp failed: I/O error
dhcp: I/O error
"
My devinfo :
"
barebox:/ devinfo
devices:
`---- platform
`---- imx_iim0
`---- imx27-ccm0
`---- imx1-gpt0
`---- imx1-gpio0
`---- imx1-gpio1
`---- imx1-gpio2
`---- imx1-gpio3
`---- imx1-gpio4
`---- imx1-gpio5
`---- imx21-wdt0
`---- imx27-esdctl0
`---- imx21-uart0
`---- cs0
`---- mem0
`---- 0x00000000-0x07ffffff: /dev/ram0
`---- mem1
`---- 0x00000000-0xfffffffe: /dev/mem
`---- cfi_flash0
`---- 0x00000000-0x01ffffff: /dev/nor0
`---- 0x00000000-0x0003ffff: /dev/self0
`---- 0x00040000-0x0005ffff: /dev/env0
`---- 0x00000000-0x0003ffff: /dev/nor0.barebox
`---- 0x00040000-0x0005ffff: /dev/nor0.bareboxenv
`---- 0x00060000-0x002bffff: /dev/nor0.kernel
`---- 0x002c0000-0x01ffffff: /dev/nor0.root
`---- cfi_flash1
`---- 0x00000000-0x01ffffff: /dev/nor1
`---- imx_nand
`---- nand0
`---- 0x00000000-0x1fffffff: /dev/nand0
`---- 0x00000000-0x00ffffff: /dev/nand_oob0
`---- i2c-fsl0
`---- i2c0
`---- lp39720
`---- 0x00000000-0x000000ff: /dev/lp3972
`---- ds133x0
`---- 0x00000000-0x000000ff: /dev/ds133x
`---- pca95350
`---- 0x00000000-0x000000ff: /dev/pca9535
`---- i2c-fsl1
`---- i2c1
`---- imxfb
`---- imx27-fec
`---- miibus0
`---- eth0
`---- mdio_bus
`---- i2c
`---- fb
`---- fb0
`---- 0x00000000-0x000bb7ff: /dev/fb0
`---- fs
`---- ramfs0
`---- devfs0
`---- net
`---- global
drivers:
imx27-ccm
imx_serial
imx-esdctl
ramfs
devfs
tftp
imx-gpt
imx-gpio
SMSC LAN83C185
SMSC LAN8187
SMSC LAN8700
SMSC LAN911x Internal PHY
SMSC LAN8710/LAN8720
fec_imx
Generic PHY
imx_nand
cfi_flash
i2c-gpio
i2c-fsl
fb
imxfb
lp3972
ds133x
pca9535
imx-watchdog
mem
"
The SMSC LAN8700 is here but I can not make it work !
I have added some prints on the phy.c and the problem is in the fonction
"mdiobus_scan" :
if (!edev->phydev) {
if (addr >= 0) {
dev = mdiobus_scan(bus, addr);
if (!dev) { << Failed here
ret = -EIO;
goto fail;
}
Did I miss something ?
Did I have to specify something in the board info ?
Is it correct to use the master branch ? I tried the v2012.12.1 tag but
I get some errors before starting barebox ("no stack data available" and
other errors).
Thank you in advance for any help and happy new year !
--
Mylène JOSSERAND
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-01-04 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 9:09 Mylene Josserand [this message]
2013-01-04 10:18 ` Thomas Petazzoni
2013-01-04 11:03 ` Mylene Josserand
2013-01-04 11:23 ` Thomas Petazzoni
2013-01-04 12:46 ` Mylene Josserand
2013-01-04 13:28 ` Eric Bénard
2013-01-07 13:56 ` Mylene Josserand
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=CA78C307B8F06747967D122FC656B15377433D@SERVEUR0.nvp.local \
--to=mylene.josserand@navocap.com \
--cc=barebox@lists.infradead.org \
/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