u-boot, MPC8313erdb

u-boot, MPC8313erdb

[Nidhi Dua]

[-- 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: 3350 bytes --]

Re: u-boot, MPC8313erdb

[Scott Wood]

Nidhi Dua wrote:
> 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?

U-boot does not support responding to pings.

Also, please use the u-boot-users list for u-boot questions, use a more 
descriptive subject, and don't repost the same question multiple times.

-Scott

RE: u-boot, MPC8313erdb

[Mike Timmons]

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

The environment variable ethact does not, "stick" for me either,
although it's not an issue for me. Look in eth.c to learn when/how it is
initialized. Note the CONFIG_NET_MULTI constant (I have it defined, but
I'm not sure why).

 

I bet you have that defined in your board header file. Take a look and
see if you can get your custom ethact to stick by defining or undefining
that or something.

 

-Mike

 

________________________________

From: linuxppc-embedded-bounces+mike_timmons=trimble.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+mike_timmons=trimble.com@ozlabs.org]
On Behalf Of Nidhi Dua
Sent: Friday, June 20, 2008 9:53 AM
To: linuxppc-embedded@ozlabs.org
Subject: u-boot, MPC8313erdb

 

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 <http://192.168.1.101/> 
serverip=192.168.1.57 <http://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 <http://192.168.1.101/> 
serverip=192.168.1.57 <http://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 <http://192.168.1.101/>  (192.168.1.101
<http://192.168.1.101/> ) 56(84) bytes of data.
>From 192.168.1.57 <http://192.168.1.57/>  icmp_seq=2 Destination Host
Unreachable
>From 192.168.1.57 <http://192.168.1.57/>  icmp_seq=3 Destination Host
Unreachable
....
....
--- 192.168.1.101 <http://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: 7354 bytes --]