mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Kamel BOUHARA <k.bouhara@gmail.com>
To: barebox@lists.infradead.org
Subject: Network Issue with Mini2440
Date: Fri, 23 Mar 2012 01:53:33 +0100	[thread overview]
Message-ID: <CAM9uW_6qLEEmNFtTxLxNHx86zzFnHRfxB+1pm+VfRfjf4FrfBg@mail.gmail.com> (raw)


[-- 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

             reply	other threads:[~2012-03-23  0:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  0:53 Kamel BOUHARA [this message]
2012-03-23  8:22 ` Juergen Beisert
2012-03-23 18:17   ` Fwd: " Kamel BOUHARA
2012-03-24  7:35     ` Kamel BOUHARA
2012-03-24  8:50       ` Juergen Beisert
2012-03-25  5:55       ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-24  8:50     ` Fwd: " Juergen Beisert

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=CAM9uW_6qLEEmNFtTxLxNHx86zzFnHRfxB+1pm+VfRfjf4FrfBg@mail.gmail.com \
    --to=k.bouhara@gmail.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