Network Issue with Mini2440

Network Issue with Mini2440

[Kamel BOUHARA]

[-- Attachment #1.1: Type: text/plain, Size: 3902 bytes --]

Hello,

I'm trying to port the last release of barebox to my sbc2440-III board with
the base config. of a mini2440 but unfortunately I'm facing a network issue
when trying to boot from nfs or to load files with tftp.

After checking all the parameters (pll, ram init etc.) I figured out that
the chip select and interrupt pinout were not good and I changed them to
fit with my board schematic.
So I have a well boot on barebox everything seems to work as you can see
here :

barebox 2012.03.0-00113-g881d9e9-dirty (Mar 23 2012 - 00:45:52)


> Board: Mini 2440

registered netconsole as cs1

NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
> 8-bit)

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

dm9000@dm90000: Found DM9000A at i/o: 0x18000300

refclk:    12000 kHz

mpll:     405000 kHz

upll:      48000 kHz

fclk:     405000 kHz

hclk:     101250 kHz

pclk:      50625 kHz

SDRAM1:   CL2@101MHz

Malloc space: 0x33a00000 -> 0x33dfffff (size  4 MB)

Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)

running /env/bin/init...



But,  when I try to ping or boot from nfs/tftp, the phy isn't receiving any
packet from host :

Hit any key to stop autoboot:  0

warning: No MAC address set. Using random address F6:48:4B:C2:51:44

phy0: Link is up - 100/Full

T T T T T T T T T T T T T T T T T T T T T T


I'm sure the host is well configured because I usually have to work with
other boards using nfs and tftp.

Here is more complete log of the packets transaction I hope it could help :

barebox 2012.03.0-00113-g881d9e9-dirty (Mar 23 2012 - 00:45:52)


> Board: Mini 2440

registered netconsole as cs1

NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
> 8-bit)

Bad block table found at page 65472, version 0x01

Bad block table found at page 65408, version 0x01

dm9000@dm90000: dm9k_reset

dm9000@dm90000: dm9000 revision 0x19

dm9000@dm90000: Found DM9000A at i/o: 0x18000300

dm9000@dm90000: 16 bit data bus

dm9000@dm90000: phy_write(reg:0, value:32768)

dm9000@dm90000: phy_read(4): 481

dm9000@dm90000: phy_write(reg:4, value:481)

dm9000@dm90000: phy_write(reg:0, value:4608)

refclk:    12000 kHz

mpll:     405000 kHz

upll:      48000 kHz

fclk:     405000 kHz

hclk:     101250 kHz

pclk:      50625 kHz

SDRAM1:   CL2@101MHz

Malloc space: 0x33a00000 -> 0x33dfffff (size  4 MB)

Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)

running /env/bin/init...


> Hit any key to stop autoboot:  1

warning: No MAC address set. Using random address 36:CF:EC:0D:18:BC

dm9000@dm90000: phy_read(1): 30825

dm9000@dm90000: phy_read(1): 30829

dm9000@dm90000: phy_read(1): 30829

dm9000@dm90000: phy_read(0): 12544

dm9000@dm90000: phy_read(5): 50657

phy0: Link is up - 100/Full

dm9000@dm90000: dm9k_eth_send: 42 bytes

dm9000@dm90000: transmit done

dm9000@dm90000: Packet present

dm9000@dm90000: dm9k_validate_entry packet status 01

dm9000@dm90000: rx Late Collision Seen error

dm9000@dm90000: rx length too big

dm9000@dm90000: dm9k_reset

T dm9000@dm90000: dm9k_eth_send: 42 bytes

dm9000@dm90000: transmit done

dm9000@dm90000: Packet present

dm9000@dm90000: dm9k_validate_entry packet status 01

dm9000@dm90000: rx fifo overflow error

dm9000@dm90000: rx crc error

dm9000@dm90000: Discarding packet

dm9000@dm90000: dm9k_validate_entry packet status 00

