Hello

I have managed to update eCos-2.0 port, adjust it to the current toolchain and track some bugs. I believe it is stable now, as it passes both my tests and tests supplied with ecos.

I would be happy to publish the sources, create a wiki page and further maintain the port. I am also planning to add more drivers (for now, only UART is available). Is it possible for me to upload the code to opencores SVN?

Finally, I would like to commit the code to the official eCos repository.

Regards
Piotr Skrzypek

That's unreal. Thanks very much for your efforts. It would be great to have you as the maintainer for the newly updated eCos port.

If you're planning on hosting it here on OpenCores we should give you write-access to the SVN to commit. Is this your intention?

The wiki page should be straight forward to set up, too.

Yes, I would like to use OpenCores SVN

Great work!!!!
We will try and test your eCos port on the new OpenRISC development board that we are developing right now.

I have added you as a OpenRISC-maintainer and this will give you write-access to the SVN repo. So feel free to check-in your work, and send me an email if you have any problems (marcus at orsoc dot se)


/Marcus

Hi Piotr,

Congratulations! Look forward to seeing this in SVN here.

There is a directory for RTOS in SVN (it has an ecos-2.0 directory), where you can put the eCos 3.0 code. Here is its SVN reference:

http://opencores.org/ocsvn/openrisc/openrisc/trunk/rtos

The main Wiki page has a section pointing to pages about RTOS. Look forward to seeing the eCos page.

http://opencores.org/or1k/OR1K:Community_portal#RTOS

Hope this is useful. Any questions, please ask on IRC (freenode.net, channel #opencores).

Best wishes,

Thank you all for the great response. I have added a small wiki page and checked in the code. Please see the wiki page before using the code.

Regards
Piotr Skrzypek

Hi guys, some little status update from what Piotr wrote:

Since then we posted a short note on our company's blog - http://antmicro.com/blog/2011/10/ecos-3-0-port-for-openrisc/ - linking back here, might make more people bump into this port and openCores ;)

Our site is getting a new version in the coming weeks (hopefully sooner but you know how it is), and we'll try to give more prominence to our involvement in openRISC - and hopefully by then we will have had the chance to get involved more.

Right now we are waiting for a copy of the devboard in order to run the port on actual hardware and see if it works fine - once we are done with it expect some wiki updates and another note on our blog.

Best,
Michael

Hi Michael,

Thanks for the interest and the publicity. That link doesn't work for me, though. Do you have another link to it that might work?

Thanks,

Julius

Hi Julius,

What is happening when you click it? It works for us (we double checked once you reported that - under FF/Chrome/IE, Linux/Windows),,,

Thanks in advance,
Michael

Hi Michael,

It appears fine now. I'm not sure what the issue was when I tried it the last few times.

Thanks again,

Julius

Having attended the OpenRISC talk at FOSDEM, I was very glad to hear that some has recently been maintaining the OpenRISC eCos port; this is really great. But then there was no sign of this work in eCos cvs/bugzilla ... what are the reasons for OpenCores forking eCos rather than doing this work upstream? I think it would be good to bring all the folk interested in eCos on openrisc together :-)

From a quick look at the patchset the OpenRISC fork is based some very old eCos code base (e.g., the ChangeLogs are missing entries from as far back as 2003), but it should not be difficult to bring this up to date I think.

Hi,

I'm glad you liked the talk at FOSDEM.

I haven't personally worked with the eCos port so I don't know in this particular case, but we often keep local versions of tools either because the upstream maintainers haven't accepted our contributions, or we feel ourselves that it's not ready to be integrated in the upstream tree.

If you know more people who would want to work on eCos, I am sure that is a very welcome contribution. Some of our RTOS ports have gotten far too little attention in the shade of Linux

--
Olof Kindgren
______________________________________________
ORSoC
Website: www.orsoc.se
Email: olof.kindgren@orsoc.se
______________________________________________
FPGA, ASIC, DSP - embedded SoC design

Whatever the reason, you ended up with a set of patches based on a 9-year old code base ... anyway.

From 2009 eCos requires (c) reassignment to the FSF, so if any patches were to be merged into eCos, the original authors would need to be traced.

* Piotr's patches seem to be based on the OpenRISC ecos-2.0 fork (in openrisk repo),

* AFAICT, ecos-2.0 in openrisk repo is more or less just an import from the or1k repo,

* There are substantive differences between the or1k version and upstream eCos, but there is no history for these, they seem to have arrived with the initial import, committed by 'phoenix'.

Tomas

Hello

As Olof said, the reason that eCos port is not reported in the upstream tree is that it's not ready. We intend to report it upstream once it passes all unit tests. Right now, there exist a configuration that passes almost all tests (except clock test), but most configurations are buggy. Once we have a stable port, converting the source tree should be quite easy.

Regards
Piotr

Hi guys,

aside from the code-base dispute, we have managed to run the port on the ordb2 devboard now and test it, you can see the blog note describing how to do this here:

http://antmicro.com/blog/2012/03/running-ecos-programs-on-openrisc-ordb2-board/

I think this might be useful to some.

Best regards,
Michael