MPC8548CDS unable to ping successfully

cancel
Showing results for 
Search instead for 
Did you mean: 

MPC8548CDS unable to ping successfully

3,309 Views
thoms52
Contributor I

I am unable to ping from U-Boot or from the Linux kernel on the MPC8548CDS, and pings from other nodes are not responded from the MPC8548CDS.

I attached to different switches and also connected using the crossover cable .. but no luck. When I ping within U-BOOT the system just hangs and I have to hit the reset button. When I ping within the booted Linux I get timeouts. 

Within u-boot I used setenv ipaddr and setenv netmask

 commands to configure network. What can I do to get ping to work properly?

 

Regards,

Carl

Labels (1)
0 Kudos
5 Replies

438 Views
DistiCasMgr
NXP Employee
NXP Employee
Carl,
 
I was wondering whether it may be a firewall issue. Are you using Windows standard firewall? I don't use that (FSl use BlackICE) and this allows individual ports to be allowed/denied.
 
Damian
0 Kudos

438 Views
thoms52
Contributor I

I am using the standard XP professional security center firewall.

Magically, I can ping the Windows host now.... after I rebooted everything...

~carl

0 Kudos

438 Views
DistiCasMgr
NXP Employee
NXP Employee
Carl,
 
My CDS system is out with a customer but from memory I recall that by default the Linux image shipped on the board will only work with one of the 4 ethernet sockets on the card. I honestly cannot recall which one, but its worth trying all 4 as a quick test.
 
Also as the kernel boots up what does it say whe it initialises eth0? You should see some status messages.
 
What does an ifconfig show once the kernel is booted.
 
Thanks
 
Damian
0 Kudos

438 Views
thoms52
Contributor I

Damian,

Yes ETH0 seems to be the port to use, it is the top most port above the serial interface.

When Linux comes up and the cable is attached ETH0 comes up ...

The output from ifconfig is ...


eth0      Link encap:Ethernet  HWaddr 00:E0:0C:00:00:FD 
         inet addr:192.168.0.254  Bcast:192.168.0.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:100 errors:0 dropped:0 overruns:0 frame:0
         TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:11440 (11.1 KiB)  TX bytes:1624 (1.5 KiB)

lo        Link encap:Local Loopback 
         inet addr:127.0.0.1  Mask:255.0.0.0
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:4 errors:0 dropped:0 overruns:0 frame:0
         TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:372 (372.0 B)  TX bytes:372 (372.0 B)

I have a crossover cable to a windows host at  IP = 192.168.0.5 , Netmask = 255.255.255.0

On Linux when I ping 192.168.0.5 I get no reply ...

On Windows I ping 192.168.0.254 and I do get reply ....so one side works!

~carl

 

0 Kudos

438 Views
thoms52
Contributor I
It is my problem..
 
I can ping both directions if I connect to a Linux system. Despite the firewall being off, the Windows host is dropping the ping.
 
Thanks for the help,
 
~carl
0 Kudos