This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Can't connect properly (TCP/IP)
- From: Gary Thomas <gary at mlbassoc dot com>
- To: "EXTERNAL Gladis Olaf (Praktikant; CR/AEM)" <external dot Olaf dot Gladis at de dot bosch dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Thu, 01 Nov 2007 05:49:18 -0600
- Subject: Re: [ECOS] Can't connect properly (TCP/IP)
- References: <F6E0DC7B316B5342918DD39721EE25B101615960@si-mail07.de.bosch.com> <20071031160251.GK17077@lunn.ch> <F6E0DC7B316B5342918DD39721EE25B101615963@si-mail07.de.bosch.com>
EXTERNAL Gladis Olaf (Praktikant; CR/AEM) wrote:
> Thank you,
>
> This is the output from the serial port, when i am starting the programm
> normaly.
>
> RedBoot> lo test.srec
> Using default protocol (TFTP)
> Entry point: 0x00100000, address range: 0x00100000-0x00163730
> RedBoot> go
> [cyg_net_init] Init: mbinit(0x00000000)
> [cyg_net_init] Init: cyg_net_init_devs(0x00000000)
> Init device 'fec_eth'
> PHY0: Intel LXT971
> Eth physical state: 0780
> FEC eth0: 10Mb
> [cyg_net_init] Init: loopattach(0x00000000)
> [cyg_net_init] Init: ifinit(0x00000000)
> [cyg_net_init] Init: domaininit(0x00000000)
> [cyg_net_init] Init: cyg_net_add_domain(0x00162748)
> New domain internet at 0x00000000
> [cyg_net_init] Init: cyg_net_add_domain(0x0016221c)
> New domain route at 0x00000000
> [cyg_net_init] Init: call_route_init(0x00000000)
> [cyg_net_init] Done
> [eth_drv_ioctl] Warning: Driver can't set multi-cast mode
> [eth_drv_ioctl] Warning: Driver can't set multi-cast mode
> [eth_drv_ioctl] Warning: Driver can't set multi-cast mode
> skTPI_Init: FPGA loaded with file /FPGA_Default.rbf
> VERSION: 0x101D and
> $T04thread:00000006;40:001647c0;01:00164788;#41+
These messages indicate that your program has crashed (at PC=0x1647c0)
Try connecting with GDB to find out why.
>
> So the programm hang up before the previous message has been wirtten
> completly, i dont think
> That i would get more information (??) when i add some diag_printf().
> But i used a debugger (via tcp)
> And the code will e executet until the connect statement, and then it
> stops.
>
> I also attached the capture from ethereal, and i think this looks quite
> normal.
>
> Node ---> PC [Syn]
> Pc ---> Node [Syn,Ack]
> Node ---> PC [Ack]
>
> Has anybody an idea?
>
> Thank you in advance.
>
> Olaf Gladis
>
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Mittwoch, 31. Oktober 2007 17:03
> To: EXTERNAL Gladis Olaf (Praktikant; CR/AEM)
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] Can't connect properly (TCP/IP)
>
>> I would add some diag_printf() so you know what has been executed and
>> if there are any errors returned.
>>
>> I would also use tcpdump/ethereal etc, to watch the packets flowing
>> backwards and forwards. You should be able to see this data in a
>> packet etc.
>>
>> Andrew
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss