public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@gmx.net>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Dependency between eCos and RedBoot
Date: Mon, 08 Apr 2013 09:07:00 -0000	[thread overview]
Message-ID: <516288DC.3050505@siva.com.mk> (raw)
In-Reply-To: <trinity-66c4e736-1abb-4c7c-afdd-dee3758b9298-1365371708219@3capp-gmx-bs37>

Hi Lukas

You don't need to take special care for RedBoot during porting process.
Simple "hello world" application is enough, and for me more convenient,
to get hal_diag in order. Once you have hal_diag (and of course clocking
and basic configuration) RedBoot should compile and run without
problems. Then, once you add Ethernet driver, you should be able to
telnet to RedBoot.

Ilija

On 07.04.2013 23:55, Lukas Riezler wrote:
> Hello ecos-guys :-)
>
> I have modified both the variant HAL and platform HAL in a minimal way, to get eCos ported
> on my FM3 (IAR KickStart Kit: MB9BF506R-SK).
> Modifying the CDL-Files will be my next step.
>
> But now I have a question about the dependency between eCos and RedBoot.
> If I'm rigt, Redboot comes with two elementary functions:
> - bootstrapping
> - debbuging
>
> My eval board has a kind of JTAG, so RedBoot's debugging facility isn't really needed by me. (?)
> In the documentation and the book it's the suggestion first to run RedBoot.
> But is RedBoot really essential to get eCos run on my board? Or are there any other ways to get this goal?
> I don't have any experience with bootsrapping/-loading because I'm quite new in this
> hardware-closeness business. Maybe I can burn ecos into flash? But I think for developing this won't be
> the best way, is it?
>
> I have built some libraries for test cases with the config-tool, but I have never seen any elf-file which
> I could load on my board - only if I used the RedBoot package! In this case an elf-file was generated.
> Okay, what I have now is "redboot.elf".
> So I have to load RedBoot on my board. But how does RedBoot "load" my minimal eCos application on the
> board?
>
> Is the following chain of thougt correct?
> 1) load "redboot.elf" on the board
> 2) RedBoot can handle the generated ecos-file "libtarget.a" (and eCos will be started in this way?)
>
> Is it possible that anybody throws some light in this issue? :)
>  
> With kind regards,
> Lukas
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2013-04-08  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 21:55 Lukas Riezler
2013-04-08  7:28 ` Ross Younger
2013-04-08  9:07 ` Ilija Kocho [this message]
2013-04-10  7:06 ` AW: " Richard Rauch

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=516288DC.3050505@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=lukas.riezler@gmx.net \
    /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).