* [ECOS] network test problem on ipaq @ 2001-07-01 3:07 Weilong Li 2001-07-01 8:46 ` Jonathan Larmour 2001-07-01 19:41 ` Gary Thomas 0 siblings, 2 replies; 11+ messages in thread From: Weilong Li @ 2001-07-01 3:07 UTC (permalink / raw) To: ecos-discuss I try to run tcp_echo, tcp_source and tcp_sink program on ipaq. From linux host, I used serial port to connect ipaq, then I used gdb to remotely run tcp_echo, after tcp_echo is running, and I run tcp_source and tcp_sink, but I got "no route to host" message. And I cannot ping ipaq. While before I run tcp_echo, I can ping ipaq, and tcp_source and tcp_sink can successfully run and waiting for packets. But I cannot run tcp_echo through gdb, it simply cannot load the program. So it seems there are conflicts even I used serial port to run tcp_echo, and used ethernet interface to run tcp_sink and tcp_source. Please help. thanks, Weilong __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-01 3:07 [ECOS] network test problem on ipaq Weilong Li @ 2001-07-01 8:46 ` Jonathan Larmour 2001-07-01 12:34 ` Weilong Li 2001-07-01 19:41 ` Gary Thomas 1 sibling, 1 reply; 11+ messages in thread From: Jonathan Larmour @ 2001-07-01 8:46 UTC (permalink / raw) To: Weilong Li; +Cc: ecos-discuss Weilong Li wrote: > > I try to run tcp_echo, tcp_source and tcp_sink > program on ipaq. > > >From linux host, I used serial port to connect > ipaq, then I used gdb to remotely run tcp_echo, after > tcp_echo is running, and I run tcp_source and > tcp_sink, but I got "no route to host" message. > And I cannot ping ipaq. > > While before I run tcp_echo, I can ping ipaq, and > tcp_source and tcp_sink can successfully run and > waiting for packets. But I cannot run tcp_echo > through gdb, it simply cannot load the program. You cannot even load it? Do you get any output from GDB? 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 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-01 8:46 ` Jonathan Larmour @ 2001-07-01 12:34 ` Weilong Li 2001-07-02 11:45 ` Jonathan Larmour 0 siblings, 1 reply; 11+ messages in thread From: Weilong Li @ 2001-07-01 12:34 UTC (permalink / raw) To: Jonathan Larmour; +Cc: ecos-discuss The ip adddress of ipaq is 192.168.1.20. After redboot boots on ipaq, I issued tcp_source and tcp_sink command to target on my redhat host. # ./ecos/packages/net/tcpip/current/tests/tcp_sink 192.168.1.20 Start TCP test - SINK mode to 192.168.1.20 At another terminal: # ./ecos/packages/net/tcpip/current/tests/tcp_source 192.168.1.20 Start TCP test - SOURCE mode to 192.168.1.20 And I pinged 192.168.1.20, and I got response. Then I issued gdb command on tcp_echo. This time it can load, while immediately after I type "continue", and tcp_echo is running, tcp_sink and tcp_source will report "no route to 192.168.1.20", and I cannot ping ipaq from linux host. Here is the screen. #arm-elf-gdb ./ipaq/install/tests/net/tcpip/current/tests/tcp_echo GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"... (gdb) set remotebaud 38400 (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 0x50046f30 in ?? () (gdb) load Loading section .rom_vectors, size 0x40 lma 0x20000 Loading section .text, size 0x2ec2c lma 0x20040 Loading section .rodata, size 0x1d18 lma 0x4ec6c Loading section .data, size 0xc3c lma 0x50984 Start address 0x20040 , load size 202176 Transfer rate: 26956 bits/sec, 305 bytes/write. (gdb) continue Continuing. Start TCP test - ECHO mode No load = 723469 Set background load = 50% starting 10 threads Set no background load High Load[100] = 686113 => 6% Set background load = 50% starting 10 threads Set no background load High Load[200] = 655463 => 10% Set background load = 50% starting 10 threads Set no background load High Load[400] = 593289 => 18% Set background load = 50% starting 10 threads Set no background load High Load[800] = 473787 => 35% Set background load = 50% starting 10 threads Set no background load High Load[1600] = 234626 => 68% Set background load = 50% starting 10 threads Set no background load Load[1200] = 354165 => 52% Set background load = 50% starting 10 threads Set no background load Final load[1153] = 368145 => 50% Here are two screens from tcp_sink and tcp_source. #./ecos/packages/net/tcpip/current/tests/tcp_source 192.168.1.20 Start TCP test - SOURCE mode to 192.168.1.20 Can't connect to target: No route to host #./ecos/packages/net/tcpip/current/tests/tcp_sink 192.168.1.20 Start TCP test - SOURCE mode to 192.168.1.20 Can't connect to target: No route to host The problem I'm suspecious of is that: after tcp_echo is running through serial port, the ipaq seems stuck there and not responding to other connections (even from ethernet card interface.) But I don't know what is behind. thanks, Weilong --- Jonathan Larmour <jlarmour@redhat.com> wrote: > Weilong Li wrote: > > > > I try to run tcp_echo, tcp_source and tcp_sink > > program on ipaq. > > > > >From linux host, I used serial port to connect > > ipaq, then I used gdb to remotely run tcp_echo, > after > > tcp_echo is running, and I run tcp_source and > > tcp_sink, but I got "no route to host" message. > > And I cannot ping ipaq. > > > > While before I run tcp_echo, I can ping ipaq, and > > tcp_source and tcp_sink can successfully run and > > waiting for packets. But I cannot run tcp_echo > > through gdb, it simply cannot load the program. > > You cannot even load it? Do you get any output from > GDB? > > 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 __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-01 12:34 ` Weilong Li @ 2001-07-02 11:45 ` Jonathan Larmour 2001-07-02 12:02 ` Weilong Li 0 siblings, 1 reply; 11+ messages in thread From: Jonathan Larmour @ 2001-07-02 11:45 UTC (permalink / raw) To: Weilong Li; +Cc: ecos-discuss Weilong Li wrote: > > The ip adddress of ipaq is 192.168.1.20. After redboot > boots on ipaq, I issued tcp_source and tcp_sink > command > to target on my redhat host. > > # ./ecos/packages/net/tcpip/current/tests/tcp_sink > 192.168.1.20 > Start TCP test - SINK mode to 192.168.1.20 > > At another terminal: > # ./ecos/packages/net/tcpip/current/tests/tcp_source > 192.168.1.20 > Start TCP test - SOURCE mode to 192.168.1.20 > > And I pinged 192.168.1.20, and I got response. > > Then I issued gdb command on tcp_echo. This time it > can load, while immediately after I type "continue", > and tcp_echo is running, tcp_sink and tcp_source > will report "no route to 192.168.1.20", and > I cannot ping ipaq from linux host. > Here is the screen. > #arm-elf-gdb > ./ipaq/install/tests/net/tcpip/current/tests/tcp_echo > GNU gdb 5.0 > Copyright 2000 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General > Public License, and you are > welcome to change it and/or distribute copies of it > under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show > warranty" for details. > This GDB was configured as "--host=i586-pc-linux-gnu > --target=arm-elf"... > (gdb) set remotebaud 38400 > (gdb) target remote /dev/ttyS0 > Remote debugging using /dev/ttyS0 > 0x50046f30 in ?? () > (gdb) load > Loading section .rom_vectors, size 0x40 lma 0x20000 > Loading section .text, size 0x2ec2c lma 0x20040 > Loading section .rodata, size 0x1d18 lma 0x4ec6c > Loading section .data, size 0xc3c lma 0x50984 > Start address 0x20040 , load size 202176 > Transfer rate: 26956 bits/sec, 305 bytes/write. > (gdb) continue > Continuing. > Start TCP test - ECHO mode > No load = 723469 > Set background load = 50% starting 10 threads > Set no background load > High Load[100] = 686113 => 6% > Set background load = 50% starting 10 threads > Set no background load > High Load[200] = 655463 => 10% > Set background load = 50% starting 10 threads > Set no background load > High Load[400] = 593289 => 18% > Set background load = 50% starting 10 threads > Set no background load > High Load[800] = 473787 => 35% > Set background load = 50% starting 10 threads > Set no background load > High Load[1600] = 234626 => 68% > Set background load = 50% starting 10 threads > Set no background load > Load[1200] = 354165 => 52% > Set background load = 50% starting 10 threads > Set no background load > Final load[1153] = 368145 => 50% > > Here are two screens from tcp_sink and tcp_source. > #./ecos/packages/net/tcpip/current/tests/tcp_source > 192.168.1.20 > Start TCP test - SOURCE mode to 192.168.1.20 > > Can't connect to target: No route to host > > #./ecos/packages/net/tcpip/current/tests/tcp_sink > 192.168.1.20 > Start TCP test - SOURCE mode to 192.168.1.20 > > Can't connect to target: No route to host > > The problem I'm suspecious of is that: after tcp_echo > is running through serial port, the ipaq seems stuck > there and not responding to other connections (even > from ethernet card interface.) > But I don't know what is behind. Firstly, are you making sure that tcp_echo is running _before_ starting tcp_sink and tcp_source? Secondly when you talk about the IP address of the ipaq, there are two to consider: RedBoot's and eCos's. Their addresses should not be the same. The latter one is the relevant one for the net test. 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 Come to the Red Hat TechWorld open source conference in Brussels! Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-02 11:45 ` Jonathan Larmour @ 2001-07-02 12:02 ` Weilong Li 2001-07-02 12:14 ` Jonathan Larmour 0 siblings, 1 reply; 11+ messages in thread From: Weilong Li @ 2001-07-02 12:02 UTC (permalink / raw) To: Jonathan Larmour; +Cc: ecos-discuss I also tried running tcp_echo before, after tcp_echo is running, I cannot ping ipaq, so tcp_source and tcp_sink will always return "no route to host" error message. The ip address of ipaq I'm talking about is assigned by running a dhcp server on linux host, then upon redboot boots, it will detect the socket communication ethernet card, and then assign the ip address. So in this sense, I think the ip address is redboot's ip address. I don't know how the ip address of ecos is assigned, can you elaborate on this ? thank you so much, Weilong > > Firstly, are you making sure that tcp_echo is > running _before_ starting > tcp_sink and tcp_source? Secondly when you talk > about the IP address of the > ipaq, there are two to consider: RedBoot's and > eCos's. Their addresses > should not be the same. The latter one is the > relevant one for the net > test. > > 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 > Come to the Red Hat TechWorld open source conference > in Brussels! > Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-02 12:02 ` Weilong Li @ 2001-07-02 12:14 ` Jonathan Larmour 2001-07-03 2:40 ` Weilong Li 2001-07-07 18:29 ` Weilong Li 0 siblings, 2 replies; 11+ messages in thread From: Jonathan Larmour @ 2001-07-02 12:14 UTC (permalink / raw) To: Weilong Li; +Cc: ecos-discuss Weilong Li wrote: > > I also tried running tcp_echo before, after > tcp_echo is running, I cannot ping ipaq, > so tcp_source and tcp_sink will always > return "no route to host" error message. > The ip address of ipaq I'm talking about > is assigned by running a dhcp server on linux host, > then upon redboot boots, it will detect the > socket communication ethernet card, and then > assign the ip address. So in this sense, > I think the ip address is redboot's ip address. > I don't know how the ip address of ecos is assigned, > can you elaborate on this ? The eCos network stack does not use redboot's ip address ( you can't have two different network stacks processing the same data). The eCos stack's IP address is set according to the CDL data, either also from BOOTP/DHCP, or statically. Try setting it statically as that's safest. Look for the component CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS and the options within it. 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 Come to the Red Hat TechWorld open source conference in Brussels! Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-02 12:14 ` Jonathan Larmour @ 2001-07-03 2:40 ` Weilong Li 2001-07-04 19:52 ` Jonathan Larmour 2001-07-07 18:29 ` Weilong Li 1 sibling, 1 reply; 11+ messages in thread From: Weilong Li @ 2001-07-03 2:40 UTC (permalink / raw) To: Jonathan Larmour; +Cc: ecos-discuss Hi, Jonathan, I have another newbie question. I have changed the configuration regarding CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS, and also give a static ip address for ecos, and then ecosconfig resolve, ecosconfig tree, and make. My question is how to update the ecos version that is already running on ipaq with the new ecos version. thanks a lot, Weilong --- Jonathan Larmour <jlarmour@redhat.com> wrote: > Weilong Li wrote: > > > > I also tried running tcp_echo before, after > > tcp_echo is running, I cannot ping ipaq, > > so tcp_source and tcp_sink will always > > return "no route to host" error message. > > The ip address of ipaq I'm talking about > > is assigned by running a dhcp server on linux > host, > > then upon redboot boots, it will detect the > > socket communication ethernet card, and then > > assign the ip address. So in this sense, > > I think the ip address is redboot's ip address. > > I don't know how the ip address of ecos is > assigned, > > can you elaborate on this ? > > The eCos network stack does not use redboot's ip > address ( you can't have > two different network stacks processing the same > data). The eCos stack's IP > address is set according to the CDL data, either > also from BOOTP/DHCP, or > statically. Try setting it statically as that's > safest. Look for the > component CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS and > the options within it. > > 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 > Come to the Red Hat TechWorld open source conference > in Brussels! > Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-03 2:40 ` Weilong Li @ 2001-07-04 19:52 ` Jonathan Larmour 0 siblings, 0 replies; 11+ messages in thread From: Jonathan Larmour @ 2001-07-04 19:52 UTC (permalink / raw) To: Weilong Li; +Cc: ecos-discuss Weilong Li wrote: > > Hi, Jonathan, I have another newbie question. > I have changed the configuration regarding > CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS, and > also give a static ip address for ecos, > and then ecosconfig resolve, ecosconfig tree, > and make. > My question is how to update the ecos version > that is already running on ipaq with the new > ecos version. eCos is linked with your application so relinking your application with the eCos libraries and uploading that is sufficient. 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 Come to the Red Hat TechWorld open source conference in Brussels! Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [ECOS] network test problem on ipaq 2001-07-02 12:14 ` Jonathan Larmour 2001-07-03 2:40 ` Weilong Li @ 2001-07-07 18:29 ` Weilong Li 1 sibling, 0 replies; 11+ messages in thread From: Weilong Li @ 2001-07-07 18:29 UTC (permalink / raw) To: Jonathan Larmour; +Cc: ecos-discuss Hi, I have tried both static ip and dhcp, still I cannot get the network configuration of ecos to work correctly. Is there any documentation , or best of all, an example of network configuration in the ecos.ecc, this would help a lot. thanks, Weilong --- Jonathan Larmour <jlarmour@redhat.com> wrote: > Weilong Li wrote: > > > > I also tried running tcp_echo before, after > > tcp_echo is running, I cannot ping ipaq, > > so tcp_source and tcp_sink will always > > return "no route to host" error message. > > The ip address of ipaq I'm talking about > > is assigned by running a dhcp server on linux > host, > > then upon redboot boots, it will detect the > > socket communication ethernet card, and then > > assign the ip address. So in this sense, > > I think the ip address is redboot's ip address. > > I don't know how the ip address of ecos is > assigned, > > can you elaborate on this ? > > The eCos network stack does not use redboot's ip > address ( you can't have > two different network stacks processing the same > data). The eCos stack's IP > address is set according to the CDL data, either > also from BOOTP/DHCP, or > statically. Try setting it statically as that's > safest. Look for the > component CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS and > the options within it. > > 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 > Come to the Red Hat TechWorld open source conference > in Brussels! > Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/ __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [ECOS] network test problem on ipaq 2001-07-01 3:07 [ECOS] network test problem on ipaq Weilong Li 2001-07-01 8:46 ` Jonathan Larmour @ 2001-07-01 19:41 ` Gary Thomas 2001-07-01 21:35 ` Weilong Li 1 sibling, 1 reply; 11+ messages in thread From: Gary Thomas @ 2001-07-01 19:41 UTC (permalink / raw) To: Weilong Li; +Cc: ecos-discuss On 01-Jul-2001 Weilong Li wrote: > I try to run tcp_echo, tcp_source and tcp_sink > program on ipaq. > >From linux host, I used serial port to connect > ipaq, then I used gdb to remotely run tcp_echo, after > tcp_echo is running, and I run tcp_source and > tcp_sink, but I got "no route to host" message. > And I cannot ping ipaq. > > While before I run tcp_echo, I can ping ipaq, and > tcp_source and tcp_sink can successfully run and > waiting for packets. But I cannot run tcp_echo > through gdb, it simply cannot load the program. > > So it seems there are conflicts even I used > serial port to run tcp_echo, and used > ethernet interface to run tcp_sink and > tcp_source. Please help. We need more details. What version of RedBoot? Can you send a listing of the output from GDB? ^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: [ECOS] network test problem on ipaq 2001-07-01 19:41 ` Gary Thomas @ 2001-07-01 21:35 ` Weilong Li 0 siblings, 0 replies; 11+ messages in thread From: Weilong Li @ 2001-07-01 21:35 UTC (permalink / raw) To: Gary Thomas; +Cc: ecos-discuss Hi, Gary, please look at the email I posted later after my original post, there are detailed description of the problem. thanks a lot, Weilong --- Gary Thomas <gthomas@cambridge.redhat.com> wrote: > > On 01-Jul-2001 Weilong Li wrote: > > I try to run tcp_echo, tcp_source and tcp_sink > > program on ipaq. > > > >>From linux host, I used serial port to connect > > ipaq, then I used gdb to remotely run tcp_echo, > after > > tcp_echo is running, and I run tcp_source and > > tcp_sink, but I got "no route to host" message. > > And I cannot ping ipaq. > > > > While before I run tcp_echo, I can ping ipaq, and > > tcp_source and tcp_sink can successfully run and > > waiting for packets. But I cannot run tcp_echo > > through gdb, it simply cannot load the program. > > > > So it seems there are conflicts even I used > > serial port to run tcp_echo, and used > > ethernet interface to run tcp_sink and > > tcp_source. Please help. > > We need more details. What version of RedBoot? Can > you send > a listing of the output from GDB? __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2001-07-07 18:29 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2001-07-01 3:07 [ECOS] network test problem on ipaq Weilong Li 2001-07-01 8:46 ` Jonathan Larmour 2001-07-01 12:34 ` Weilong Li 2001-07-02 11:45 ` Jonathan Larmour 2001-07-02 12:02 ` Weilong Li 2001-07-02 12:14 ` Jonathan Larmour 2001-07-03 2:40 ` Weilong Li 2001-07-04 19:52 ` Jonathan Larmour 2001-07-07 18:29 ` Weilong Li 2001-07-01 19:41 ` Gary Thomas 2001-07-01 21:35 ` Weilong Li
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).