public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Koco <ilijak@siva.com.mk>
To: Ilija Koco <ilijak@siva.com.mk>
Cc: "C. Adam Lamb" <alamb@ilxlightwave.com>,  ecos-devel@sourceware.org
Subject: Re: Porting eCos to STR9
Date: Sat, 17 Jun 2006 09:59:00 -0000	[thread overview]
Message-ID: <4493D24D.2040403@siva.com.mk> (raw)
In-Reply-To: <4493CFA9.5050902@siva.com.mk>

Ilija Koco wrote:
> C. Adam Lamb wrote:
>   
>>> I did my 1st port recently and I had same dillema. I choosed the one
>>> with most simillar booting sequence and memory structure. I was looking
>>> for peripheral simillarity too, but unfortunatelly i found no chips with
>>> peripharals simillar to mine.
>>>     
>>>       
>> How long did it take you to get the basic part (enough to get an LED
>> blinking, for example) of your first port going?  A few weeks?  
>>   
>>     
> Well' my biggest effort was to consume and compile vast amount of
> documentation. While having experience with porting (proprietary) OS and
> some other processors I was completely novice at ARM and eCos. So I
> spent about 2 week in reading, waiting for my PEEDI.
>
> Then I had to test my hardware (I hadn't off the shelf evaluation board)
> during which time I also got familiar with ARM and found out that eCos'
> downloadable GCC doesn't support big endian. You may not encounter this
> issue but if your chip is BE you will need to build your GNU tool chain
> <http://ecos.sourceware.org/build-toolchain.html>
>
> Once I got this I started porting and within 3-4 weeks I got 1st message
> at serial line through hal_diag functions (I was familiar with similar
> serial port to one I ported).
>
> Porting process is very well described in "eCos reference" and
> "Component writer's guide" and also explained (with example) here
> http://www.phptr.com/browse/product.asp?product_id={0BEE58C4-0812-4B13-9B8C-A0FC31A4C02F}
>
>   
I placed wrong link, sorry!

It should be this
http://www.phptr.com/bookstore/product.asp?isbn=0130354732&redir=1

And here in PDF
http://www.informit.com/content/downloads/perens/0130354732.pdf

>> Anybody have any idea about how much time I should expect to take to just
>> get the basics running (assuming I'm an average guy) before I start on all
>> of the peripherals?
>>
>> Adam
>>
>>
>>   
>>     
>
>
>   

  reply	other threads:[~2006-06-17  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 20:17 Intention to Port " C. Adam Lamb
2006-06-14 21:09 ` Andrew Lunn
2006-06-14 21:15   ` Re[2]: " Evgeny Belyanco
2006-06-14 21:33     ` Andrew Lunn
2006-06-15  8:54   ` Ilija Koco
2006-06-15 14:55     ` C. Adam Lamb
2006-06-15 15:12       ` Andrew Lunn
2006-06-15 21:56         ` Joakim Langlet
2006-06-15 22:11           ` C. Adam Lamb
2006-08-28 10:29           ` fabio
2008-07-28  6:48             ` Mohd_Arif
2006-06-16  9:44       ` Ilija Koco
2006-06-16 14:47         ` Porting " C. Adam Lamb
2006-06-17  9:47           ` Ilija Koco
2006-06-17  9:59             ` Ilija Koco [this message]
2006-08-27 15:51 ` Intention to Port " Evgeny Belyanco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4493D24D.2040403@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=alamb@ilxlightwave.com \
    --cc=ecos-devel@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).