If you haven't figured out your problem yet, maybe you can give us more info to help solve your problem.
Which platform are you using? Is this an in house HAL? Which ethernet driver(s) are you using? Most drivers have debug messages. Try looking in the source code to figure out what macro you have to define to turn them on. Which TCP/IP stack are you using? What is your definition of doesn't work ( i.e. can't ping target while running RedBoot, can't ping from RedBoot, can't ping while running eCos application, etc.)? Are you using the latest sources from CVS? Mike On 5/4/07, dogu cetin <[EMAIL PROTECTED]> wrote:
Hi, We have our own board which has two ethernet ports. If I configure ecos to use only eth0, it works. Similarly it works for eth1. However if I configure ecos to use both eth0 and eth1 at the same time. I can access the board via eth1 only. IP settings of interfaces are given below. Why doesn't eth0 and eth1 work together? is there any idea? Thanks, Dogu eth0: ip: 192.168.1.22 subnet: 255.255.255.0 broadcast: 192.168.1.255 gateway: 192.168.1.1 server ip: 192.168.1.1 eth0 is connected to local network eth1: ip: 140.120.1.22 subnet: 255.255.0.0 broadcast: 140.120.1.255 gateway: 140.120.1.1 server ip: 140.120.1.1 eth1 is connected to another PC via cross cable _________________________________________________________________ Hava durumunu bizden ögrenin ve evden öyle çikin! http://www.msn.com.tr/havadurumu/ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
-- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
