headers
Lin Ming | 1 Nov 2002 03:25
Favicon

Re: Re: How to generate the binay file

Hi, Tim,

Sure I can generate the binary file before.(I am sorry not to make myself clear.)
But I cannot get it run on my EB40A. It seems there is the problem about memory layout.
The elf file can be executed in arm-elf-gdb, but the binary file cannot run.

I built ecos in default and the rom_vectors in target.ld is 0xC000. The bin cannot run.
Then I changed eCos HAL>ROM monitor support>work with a ROM monitor to behave as a ROM monitor.
And built ecos. Then the rom_vectors in target.ld is changed to 0x0100000 + 10000, still not run.
So I changed target.ld by hand remove + 10000, then the rom_vectors is changed to 0x01000000.
It seems ok. Then my bin runs but not completely: the serial port works well but the LEDs don't 
work. I don't know why...

Yes, I am a newbie in atmel and I don't know much about ecos. I want to make clear how
to develop our AT91 with ecos and gnu tools so that we can have a free development solution 
for the customer. So would you please help me?

Thanks a lot!!   

Best Regards,				 
Lin Ming
2002-11-01

======= 2002-10-31 10:37:00 YOU WROTE:=======

>Your syntax for arm-elf-objcopy doesn't appear correct.
>Running 'arm-elf-obcopy --help' says to use:
>
>arm-elf-objcopy [switches] infile [outfile]
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
AL Chane | 1 Nov 2002 04:33
Picon

stubs and redboot building

What are the main differences between stubs and redboot building?
I am doing an eCos platform porting. First step is to make GDB
work on the new platform. Which building takes less efforts?

thanks for the helps.

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 2 comments |
headers
Lin Ming | 1 Nov 2002 05:24
Favicon

Re: Re: How to generate the binay file

Hi, Tim,

Sure I can generate the binary file before.(I am sorry not to make myself clear.)
But I cannot get it run on my EB40A. It seems there is the problem about memory layout.
The elf file can be executed in arm-elf-gdb, but the binary file cannot run.

I built ecos in default and the rom_vectors in target.ld is 0xC000. The bin cannot run.
Then I changed eCos HAL>ROM monitor support>work with a ROM monitor to behave as a ROM monitor.
And built ecos. Then the rom_vectors in target.ld is changed to 0x0100000 + 10000, still not run.
So I changed target.ld by hand remove + 10000, then the rom_vectors is changed to 0x01000000.
It seems ok. Then my bin runs but not completely: the serial port works well but the LEDs don't 
work. I don't know why...

Yes, I am a newbie in atmel and I don't know much about ecos. I want to make clear how
to develop our AT91 with ecos and gnu tools so that we can have a free development solution 
for the customer. So would you please help me?

Thanks a lot!!   

Best Regards,				 
Lin Ming
2002-11-01

======= 2002-10-31 10:37:00 YOU WROTE:=======

>Your syntax for arm-elf-objcopy doesn't appear correct.
>Running 'arm-elf-obcopy --help' says to use:
>
>arm-elf-objcopy [switches] infile [outfile]
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
00917764d | 1 Nov 2002 06:58
Picon

Port eCos to iPAQ H3850

As it is sucessful to port eCos to iPAQ H3630, I would like to port eCos to 
the iPAQ H3850. However, there are some problems. The touch screen will not 
work in iPAQ H3850. Is there any thing I need to modify in order to port eCos 
to iPAQ H3850?

Pang

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 1 comment |
headers
Andrew Lunn | 1 Nov 2002 09:24
Picon
Favicon

Re: Accessing config parameters in define_proc code

