public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Ethernet not found on Arria 5.
Date: Thu, 10 Mar 2016 01:25:20 +0100	[thread overview]
Message-ID: <56E0BEF0.5070906@denx.de> (raw)
In-Reply-To: <56E0983D.6090304@opensource.altera.com>

On 03/09/2016 10:40 PM, Dinh Nguyen wrote:
> On 03/09/2016 08:00 AM, Bakhvalov, Denis (Nokia - PL/Wroclaw) wrote:
>> Hi Marek,
>>
>>> Perform usual test, disable cache (dcache off) .
>>
>> I tried and result is still the same.
>>
>> UPD: I did a little trick:
>> 1. I started ping from the board side. That made the board listen to incoming packets (calling in infinite loop eth_rx() ).
>> 2. Started ping from PC side.
>> 3. In this case board receive ICMP packets from PC:
>>
>> packet received
>> Receive from protocol 0x800
>> Got IP
>> len=60, v=45
>> Got ICMP ECHO REQUEST, return 74 bytes 
>>
>> So, ICMP packets are handled by the board, but ARP packets not.
>>
>> In my understanding it tells me that at least interface on the board side is alive.
>>
>> I'm now doing some low-level debugging, however I think this is not the best idea. :)
>> Now dw_eth_recv (designware.c) always returns 0 length of the packet.
>>
> 
> I was able to tftp an kernel image using mainline U-Boot on my Arria5
> board today. However, I wasn't able to dhcp, but I'm not sure if that's
> the board or my network.
> 
> 
> U-Boot 2016.03-rc3-00008-g08b2472 (Mar 09 2016 - 13:37:27 -0600)
> 
> CPU:   Altera SoCFPGA Platform
> FPGA:  Altera Arria V, D5, version 0x0
> BOOT:  SD/MMC External Transceiver (1.8V)
>        Watchdog enabled
> I2C:   ready
> DRAM:  1 GiB
> MMC:   dwmmc0 at ff704000: 0
> In:    serial
> Out:   serial
> Err:   serial
> Model: Altera SOCFPGA Arria V SoC Development Kit
> Net:   eth0: ethernet at ff702000
> Hit any key to stop autoboot:  0
> => tftp ${loadaddr} zImage
> Speed: 1000, full duplex
> Using ethernet at ff702000 device
> TFTP from server 137.57.160.210; our IP address is 137.57.160.216
> Filename 'zImage'.
> Load address: 0x8000
> Loading:
>          #################################
>          552.7 KiB/s
> done
> Bytes transferred = 3491984 (354890 hex)
> =>

Thanks for the test!

The speed looks weird, it should be in the 2-3MiB range.

Are you booting using mainline U-Boot SPL ? :-)

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-03-10  0:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  9:20 [U-Boot] Ethernet not found on Arria 5 Bakhvalov, Denis
2016-03-04 12:30 ` Marek Vasut
2016-03-04 12:53   ` Bakhvalov, Denis
2016-03-05 12:36     ` Marek Vasut
2016-03-08  9:58       ` Bakhvalov, Denis
2016-03-09  9:22       ` Bakhvalov, Denis
2016-03-09 13:47         ` Marek Vasut
2016-03-09 14:00           ` Bakhvalov, Denis
2016-03-09 21:40             ` Dinh Nguyen
2016-03-10  0:25               ` Marek Vasut [this message]
2016-03-10  8:58                 ` Bakhvalov, Denis
2016-03-10 12:43                   ` Marek Vasut
2016-03-10 17:19                     ` Bakhvalov, Denis
2016-03-21  8:16                     ` Bakhvalov, Denis
2016-03-21 11:18                       ` Marek Vasut
2016-03-21 12:34                         ` Bakhvalov, Denis
2016-03-21 12:39                           ` Marek Vasut
2016-03-10 14:16                 ` Dinh Nguyen
2016-03-21  8:30       ` Bakhvalov, Denis

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=56E0BEF0.5070906@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /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