Re: [ECOS] problems in sending and receiving packets

[Nick Garnett <nickg at ecoscentric dot com>]

"mohanlal jangir" <mohanlaljangir@hotmail.com> writes:

> I have been facing problems in sending and receiving packets with eCos. I
> have booted one Intelx86 machine with RedBoot. At RedBoot prompt, I executed
> following command:
> ip_address -l 10.10.3.64
> After this if I ping to above address from some machine, I do receive echo
> replies. Later I load the eCos image with one application using
> i386-elf-gdb(from another Intelx86 machine) and executed follwing command at
> gdb prompt:
> target remote 10.10.3.64:9000
> then I load the image using *load* command at gdb prompt. Interface
> initialisation goes fine. But the application fails to bind to address
> 10.10.3.64
> When I ping to 10.10.3.64 from some other machine, I receive echo reply. I
> am wondering, who is replying? eCos or RedBoot !!! Even if I try to send any
> packet using ether_output_frame, where I build entire packet including
> ethernet header, packet is  not going out. I am able to get a valid pointer
> through function ifunit for eth0. I am not able to receive any packets
> either. I am purplexed what is happening. Can somebody explain this? Thanks
> in advance.
> 

RedBoot and eCos cannot use the same IP address. To allow you to debug
eCos apps over the network, incoming packets are sorted in the low
level drivers and passed either to eCos or RedBoot. It uses the
destination IP address for this.

My usual approach is to let RedBoot acquire its address via DHCP and
to configure eCos with a statically bound address.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss