Saurabh Agarwal | 1 Jul 13:53 2004
Picon

Help Nedded understanding ecos

Hi All,
I am new to embedded and ecos development i need ur help in starting
ecos development.

I had installed ecos on my windows machine in cygwin .
Now i want to start with sample and simple test programs using my P3
syatem as i dont have target boards now.
Can i do that and are there any emulators(freeware) available through
which i can simulate target machines.

please also share anything that u think will help me as startter.
Please help.
Thanks for your Time  and Help

Martin Laabs | 8 Jul 22:54 2004
Picon

redboot does not start in ram mode

Hi,

I have a  3e-524 board with an IXP425. Because I want
to update the redboot I tried to compile a ram version.
Therefor I used the guide from intel beacuse the board seems
to be only slightly different from intels IXDP425 board.
I changed the memory map and tried to load/start the image. I failed.
After many attempt I tried to load the original RAM version that
is saved in the flash:

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0x51000000  0x51000000  0x00040000  0x00000000
RedBoot config    0x517C0000  0x517C0000  0x00001000  0x00000000
FIS directory     0x517E0000  0x517E0000  0x00020000  0x00000000
RedBoot_RAM       0x51040000  0x11400000  0x00040000  0x00000000
zImage            0x51080000  0x11400000  0x000C0000  0x00000000
RedBoot> fis load RedBoot_RAM
RedBoot> go

But after pressing return the board hangs. Because there is an eeprom
onboard the RAM begins at 0x10000000

edBoot> v 
RedBoot(tm) bootstrap and debug environment [ROM] 
Non-certified release, version 2.00 - built 10:04:47, Dec 17 2003 

Platform: 3eTI-EAP (XScale) 
Copyright (C) 2000, 2001, 2002, Red Hat, Inc. 

(Continue reading)

Andrew Lunn | 9 Jul 10:40 2004
Picon

Re: redboot does not start in ram mode

On Thu, Jul 08, 2004 at 10:54:55PM +0200, Martin Laabs wrote:
> Hi,
> 
> I have a  3e-524 board with an IXP425. Because I want
> to update the redboot I tried to compile a ram version.
> Therefor I used the guide from intel beacuse the board seems
> to be only slightly different from intels IXDP425 board.
> I changed the memory map and tried to load/start the image. I failed.
> After many attempt I tried to load the original RAM version that
> is saved in the flash:
> 
> RedBoot> fis list
> Name              FLASH addr  Mem addr    Length      Entry point
> RedBoot           0x51000000  0x51000000  0x00040000  0x00000000
> RedBoot config    0x517C0000  0x517C0000  0x00001000  0x00000000
> FIS directory     0x517E0000  0x517E0000  0x00020000  0x00000000
> RedBoot_RAM       0x51040000  0x11400000  0x00040000  0x00000000
> zImage            0x51080000  0x11400000  0x000C0000  0x00000000
> RedBoot> fis load RedBoot_RAM
> RedBoot> go
> 
> But after pressing return the board hangs. Because there is an eeprom
> onboard the RAM begins at 0x10000000
> 
> edBoot> v 
> RedBoot(tm) bootstrap and debug environment [ROM] 
> Non-certified release, version 2.00 - built 10:04:47, Dec 17 2003 
>  
> Platform: 3eTI-EAP (XScale) 
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc. 
(Continue reading)

Martin Laabs | 9 Jul 15:25 2004
Picon

Re: redboot does not start in ram mode

On Fri, Jul 09, 2004 at 10:40:01AM +0200, Andrew Lunn wrote:
> On Thu, Jul 08, 2004 at 10:54:55PM +0200, Martin Laabs wrote:

> > But when I load the RedBoot_RAM to 0x10200000 (or an other
> > explicit address with the -b option) I get much binary data 
> > printet onto my terminal.
> 
> eCos images are not position independant. So this will not work.

Why isn't it? Does it depend on the interrupt vectors and so on?

> You might want to take a look at the MMU setup. Normally the RAM is
> mapped by the MMU to address 0. It could be that on your hardware it
> is mapping the EEPROM to memory zero, which is not going to work...

Yes. You are right. The Ram is mapped to 0x10000000-0x12000000.
So I can't load redboot to 0x0:

RedBoot> load -r -b 0 -m x                                                      
Specified address (0x00000000) is not believed to be in RAM - are you sure (y/n

This is exactly my problem. But the manufacturer placed a RAM
version of redboot in the fis and this also does not work.

I thought it is enough only to change the linker script and
the constant in the header file. 

Can you give me a hint how to change redboot that it works
at another adress than 0x0?

(Continue reading)

Gary Thomas | 9 Jul 15:34 2004

Re: redboot does not start in ram mode

On Fri, 2004-07-09 at 07:25, Martin Laabs wrote:
> On Fri, Jul 09, 2004 at 10:40:01AM +0200, Andrew Lunn wrote:
> > On Thu, Jul 08, 2004 at 10:54:55PM +0200, Martin Laabs wrote:
> 
> 
> > > But when I load the RedBoot_RAM to 0x10200000 (or an other
> > > explicit address with the -b option) I get much binary data 
> > > printet onto my terminal.
> > 
> > eCos images are not position independant. So this will not work.
> 
> Why isn't it? Does it depend on the interrupt vectors and so on?
> 
> > You might want to take a look at the MMU setup. Normally the RAM is
> > mapped by the MMU to address 0. It could be that on your hardware it
> > is mapping the EEPROM to memory zero, which is not going to work...
> 
> Yes. You are right. The Ram is mapped to 0x10000000-0x12000000.
> So I can't load redboot to 0x0:
> 
> RedBoot> load -r -b 0 -m x                                                      
> Specified address (0x00000000) is not believed to be in RAM - are you sure (y/n
> 
> 
> This is exactly my problem. But the manufacturer placed a RAM
> version of redboot in the fis and this also does not work.
> 
> I thought it is enough only to change the linker script and
> the constant in the header file. 
> 
(Continue reading)

Edgar Grimberg | 9 Jul 16:00 2004
Picon

"fis create" substitute

It's me again with FS problems. 

Is there any way to substitute the "fis create" command in RedBoot with
some other means to load an image to the flash? (I have an BDI2000
debugger). I need this because of insufficient RAM on my board, so I
have no room to store an image in RAM. I want to flash some JFFS2 image
and run the jffs test application.

Thanks,
Edgar

Saurabh Agarwal | 9 Jul 17:08 2004
Picon

Hot to use redboot on P3 using existing bios as basic boot system

Hi All,
I want to use my Pentium3 as the target system for the time being i
want that redboot should boot from floppy ie first boot will be
through standard bios and then REDBOOT takes control after booting
from floppy.
Firstly standard bios is used and using it redboot takes control after
booting from floppy .
If somebody have the required image please mail it.

I think i can make some sense .
Please help me

--

-- 
Saurabh Agarwal
9868358071

Saurabh Agarwal | 12 Jul 06:58 2004
Picon

Implementing JVM for ecos

Hi all,
I just heard from thje mailing list itself that JVM is not implemented
in ecos and in todays scenario as j2me is at peak i think it will be
quite nice to implement jvm on ecos.
So I want to implement JVM in ecos if anybody have any pointers
relating to implementing jvm and want  to help we can look toward it.
Any participants are invited.

please help
Saurabh Agarwal
saurabhagarwal1981 <at> gmail.com
9868358071

Pablo Bleyer Kocik | 12 Jul 07:29 2004
Picon

Re: [ECOS] Implementing JVM for ecos

At 00:58 2004-07-12, Saurabh Agarwal wrote:
>Hi all,
>I just heard from thje mailing list itself that JVM is not implemented
>in ecos and in todays scenario as j2me is at peak i think it will be
>quite nice to implement jvm on ecos.
>So I want to implement JVM in ecos if anybody have any pointers
>relating to implementing jvm and want  to help we can look toward it.
>Any participants are invited.

Good intro info, though a bit outdated: http://www.artima.com/java/index.html
http://java.sun.com/docs/books/vmspec/

http://java.sun.com/products/cdc/
http://java.sun.com/products/cldc/
http://www.kaffe.org/
http://www.rtjcom.com/
http://www.wabasoft.com/
http://www.superwaba.com.br/
http://jamvm.sourceforge.net/
http://lejos.sourceforge.net/
http://kissme.sourceforge.net/
http://sablevm.org/
...

  I would strongly suggest you to *not* reinvent the wheel. Find one of the 
promising projects out there and contribute to it adapting it to eCos.

  Regards.

--
(Continue reading)

Chris Gray | 12 Jul 10:07 2004
Picon

Re: Implementing JVM for ecos

On Monday 12 July 2004 06:58, Saurabh Agarwal wrote:
> Hi all,
> I just heard from thje mailing list itself that JVM is not implemented
> in ecos and in todays scenario as j2me is at peak i think it will be
> quite nice to implement jvm on ecos.

Then you're not paying attention. :) At least Wonka and Kaffe have been ported 
to eCos. The Wonka port was working on StrongARM, but will need some work to 
get it to build because some internal APIs have changed a bit; plus Wonka 
currently assumes an MMU in the way it manages its heap. I know it's possible 
to remove the dependency on MMU because I've done it. :) Last year an Italian 
student called Andrea Scian was working on Wonka-arm7-eCos, but I'm not sure 
what she finally achieved. Kaffe on eCos exists for Hitachi architecture, so 
you should be able to get that working in ARM7 too.

There are several other open-source VMs, but I don't know how easy they will 
be to port to eCos and to MMU-less systems; for example some VMs use the MMU 
to detect NullPointerException.

As far as J2ME is concerned, Wonka aims at J2ME CDC; so far as I am aware all 
other open-source VMs are J2SE, so for embedded devices some degree of 
stripping-down will be necessary. I don't know of any open source VM 
targeting J2ME CLDC.

> So I want to implement JVM in ecos if anybody have any pointers
> relating to implementing jvm and want  to help we can look toward it.
> Any participants are invited.

Wonka: http://wonka.acunia.com
Kaffe: http://www.kaffe.org, and http://sourceforge.jp/projects/kaffe-ecos/
(Continue reading)


Gmane