mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Ethernet does not work in EFM32 Giant Gecko
Date: Thu, 27 Jun 2013 09:38:27 +0200	[thread overview]
Message-ID: <20130627073827.GD27010@pengutronix.de> (raw)
In-Reply-To: <CADe7rRcNtYfGXapVfHxh9=je19tsox0ih7V+t3LAw=04_M2CrA@mail.gmail.com>

Hello Joey,

On Thu, Jun 27, 2013 at 02:51:18PM +0800, Jinyun Ye wrote:
> I'm trying to enable network on my EFM32 Giant Gecko (FPGA version
> 0v1p1b148), but failed. Here is what I did:
> 
> 1. Downgraded to board firmware 0v9p9b909
not sure this is necessary. Anyhow, this is the version I do use, too.

> 2. Enabled ping and route in busybox
> 3. Built, burnt and boot uclinux successfully
> 4. ping local eth0 but doesn't work:
I assume you're using the BSP from
http://git-public.pengutronix.de/?p=OSELAS.BSP-EnergyMicro-Gecko.git?

> / # /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr D6:C5:6F:EC:7B:F1
>           inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>           Interrupt:4
> / # ping 192.168.0.100
> No response from 192.168.0.100
> / # /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr D6:C5:6F:EC:7B:F1
>           inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>           Interrupt:4
> 
> Please share me some hint, if anyone have succeeded before.
Full kernel log and the content of /proc/interrupts between all steps
would be interesting.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-06-27  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  6:51 Jinyun Ye
2013-06-27  7:38 ` Uwe Kleine-König [this message]
2013-06-27  9:46   ` Jinyun Ye
2013-06-27  9:53     ` Marc Kleine-Budde
2013-06-27 20:10     ` Uwe Kleine-König
2013-06-28  1:05       ` Jinyun Ye
2013-07-16 21:20       ` Uwe Kleine-König

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=20130627073827.GD27010@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ptxdist@pengutronix.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