Re: [ECOS] RE: networking support for my eCos application

[Gary Thomas <gary at mlbassoc dot com>]

C B wrote:
> 
> Brilliant!  Changing the CYG_HAL_STARTUP to RAM seems to resolve the issue I was having.  However, rather than seeing the expected output from my simple HelloWorld program that I see with my older version of eCos I get the following output:
> 
> ------------------------- begin output -------------------------
> RedBoot> go 0x20020040
> [cyg_net_init] Init: mbinit(0x00000000)
> [cyg_net_init] Init: cyg_net_init_devs(0x00000000)
> Init device 'dm9000_eth0'
> -------------------------- end output ---------------------------
> 
> Thoughts?

How did you connect to RedBoot to initiate this session?  If it's
via the network, then you are probably experiencing problems due to
the fact that RedBoot and your application have to share the same
hardware.  If this is the case, you'll need (somehow) to arrange that
the RedBoot connection and your application use separate IP addresses
(this is part of how RedBoot can separate what traffic goes to the
debug session and what goes to the application).

Another problem which can come up [again when you connect to RedBoot
via network] is when the driver in the eCos application tries to print
debug messages *while the driver/hardware is being initialized*.  In
this case, it's wise to make sure that CYGPKG_NET_FORCE_SERIAL_CONSOLE
is set which will force any debug messages which happen during system
initialization to a serial console (keeps the RedBoot network driver
from getting confused).  Try running your application from a serial
console - if it works, then this is an issue for you.

> 
>> Date: Fri, 9 Nov 2007 19:55:42 +0100
>> From: andrew@lunn.ch
>> To: csb_80@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: [ECOS] RE: networking support for my eCos application
>>
>>> MEMORY
>>> {
>>> ram : ORIGIN = 0x20000000, LENGTH = 0x00C00000
>>> rom : ORIGIN = 0x20C00000, LENGTH = 0x00400000
>>> sram : ORIGIN = 0x00000100, LENGTH = 0x00023F00
>>> }
>>>
>>> versus this for the older (working) version:
>>>
>>> MEMORY
>>> {
>>> ram : ORIGIN = 0x20000000, LENGTH = 0x02000000
>>> sram : ORIGIN = 0x00000000, LENGTH = 0x00024000
>>> }
>>>
>>>
>>> Can anyone provide a little clarification on how these files are generated and what I may have screwed up in my config.
>> The linker file is derived from you hal include/pkgconf/*.ldi files.
>>
>> My guess is your working binary is a RAM startup application, but your
>> new application is a ROM startup. Take a look at the value of
>> CYG_HAL_STARTUP in your working and none working configuration.
>>
>> Andrew
> 
> _________________________________________________________________
> Windows Live Hotmail and Microsoft Office Outlook – together at last.  Get it now.
> http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033
> 


-- 
------------------------------------------------------------
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