T dm9000@dm90000: dm9k_eth_send: 42 bytes

dm9000@dm90000: transmit done

dm9000@dm90000: Packet present

dm9000@dm90000: dm9k_validate_entry packet status 00

T dm9000@dm90000: dm9k_eth_send: 42 bytes

dm9000@dm90000: transmit done

dm9000@dm90000: Packet present

dm9000@dm90000: dm9k_validate_entry packet status 00

NFS failed: Interrupted system call


Any help is welcome for sure.

Regards.
-- 

_______________________________
*Kamel BOUHARA*
62 Bis Rue Carnot
60610 Lacroix Saint-Ouen

Tel :  +33617832904

[-- Attachment #1.2: Type: text/html, Size: 22339 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Network Issue with Mini2440

[Juergen Beisert]

Hi Kamel,

Kamel BOUHARA wrote:
> I'm trying to port the last release of barebox to my sbc2440-III board with
> the base config. of a mini2440 but unfortunately I'm facing a network issue
> when trying to boot from nfs or to load files with tftp.
>
> After checking all the parameters (pll, ram init etc.) I figured out that
> the chip select and interrupt pinout were not good and I changed them to
> fit with my board schematic.
> So I have a well boot on barebox everything seems to work as you can see
> here :
> [...]

I changes the DM9000 driver recently. So, I tested both DM9000 revisions I
have access to (based on the Barebox's next branch).

First on the Mini2440. It comes with a DM9000E:

---------------------------------------------------------------------------

mini2440:/ tftp barebox-mini2440 /dev/ram0
TFTP from server 192.168.1.7 ('barebox-mini2440' -> '/dev/ram0')
        #################################
mini2440:/ go /dev/ram0
## Starting application at 0x30000000 ...

barebox 2012.02.0-00259-g773e35b (Mar 23 2012 - 08:53:16)

Board: Mini 2440
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x019e0000
nand_read_bbt: Bad block at 0x02540000
dm9000@dm90000: Found DM9000E at i/o: 0x20000300
s3c_mci@mci0: registered as mci0
refclk:    12000 kHz
mpll:     405000 kHz
upll:      48000 kHz
fclk:     405000 kHz
hclk:     101250 kHz
pclk:      50625 kHz
SDRAM1:   CL2@101MHz
Malloc space: 0x33a00000 -> 0x33dfffff (size  4 MB)
Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)
envfs: wrong magic on /dev/env0
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  3
mini2440:/ devinfo eth0
resources:
driver: none

Parameters:
          ipaddr = 192.168.1.241
         ethaddr = 36:CF:EC:0D:18:Bd
         gateway = <NULL>
         netmask = 255.255.255.0
        serverip = 192.168.1.7
mini2440:/ ping 192.168.1.7
phy0: Link is up - 100/Full
host 192.168.1.7 is alive

---------------------------------------------------------------------------

And here with my Mini6410. This comes with a DM9000A like your system.

---------------------------------------------------------------------------

barebox 2012.02.0-00259-g773e35b-dirty (Mar 23 2012 - 09:19:48)

Board: Mini 6410
Will write 0x00021300
dm9000@dm90000: Found DM9000A at i/o: 0x18000300
eth@eth0: got MAC address from EEPROM: 08:90:90:90:90:90
refclk:    12000 kHz
apll:     532000 kHz
mpll:     532000 kHz
CPU:      532000 kHz
hclkx2:   266000 kHz
hclk:     133000 kHz
pclk:      66500 kHz
Malloc space: 0x57bc0000 -> 0x57fbffff (size  4 MB)
Stack space : 0x57bb8000 -> 0x57bc0000 (size 32 kB)
Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  3
mini6410:/ devinfo eth0
resources:
driver: none

Parameters:
          ipaddr = 192.168.1.187
         ethaddr = 08:90:90:90:90:90
         gateway = 192.168.1.1
         netmask = 255.255.255.0
        serverip = 192.168.1.7
mini6410:/ ping 192.168.1.7
phy0: Link is up - 100/Full
host 192.168.1.7 is alive

---------------------------------------------------------------------------

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Fwd: Network Issue with Mini2440

[Kamel BOUHARA]

[-- Attachment #1.1: Type: text/plain, Size: 4302 bytes --]

Hi Juergen,

Ok, it light me on the way that my board don't use an eeprom to set the FEC
address so I probably have to fix that somewhere ...maybe a macro #define
NO_EEPROM or something like that ??

Can you, please, show me the *md -s /dev/phy0* command output from you
mini6410.

Thanks.

---------- Message transféré ----------
De : Juergen Beisert <jbe@pengutronix.de>
Date : 23 mars 2012 09:22
Objet : Re: Network Issue with Mini2440
À : barebox@lists.infradead.org
Cc : Kamel BOUHARA <k.bouhara@gmail.com>


Hi Kamel,

Kamel BOUHARA wrote:
> I'm trying to port the last release of barebox to my sbc2440-III board
with
> the base config. of a mini2440 but unfortunately I'm facing a network
issue
> when trying to boot from nfs or to load files with tftp.
>
> After checking all the parameters (pll, ram init etc.) I figured out that
> the chip select and interrupt pinout were not good and I changed them to
> fit with my board schematic.
> So I have a well boot on barebox everything seems to work as you can see
> here :
> [...]

I changes the DM9000 driver recently. So, I tested both DM9000 revisions I
have access to (based on the Barebox's next branch).

First on the Mini2440. It comes with a DM9000E:

---------------------------------------------------------------------------

mini2440:/ tftp barebox-mini2440 /dev/ram0
TFTP from server 192.168.1.7 ('barebox-mini2440' -> '/dev/ram0')
       #################################
mini2440:/ go /dev/ram0
## Starting application at 0x30000000 ...

barebox 2012.02.0-00259-g773e35b (Mar 23 2012 - 08:53:16)

Board: Mini 2440
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V
8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x019e0000
nand_read_bbt: Bad block at 0x02540000
dm9000@dm90000: Found DM9000E at i/o: 0x20000300
s3c_mci@mci0: registered as mci0
refclk:    12000 kHz
mpll:     405000 kHz
upll:      48000 kHz
fclk:     405000 kHz
hclk:     101250 kHz
pclk:      50625 kHz
SDRAM1:   CL2@101MHz
Malloc space: 0x33a00000 -> 0x33dfffff (size  4 MB)
Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)
envfs: wrong magic on /dev/env0
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  3
mini2440:/ devinfo eth0
resources:
driver: none

Parameters:
         ipaddr = 192.168.1.241
        ethaddr = 36:CF:EC:0D:18:Bd
        gateway = <NULL>
        netmask = 255.255.255.0
       serverip = 192.168.1.7
mini2440:/ ping 192.168.1.7
phy0: Link is up - 100/Full
host 192.168.1.7 is alive

---------------------------------------------------------------------------

And here with my Mini6410. This comes with a DM9000A like your system.

---------------------------------------------------------------------------

barebox 2012.02.0-00259-g773e35b-dirty (Mar 23 2012 - 09:19:48)

Board: Mini 6410
Will write 0x00021300
dm9000@dm90000: Found DM9000A at i/o: 0x18000300
eth@eth0: got MAC address from EEPROM: 08:90:90:90:90:90
refclk:    12000 kHz
apll:     532000 kHz
mpll:     532000 kHz
CPU:      532000 kHz
hclkx2:   266000 kHz
hclk:     133000 kHz
pclk:      66500 kHz
Malloc space: 0x57bc0000 -> 0x57fbffff (size  4 MB)
Stack space : 0x57bb8000 -> 0x57bc0000 (size 32 kB)
Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  3
mini6410:/ devinfo eth0
resources:
driver: none

Parameters:
         ipaddr = 192.168.1.187
        ethaddr = 08:90:90:90:90:90
        gateway = 192.168.1.1
        netmask = 255.255.255.0
       serverip = 192.168.1.7
mini6410:/ ping 192.168.1.7
phy0: Link is up - 100/Full
host 192.168.1.7 is alive

---------------------------------------------------------------------------

Regards,
Juergen

--
Pengutronix e.K.                              | Juergen Beisert
|
Linux Solutions for Science and Industry      | http://www.pengutronix.de/ |



-- 

_______________________________
*Kamel BOUHARA*
62 Bis Rue Carnot
60610 Lacroix Saint-Ouen

Tel :  +33617832904

[-- Attachment #1.2: Type: text/html, Size: 5593 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Network Issue with Mini2440

[Kamel BOUHARA]

[-- Attachment #1.1: Type: text/plain, Size: 4951 bytes --]

Hello,

Sorry for the pm but I still wait the bellow message to be approved by the
mailing list admin and it seems he takes a week ;).

Can you please look at it.

Le 23 mars 2012 19:17, Kamel BOUHARA <k.bouhara@gmail.com> a écrit :

> Hi Juergen,
>
> Ok, it light me on the way that my board don't use an eeprom to set the
> FEC address so I probably have to fix that somewhere ...maybe a macro
> #define NO_EEPROM or something like that ??
>
> Can you, please, show me the *md -s /dev/phy0* command output from you
> mini6410.
>
> Thanks.
>
> ---------- Message transféré ----------
> De : Juergen Beisert <jbe@pengutronix.de>
> Date : 23 mars 2012 09:22
> Objet : Re: Network Issue with Mini2440
> À : barebox@lists.infradead.org
> Cc : Kamel BOUHARA <k.bouhara@gmail.com>
>
>
>
> Hi Kamel,
>
> Kamel BOUHARA wrote:
> > I'm trying to port the last release of barebox to my sbc2440-III board
> with
> > the base config. of a mini2440 but unfortunately I'm facing a network
> issue
> > when trying to boot from nfs or to load files with tftp.
> >
> > After checking all the parameters (pll, ram init etc.) I figured out that
> > the chip select and interrupt pinout were not good and I changed them to
> > fit with my board schematic.
> > So I have a well boot on barebox everything seems to work as you can see
> > here :
> > [...]
>
> I changes the DM9000 driver recently. So, I tested both DM9000 revisions I
> have access to (based on the Barebox's next branch).
>
> First on the Mini2440. It comes with a DM9000E:
>
> ---------------------------------------------------------------------------
>
> mini2440:/ tftp barebox-mini2440 /dev/ram0
> TFTP from server 192.168.1.7 ('barebox-mini2440' -> '/dev/ram0')
>        #################################
> mini2440:/ go /dev/ram0
> ## Starting application at 0x30000000 ...
>
> barebox 2012.02.0-00259-g773e35b (Mar 23 2012 - 08:53:16)
>
> Board: Mini 2440
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB
> 3,3V 8-bit)
> Bad block table found at page 65472, version 0x01
> Bad block table found at page 65408, version 0x01
> nand_read_bbt: Bad block at 0x019e0000
> nand_read_bbt: Bad block at 0x02540000
> dm9000@dm90000: Found DM9000E at i/o: 0x20000300
> s3c_mci@mci0: registered as mci0
> refclk:    12000 kHz
> mpll:     405000 kHz
> upll:      48000 kHz
> fclk:     405000 kHz
> hclk:     101250 kHz
> pclk:      50625 kHz
> SDRAM1:   CL2@101MHz
> Malloc space: 0x33a00000 -> 0x33dfffff (size  4 MB)
> Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)
> envfs: wrong magic on /dev/env0
> no valid environment found on /dev/env0. Using default environment
> running /env/bin/init...
>
> Hit any key to stop autoboot:  3
> mini2440:/ devinfo eth0
> resources:
> driver: none
>
> Parameters:
>          ipaddr = 192.168.1.241
>         ethaddr = 36:CF:EC:0D:18:Bd
>         gateway = <NULL>
>         netmask = 255.255.255.0
>        serverip = 192.168.1.7
> mini2440:/ ping 192.168.1.7
> phy0: Link is up - 100/Full
> host 192.168.1.7 is alive
>
> ---------------------------------------------------------------------------
>
> And here with my Mini6410. This comes with a DM9000A like your system.
>
> ---------------------------------------------------------------------------
>
> barebox 2012.02.0-00259-g773e35b-dirty (Mar 23 2012 - 09:19:48)
>
> Board: Mini 6410
> Will write 0x00021300
> dm9000@dm90000: Found DM9000A at i/o: 0x18000300
> eth@eth0: got MAC address from EEPROM: 08:90:90:90:90:90
> refclk:    12000 kHz
> apll:     532000 kHz
> mpll:     532000 kHz
> CPU:      532000 kHz
> hclkx2:   266000 kHz
> hclk:     133000 kHz
> pclk:      66500 kHz
> Malloc space: 0x57bc0000 -> 0x57fbffff (size  4 MB)
> Stack space : 0x57bb8000 -> 0x57bc0000 (size 32 kB)
> Open /dev/env0 No such file or directory
> no valid environment found on /dev/env0. Using default environment
> running /env/bin/init...
>
> Hit any key to stop autoboot:  3
> mini6410:/ devinfo eth0
> resources:
> driver: none
>
> Parameters:
>          ipaddr = 192.168.1.187
>         ethaddr = 08:90:90:90:90:90
>         gateway = 192.168.1.1
>         netmask = 255.255.255.0
>        serverip = 192.168.1.7
> mini6410:/ ping 192.168.1.7
> phy0: Link is up - 100/Full
> host 192.168.1.7 is alive
>
> ---------------------------------------------------------------------------
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K.                              | Juergen Beisert
>   |
> Linux Solutions for Science and Industry      | http://www.pengutronix.de/ |
>
>
>
> --
>
> _______________________________
> *Kamel BOUHARA*
> 62 Bis Rue Carnot
> 60610 Lacroix Saint-Ouen
>
> Tel :  +33617832904
>
>
>


-- 

_______________________________
*Kamel BOUHARA*
62 Bis Rue Carnot
60610 Lacroix Saint-Ouen

Tel :  +33617832904

[-- Attachment #1.2: Type: text/html, Size: 6548 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Fwd: Network Issue with Mini2440

[Juergen Beisert]

Hi Kamel,

Kamel BOUHARA wrote:
> Ok, it light me on the way that my board don't use an eeprom to set the FEC
> address so I probably have to fix that somewhere ...maybe a macro #define
> NO_EEPROM or something like that ??

You do not need an EEPROM for the MAC address. Setting a random one should do 
the trick. The Mini6410 also has no EEPROM. The message is a little bit 
confusing. It only shows the already set MAC address in the DM9000.

> Can you, please, show me the *md -s /dev/phy0* command output from you
> mini6410.

mini6410:/ md -s /dev/phy0
00000000: 78693100 b8a00181 45e101e1 00000003                .1ix.......E....
00000010: 00000000 00000000 00000000 00000000                ................
00000020: 80180414 00007800 00000080 00000000                .....x..........
00000030: 000004e1 00000000 00000000 00000000                ................

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Network Issue with Mini2440

[Juergen Beisert]

Kamel BOUHARA wrote:
> Sorry for the pm but I still wait the bellow message to be approved by the
> mailing list admin and it seems he takes a week ;).
>
> Can you please look at it.

Done.

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Network Issue with Mini2440

[Jean-Christophe PLAGNIOL-VILLARD]

On 08:35 Sat 24 Mar     , Kamel BOUHARA wrote:
>    Hello,
>    Sorry for the pm but I still wait the bellow message to be approved by the
>    mailing list admin and it seems he takes a week ;). 
stop to post in HTML please so we do not have to ack your message everytime

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox