Trouble with alternate PHY on MPC8313ERDB (configuration)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Trouble with alternate PHY on MPC8313ERDB (configuration)

Jump to solution
1,862 Views
D_a_v_e
Contributor I
Hello,
 
I have a board which is a modified MPC8313ERDB to have broadcom phy instead of marvell.
It's having trouble finding the phy at boot, and it looks like the bus_id is incorrect.  The marvell is
at bus address 4, but my broadcom is at 5.  In the boot log I see:
 
e0024520:04 not found
eth1: Could not attach to PHY
 
I think the :04 is the bus id being used from the marvell. I've looked, but can't figure our where this
is configured.
 
This is with the ubuntu linux distribution, ltib-mpc8313erdb-20070824.
 
I am _not_ very versed in linux.
 
Thanks for any help.
 
Dave
 
0 Kudos
1 Solution
905 Views
admin
Specialist II
Hi
I don't know if youre problem comes from the kernel boot, or if it's from the bootloader...
Anyway, I imagine two ways to get such error (all of them comming from the kernel) :
the first one is that you don't have the correct phy driver
the second one is that you didn't change the dts tree, to match you're board...
(the device tree is in [kernel_path]/arch/powerpc/boot/dts/)

Good luck !!
CimCim


Message Edited by cimcim on 2008-03-06 02:21 PM

View solution in original post

0 Kudos
2 Replies
906 Views
admin
Specialist II
Hi
I don't know if youre problem comes from the kernel boot, or if it's from the bootloader...
Anyway, I imagine two ways to get such error (all of them comming from the kernel) :
the first one is that you don't have the correct phy driver
the second one is that you didn't change the dts tree, to match you're board...
(the device tree is in [kernel_path]/arch/powerpc/boot/dts/)

Good luck !!
CimCim


Message Edited by cimcim on 2008-03-06 02:21 PM
0 Kudos
906 Views
D_a_v_e
Contributor I
Thanks CimCim,
 
You got it.  I hadn't found the .dts file for the right configuration.  I had been searching though
the configs, but hadn't found those files.  So now it is finding the device!  (It's not working yet,
I think I now have the driver issues).
Thanks for pointing me in the right direction.
 
Dave
 
0 Kudos