This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Ping problem ? (edb7209 with ep7212)


Hi:


>From: Jonathan Larmour <jlarmour@redhat.com>
>To: Shulin Cui <cuishulin@hotmail.com>
>CC: ecos-discuss@sources.redhat.com
>Subject: Re: [ECOS] Ping problem ? (edb7209 with ep7212)
>Date: Thu, 10 Jan 2002 21:06:47 +0000
>
>Shulin Cui wrote:
> >
> > Hi,All:
> >         It seems not work!
> >
> >         Cirrus Logic EDB7209 with EP7212,
> >         Windows me + cygwin +gnupro tools,
> >         configurature tools version 2.08,
> >         gdb stub,
> >         ecos 2002-01-08 updated.
> >
> >         I selected the board and the net template,followed with building 
>and
> >         no problem found.
> > 1.      I started a application with gdb.When It runs step to "do_dhcp" 
>in
> > fuction
> >          "init_all_network_interfaces", it could not back to gdb.I do 
>not know Why?
>
>Are you debugging over the network as well? Or over serial?
>
     I debuged the board with gdb over serial 1, I have been attempted to 
use the redboot, it said This to serial 1:

+FLASH: 0xe0000000 - 0xe1000000, 128 blocks of 0x00020000 bytes each.
FLASH configuration checksum error or invalid key
Can't get BOOTP info - network disabled!

RedBoot(tm) bootstrap and debug environment - built 07:02:14, May  1 2001

Platform: Cirrus Logic EDB7212 (ARM 720T)
Copyright (C) 2000, 2001, Red Hat, Inc.

RAM: 0x00000000-0x00fd7000, 0x00009820-0x00fa7000 available
RedBoot>

>I have sometimes seen instances where GDB or the GDB stub has not placed
>the next breakpoint (used for the stepping) in the right place. If your
>program just continues rather than stops dead that may be what it is, and
>to fix it requires you to debug it.
>
> > 2.      I change the
> >         networking->initialization options for 'eth0'->use BOOTP/DHCP...
> >         to
> >         networking->initialization options for 'eth0'->Address setups 
>'for eth0'
> >                 IP address:192.168.1.2
> >                 Network mask:255.255.255.0
> >                 Broadcast address:192.168.1.255
> >                 router IP:192.168.1.1
> >                 server IP:192.168.1.101
> >         then I build the test program ping_test.c and ping_lo_test.c
>
>Okay... assuming you had a reason to do this.
>
> > 3.      When it pings the 192.168.1.2 the ping_test.c run fine
> >         When it pings the server 192.168.1.101,it gave me message:
> >
> >       Message from "init_all_network_interfaces":
> >
> >         Start PING test
> >                 BOOTP[eth0] op: REPLY
>
>You got a bootp reply even though you told it not to use bootp? Are you
>sure you saved the configuration and rebuilt both eCos and the test?
>
> >                         htype: Ethernet
> >                         hlen: 6
> >                         hops: 0
> >                         xid: 0x0
> >                         secs: 0
> >                         flags: 0x0
> >                         hw_addr: FF:FF:FF:FF:FF:FF
>
>Hmm.....
>
I always confused with  the hw_addr value, because I knew that the board had 
an
EEPROM belonged to c46.
> >                 Client IP: 192.168.1.2
> >                 my IP: 192.168.1.2
> >                 server IP: 192.168.1.101
> >                 gateway IP: 192.168.1.1
> >                 options:
> >                         subnet mask: 255.255.255.0
> >             IP broadcast:192.168.1.255
> >                         gateway:192.168.1.1
> >
> >         Message from "ping_host(s,&host)":
> >
> >                 PING server 192.168.1.101
> >                 192.168.1.2: Invalid ICMP - type: 8
> >                 192.168.1.2: Invalid ICMP - type: 8
>
>This is the ICMP code for echo, not echo reply.
>
>I thought the BOOTP debug output was meant to display the local address,
>i.e. not FF:FF:FF:FF:FF:FF:FF. Do you know if your board has a serial
>EEPROM for the ESA? If not, you will need to set a MAC address for the
>board in the eth driver config.
>
>Does ping_lo_test work?
>
I did the ping_lo_test, it work fine.

>Jifl
>--
>Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
>Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]