linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* mpc8313erdb
@ 2008-06-20 10:42 Nidhi Dua
  2008-06-20 11:24 ` mpc8313erdb Marco Stornelli
  0 siblings, 1 reply; 4+ messages in thread
From: Nidhi Dua @ 2008-06-20 10:42 UTC (permalink / raw)
  To: linuxppc-embedded

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

We are using the board MPC8313ERDB and we are facing problems regarding
u-boot environment variables(the environment variables displayed after
giving 'printenv' command at u-boot prompt).

We are following the steps stated as below:

1. =>printenv

output is:
....
....
bootargs=root=/dev/mtdblock2 rootfstype=jffs2 rw console=ttyS0,115200
bootcmd=bootm fe100000 - fe700000
filesize=1a4a05
fileaddr=200000
ipaddr=192.168.1.101
serverip=192.168.1.57
stdin=serial
stdout=serial
stderr=serial
ethact=TSEC0


Here ethact is TSEC0 by default.

2. =>setenv ethact TSEC1
3. =>saveenv
output:
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors

Here we have set the ethact variable to TSEC1 and saved it. Now it is
showing that this value of ethact is burnt in flash. But after the board is
reset,

4. =>printenv

ileaddr=200000
ipaddr=192.168.1.101
serverip=192.168.1.57
stdin=serial
stdout=serial
stderr=serial
ethact=TSEC0

Here again the value of ethact is changed to TSEC0.

we have following questions:

question 1: We want to know the reason why it(ethact variable) changes to
TSEC0 everytime with a reset.

question2: After we have set ethact to TSEC1 and saved it(=>saveenv) and
tried to ping the Host from u-boot prompt it is working (displaying: 'host
alive').
But when we are trying to ping Target board from the host it is showing:

PING 192.168.1.101 (192.168.1.101) 56(84) bytes of data.
>From 192.168.1.57 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.57 icmp_seq=3 Destination Host Unreachable
....
....
--- 192.168.1.101 ping statistics ---
12 packets transmitted, 0 received, +9 errors, 100% packet loss, time
11002ms
, pipe 3

Why is it happening so?

question 3: After we have set 'ethact' to TSEC1, the kernel is loaded, and
we have logged -in, when we try to ping the Host from target it says '100%
packet lost'. also we are unable to ping target from the host. Why is it
happening so?

Awaiting a prompt reply
Regards
Nidhi Dua

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

^ permalink raw reply	[flat|nested] 4+ messages in thread
[parent not found: <d8b992c20806200757l73f09a22jf9fbd7200ef60268@mail.gmail.com>]
[parent not found: <mailman.2509.1213973560.4744.linuxppc-embedded@ozlabs.org>]

end of thread, other threads:[~2008-06-20 16:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-20 10:42 mpc8313erdb Nidhi Dua
2008-06-20 11:24 ` mpc8313erdb Marco Stornelli
     [not found] <d8b992c20806200757l73f09a22jf9fbd7200ef60268@mail.gmail.com>
2008-06-20 15:02 ` mpc8313erdb Nidhi Dua
     [not found] <mailman.2509.1213973560.4744.linuxppc-embedded@ozlabs.org>
2008-06-20 16:43 ` mpc8313erdb Carlos Roberto Moratelli

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).