On Thu, Oct 31, 2002 at 09:26:04PM +0000, Bart Veer wrote:
> >>>>> "Andrew" == Andrew Lunn <andrew.lunn <at> ascom.ch> writes:
> 
>     >> I'm sure that Bart will correct me if I'm wrong, but I'm pretty 
>     >> sure that the ability to use CDL variables like this was never
>     >> implemented. 
>     >> 
> 
>     Andrew> I think you are right. I found some documentation i didn't
>     Andrew> know existed. host/libcdl/doc/*.sgml.
> 
> That is the Component Writer's Guide, which I think is still the
> single largest piece of documentation in eCos. How could you miss it?

I was under the silly impression that all documentation was under
ecos/doc/sgml. Well, i know parts of the main manual are inside side
individual target packages, but the makefiles are under this branch of
the tree.

Iztok does not have the Components writers guide on this web site
either......

Humm, just ran a find . -name "*.sgml"

There are a few documents file this. I think this is a problem. Unless
you go looking, you just don't know these documentation exists. It
would be better if there was one central place you can make them from
and an install process that puts the resulting html or pdf into one
tree.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Andrew Lunn | 1 Nov 2002 09:27
Picon
Favicon

Re: Okay,I got everything but configtool.exe built (GUI).

On Thu, Oct 31, 2002 at 02:14:44PM -0700, Gary Thomas wrote:
> Is there some reason that you are going to all of this trouble, just
> to build the tools?  There are pre-built executables available for both 
> 'ecosconfig' and the GUI tool on the web-site.

Also, you say you are a unix'y person. You don't need the GUI, you can
configure everything with ecosconfig and an text editor. 

          Andrew

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
Lin Ming | 1 Nov 2002 09:37
Favicon

Fw: Re: Re: [ECOS] How to generate the binay file

Thanks to God! I have got it work. It really works!!

Best Regards,  
Lin Ming
2002-11-01 

************HERE IS THE FORWARD************
NAME: 		Lin Ming
ADDRESS:	minglin <at> atmel.com

>Hi, Tim,
>
>Sure I can generate the binary file before.(I am sorry not to make myself clear.)
>But I cannot get it run on my EB40A. It seems there is the problem about memory layout.
>The elf file can be executed in arm-elf-gdb, but the binary file cannot run.
>
>I built ecos in default and the rom_vectors in target.ld is 0xC000. The bin cannot run.
>Then I changed eCos HAL>ROM monitor support>work with a ROM monitor to behave as a ROM monitor.
>And built ecos. Then the rom_vectors in target.ld is changed to 0x0100000 + 10000, still not run.
>So I changed target.ld by hand remove + 10000, then the rom_vectors is changed to 0x01000000.
>It seems ok. Then my bin runs but not completely: the serial port works well but the LEDs don't 
>work. I don't know why...
>
>Yes, I am a newbie in atmel and I don't know much about ecos. I want to make clear how
>to develop our AT91 with ecos and gnu tools so that we can have a free development solution 
>for the customer. So would you please help me?
>
>Thanks a lot!!   
>
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Vijai Krishnamurthy | 1 Nov 2002 14:44

server_test vmware tribulation

Thanks for the vmware dhcp information, but I'm still facing this problem.

Here's my observation in detail supplemented by tcpdump trace on vmnet8
interface:
vmnet8 is configured for 192.168.2.1 with dns and router at 192.168.2.2

Redboot (configured for static ip 192.168.2.3) boots quite well.
tcpdump -
22:21:43.357008 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:44.379784 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:45.404087 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:46.505599 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:47.526022 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
.
.
.

RedBoot defaults to the static IP address and on the screen I can see these
prints -
Can't get BOOTP info, using default IP address
Ethernet eth0: MAC address 27:39:08:00:00:8e
IP: 192.168.2.3/255.255.255.0, Gateway: 192.168.2.2
Default server: 0.0.0.0, DNS server IP: 192.168.2.2
.
.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Andrew Lunn | 1 Nov 2002 14:41
Picon
Favicon

redboot always disabled entry

Hi Gary

Redboot configury can store entries that are always enabled using
ALWAYS_ENABLED as the enable key. Can you think of a waoy of doing an
always disabled?

I want an entry that fconfig -l won't list. The obvious solution is
make it disabled, but i cannot find a way to do that.

Any ideas?

    Thanks
        Andrew

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 2 comments |
headers
Gary Thomas | 1 Nov 2002 14:47
Favicon

Re: stubs and redboot building

On Thu, 2002-10-31 at 20:33, AL Chane wrote:
> What are the main differences between stubs and redboot building?
> I am doing an eCos platform porting. First step is to make GDB
> work on the new platform. Which building takes less efforts?

It depends on the architecture base.  For most of them, the
basic GDB support is already up-to-speed and all that you
need is a basic HAL.  Once you have that, you can build
either RedBoot or bare stubs.  For most environments, RedBoot
is more useful.  The GDB stubs haven't been used much in
recent times, so that course might be a little harder.

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas <at> ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------

--

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

Gmane