ifconfig MPC8313

ifconfig MPC8313

[Ronald Madrid]

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

Hello all,

I am working on porting linux 2.6.25 with a custom MPC8313 based board, but am having a little bit of trouble with the ethernet, more specifically ifconfig.

after typing "ifconfig eth0 10.196.31.84" I receive the following error
ifconfig: SIOCSIFFLAGS: Cannot assign requested address

after entering a MAC address via "ifconfig eth0 hw ether"  I receive this error.
e0024520:01 not found
eth0: Could not attach to PHY
ifconfig: SIOCSIFFLAGS: No such device

which I have traced to bus_find_device, but I'm not sure what to make of this.

I'm not sure where I'm going wrong here, and I'm sure that it's something that I'm forgetting to do/include.

Sorry if this isn't enough information, but I don't know enough to know what other information would be needed.


Ron

_________________________________________________________________
Get Free (PRODUCT) RED™  Emoticons, Winks and Display Pics.
http://joinred.spaces.live.com?ocid=TXT_HMTG_prodredemoticons_052008

[-- Attachment #2: Type: text/html, Size: 1254 bytes --]

Re: ifconfig MPC8313

[Scott Wood]

Ronald Madrid wrote:
> Hello all,
> 
> I am working on porting linux 2.6.25 with a custom MPC8313 based board, 
> but am having a little bit of trouble with the ethernet, more 
> specifically ifconfig.
> 
> after typing "ifconfig eth0 10.196.31.84" I receive the following error
> ifconfig: SIOCSIFFLAGS: Cannot assign requested address
> 
> after entering a MAC address via "ifconfig eth0 hw ether"  I receive 
> this error.
> e0024520:01 not found
> eth0: Could not attach to PHY
> ifconfig: SIOCSIFFLAGS: No such device

It can't find the PHY for eth0.  What does your device tree look like, 
and what is the relevant PHY address?

-Scott

RE: ifconfig MPC8313

[Ronald Madrid]

[-- Attachment #1: Type: text/plain, Size: 9304 bytes --]

I'm guessing by device tree you mean the .dts file?  I'm using a modified version of the mpc8313erdb.dts with minor changes (to the local bus only).  Here is a copy of it./* * MPC8313E RDB Device Tree Source * * Copyright 2005, 2006, 2007 Freescale Semiconductor Inc. * * This program is free software; you can redistribute  it and/or modify it * under  the terms of  the GNU General  Public License as published by the * Free Software Foundation;  either version 2 of the  License, or (at your * option) any later version. *//dts-v1/;/ {    model = "MPC8313ERDB";    compatible = "MPC8313ERDB", "MPC831xRDB", "MPC83xxRDB";    #address-cells = <1>;    #size-cells = <1>;    aliases {        ethernet0 = &enet0;        ethernet1 = &enet1;        serial0 = &serial0;        serial1 = &serial1;        pci0 = &pci0;    };    cpus {        #address-cells = <1>;        #size-cells = <0>;        PowerPC,8313@0 {            device_type = "cpu";            reg = <0x0>;            d-cache-line-size = <32>;            i-cache-line-size = <32>;            d-cache-size = <16384>;            i-cache-size = <16384>;            timebase-frequency = <0>;    // from bootloader            bus-frequency = <0>;        // from bootloader            clock-frequency = <0>;        // from bootloader        };    };    memory {        device_type = "memory";        reg = <0x00000000 0x08000000>;    // 128MB at 0    };    localbus@e0005000 {        #address-cells = <2>;        #size-cells = <1>;        compatible = "fsl,mpc8313-elbc", "fsl,elbc", "simple-bus";        reg = <0xe0005000 0x1000>;        interrupts = <77 0x8>;        interrupt-parent = <&ipic>;        // CS0 and CS1 are swapped when        // booting from nand, but the        // addresses are the same.//        ranges = <0x0 0x0 0xfe000000 0x00800000//                  0x1 0x0 0xe2800000 0x00008000//                  0x2 0x0 0xf0000000 0x00020000//                  0x3 0x0 0xfa000000 0x00008000>;        ranges = <0x0 0x0 0xe2800000 0x00008000>;//        flash@0,0 {//            #address-cells = <1>;//            #size-cells = <1>;//            compatible = "cfi-flash";//            reg = <0x0 0x0 0x800000>;//            bank-width = <2>;//            device-width = <1>;//        };//        nand@1,0 {        nand@0,0 {            #address-cells = <1>;            #size-cells = <1>;            compatible = "fsl,mpc8313-fcm-nand",                         "fsl,elbc-fcm-nand";//            reg = <0x1 0x0 0x2000>;            reg = <0x0 0x0 0x2000>;            u-boot@0 {                reg = <0x0 0x100000>;                read-only;            };            kernel@100000 {                reg = <0x100000 0x300000>;            };            fs@400000 {                reg = <0x400000 0x1c00000>;            };        };    };    soc8313@e0000000 {        #address-cells = <1>;        #size-cells = <1>;        device_type = "soc";        compatible = "simple-bus";        ranges = <0x0 0xe0000000 0x00100000>;        reg = <0xe0000000 0x00000200>;        bus-frequency = <0>;        wdt@200 {            device_type = "watchdog";            compatible = "mpc83xx_wdt";            reg = <0x200 0x100>;        };        i2c@3000 {            #address-cells = <1>;            #size-cells = <0>;            cell-index = <0>;            compatible = "fsl-i2c";            reg = <0x3000 0x100>;            interrupts = <14 0x8>;            interrupt-parent = <&ipic>;            dfsrr;            rtc@68 {                compatible = "dallas,ds1339";                reg = <0x68>;            };        };        i2c@3100 {            #address-cells = <1>;            #size-cells = <0>;            cell-index = <1>;            compatible = "fsl-i2c";            reg = <0x3100 0x100>;            interrupts = <15 0x8>;            interrupt-parent = <&ipic>;            dfsrr;        };        spi@7000 {            cell-index = <0>;            compatible = "fsl,spi";            reg = <0x7000 0x1000>;            interrupts = <16 0x8>;            interrupt-parent = <&ipic>;            mode = "cpu";        };        /* phy type (ULPI, UTMI, UTMI_WIDE, SERIAL) */        usb@23000 {            compatible = "fsl-usb2-dr";            reg = <0x23000 0x1000>;            #address-cells = <1>;            #size-cells = <0>;            interrupt-parent = <&ipic>;            interrupts = <38 0x8>;            phy_type = "utmi_wide";        };        mdio@24520 {            #address-cells = <1>;            #size-cells = <0>;            compatible = "fsl,gianfar-mdio";            reg = <0x24520 0x20>;            phy1: ethernet-phy@1 {                interrupt-parent = <&ipic>;                interrupts = <19 0x8>;                reg = <0x1>;                device_type = "ethernet-phy";            };            phy4: ethernet-phy@4 {                interrupt-parent = <&ipic>;                interrupts = <20 0x8>;                reg = <0x4>;                device_type = "ethernet-phy";            };        };        enet0: ethernet@24000 {            cell-index = <0>;            device_type = "network";            model = "eTSEC";            compatible = "gianfar";            reg = <0x24000 0x1000>;            local-mac-address = [ 00 00 00 00 00 00 ];            interrupts = <37 0x8 36 0x8 35 0x8>;            interrupt-parent = <&ipic>;            phy-handle = < &phy1 >;        };        enet1: ethernet@25000 {            cell-index = <1>;            device_type = "network";            model = "eTSEC";            compatible = "gianfar";            reg = <0x25000 0x1000>;            local-mac-address = [ 00 00 00 00 00 00 ];            interrupts = <34 0x8 33 0x8 32 0x8>;            interrupt-parent = <&ipic>;            phy-handle = < &phy4 >;        };        serial0: serial@4500 {            cell-index = <0>;            device_type = "serial";            compatible = "ns16550";            reg = <0x4500 0x100>;            clock-frequency = <0>;            interrupts = <9 0x8>;            interrupt-parent = <&ipic>;        };        serial1: serial@4600 {            cell-index = <1>;            device_type = "serial";            compatible = "ns16550";            reg = <0x4600 0x100>;            clock-frequency = <0>;            interrupts = <10 0x8>;            interrupt-parent = <&ipic>;        };        crypto@30000 {            device_type = "crypto";            model = "SEC2";            compatible = "talitos";            reg = <0x30000 0x7000>;            interrupts = <11 0x8>;            interrupt-parent = <&ipic>;            /* Rev. 2.2 */            num-channels = <1>;            channel-fifo-len = <24>;            exec-units-mask = <0x0000004c>;            descriptor-types-mask = <0x0122003f>;        };        /* IPIC         * interrupts cell = <intr #, sense>         * sense values match linux IORESOURCE_IRQ_* defines:         * sense == 8: Level, low assertion         * sense == 2: Edge, high-to-low change         */        ipic: pic@700 {            interrupt-controller;            #address-cells = <0>;            #interrupt-cells = <2>;            reg = <0x700 0x100>;            device_type = "ipic";        };    };    pci0: pci@e0008500 {        cell-index = <1>;        interrupt-map-mask = <0xf800 0x0 0x0 0x7>;        interrupt-map = <                /* IDSEL 0x0E -mini PCI */                 0x7000 0x0 0x0 0x1 &ipic 18 0x8                 0x7000 0x0 0x0 0x2 &ipic 18 0x8                 0x7000 0x0 0x0 0x3 &ipic 18 0x8                 0x7000 0x0 0x0 0x4 &ipic 18 0x8                /* IDSEL 0x0F - PCI slot */                 0x7800 0x0 0x0 0x1 &ipic 17 0x8                 0x7800 0x0 0x0 0x2 &ipic 18 0x8                 0x7800 0x0 0x0 0x3 &ipic 17 0x8                 0x7800 0x0 0x0 0x4 &ipic 18 0x8>;        interrupt-parent = <&ipic>;        interrupts = <66 0x8>;        bus-range = <0x0 0x0>;        ranges = <0x02000000 0x0 0x90000000 0x90000000 0x0 0x10000000              0x42000000 0x0 0x80000000 0x80000000 0x0 0x10000000              0x01000000 0x0 0x00000000 0xe2000000 0x0 0x00100000>;        clock-frequency = <66666666>;        #interrupt-cells = <1>;        #size-cells = <2>;        #address-cells = <3>;        reg = <0xe0008500 0x100>;        compatible = "fsl,mpc8349-pci";        device_type = "pci";    };};Ron> Date: Tue, 6 May 2008 16:19:25 -0500> From: scottwood@freescale.com> To: ron_madrid@hotmail.com> CC: linuxppc-dev@ozlabs.org> Subject: Re: ifconfig MPC8313> > Ronald Madrid wrote:> > Hello all,> > > > I am working on porting linux 2.6.25 with a custom MPC8313 based board, > > but am having a little bit of trouble with the ethernet, more > > specifically ifconfig.> > > > after typing "ifconfig eth0 10.196.31.84" I receive the following error> > ifconfig: SIOCSIFFLAGS: Cannot assign requested address> > > > after entering a MAC address via "ifconfig eth0 hw ether"  I receive > > this error.> > e0024520:01 not found> > eth0: Could not attach to PHY> > ifconfig: SIOCSIFFLAGS: No such device> > It can't find the PHY for eth0.  What does your device tree look like, > and what is the relevant PHY address?> > -Scott
_________________________________________________________________
Windows Live SkyDrive lets you share files with faraway friends.
http://www.windowslive.com/skydrive/overview.html?ocid=TXT_TAGLM_WL_Refresh_skydrive_052008

[-- Attachment #2: Type: text/html, Size: 21642 bytes --]

Re: ifconfig MPC8313

[Scott Wood]

Ronald Madrid wrote:
> I'm guessing by device tree you mean the .dts file?  I'm using a 
> modified version of the mpc8313erdb.dts with minor changes (to the local 
> bus only).  Here is a copy of it.

OK, according to that device tree, eth0 is associated with PHY address 
1.  Is that correct on your board?

-Scott

RE: ifconfig MPC8313

[Ronald Madrid]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

I don't know, where would I find that out?

Sorry, I'm still kind of new to this.

Ron

> Date: Tue, 6 May 2008 16:35:38 -0500
> From: scottwood@freescale.com
> To: ron_madrid@hotmail.com
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
> 
> Ronald Madrid wrote:
> > I'm guessing by device tree you mean the .dts file?  I'm using a 
> > modified version of the mpc8313erdb.dts with minor changes (to the local 
> > bus only).  Here is a copy of it.
> 
> OK, according to that device tree, eth0 is associated with PHY address 
> 1.  Is that correct on your board?
> 
> -Scott

_________________________________________________________________
Stay in touch when you're away with Windows Live Messenger.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_messenger_052008

[-- Attachment #2: Type: text/html, Size: 1173 bytes --]

Re: ifconfig MPC8313

[Scott Wood]

Ronald Madrid wrote:
> I don't know, where would I find that out?
> 
> Sorry, I'm still kind of new to this.

In the documentation/schematics/designer's-head of your custom board.

-Scott

RE: ifconfig MPC8313

[Ronald Madrid]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

I believe that it is zero.  Is that valid?

Ron

> Date: Tue, 6 May 2008 16:43:57 -0500
> From: scottwood@freescale.com
> To: ron_madrid@hotmail.com
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
> 
> Ronald Madrid wrote:
> > I don't know, where would I find that out?
> > 
> > Sorry, I'm still kind of new to this.
> 
> In the documentation/schematics/designer's-head of your custom board.
> 
> -Scott

_________________________________________________________________
With Windows Live for mobile, your contacts travel with you.
http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008

[-- Attachment #2: Type: text/html, Size: 984 bytes --]

Re: ifconfig MPC8313

[Scott Wood]

Ronald Madrid wrote:
> I believe that it is zero.  Is that valid?

FWIH, it's not recommended, as it's interpreted as a broadcast address 
in some cases.  However, if that's the way the board is, then go ahead 
and put a zero in the phy node's reg property.

-Scott

RE: ifconfig MPC8313

[Ronald Madrid]

[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]

Thank you, that seems to have worked.  I can now ping and whatnot.  One question though.  I used the linux v2.6.20 that came with the BSP for the MPC8313ERDB and the ethernet worked.  Was there a bug earlier that would have allowed this default .dts to work with my phy address of '0'?  I was rather baffled with this problem as the two dts files seemed to be more or less functionally identical (2.6.20 from BSP vs. 2.6.25)

Ron

> Date: Tue, 6 May 2008 17:04:21 -0500
> From: scottwood@freescale.com
> To: ron_madrid@hotmail.com
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
> 
> Ronald Madrid wrote:
> > I believe that it is zero.  Is that valid?
> 
> FWIH, it's not recommended, as it's interpreted as a broadcast address 
> in some cases.  However, if that's the way the board is, then go ahead 
> and put a zero in the phy node's reg property.
> 
> -Scott

_________________________________________________________________
Make Windows Vista more reliable and secure with Windows Vista Service Pack 1.
http://www.windowsvista.com/SP1?WT.mc_id=hotmailvistasp1banner

[-- Attachment #2: Type: text/html, Size: 1444 bytes --]