From: John Dallaway <john@dallaway.org.uk>
To: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Running ECOS on AT91SAM7X-EK
Date: Thu, 01 Oct 2009 08:32:00 -0000 [thread overview]
Message-ID: <4AC46921.8080109@dallaway.org.uk> (raw)
In-Reply-To: <b18c5f790909300205n69fdee32n9d6a376fc4b5a97d@mail.gmail.com>
Hi Mandeep
Mandeep Sandhu wrote:
> I'm going to run ECOS on my AT91SAM7X-EK eval board.
>
> Any tips/pointers on how to go about running ECOS/sample app on the board?
This board has only 64kB RAM. While it should be possible to install GDB
stubs, using a JTAG debugger for code download and execution will leave
you with more free RAM to experiment with.
> As a start, I'd like to test out the serial port, i.e, run some app
> that writes to the serial port and verify the output on the other end.
> As this board is available in the templates, I plan to build the
> sample serial.c example code against this target and run it.
The serial.c example code should work, but the serial tests in
CYGPKG_IO_SERIAL will provide better verification of serial I/O. Make
sure that you set CYGPRI_SER_TEST_SER_DEV appropriately and that you're
running the ser_filter host tool at the other end of the serial link.
If a particular test does not fit into RAM, you will see a linker error.
You will then need to configure with CYG_HAL_STARTUP == "ROM" and write
the test to Flash for execution on board reset.
> Also, should I use EABI or will ELF do as well?
It would be preferable to use the arm-eabi toolchain if only because it
is likely to produce better optimised code than the older arm-elf toolchain.
I hope this helps...
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2009-10-01 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 9:06 [ECOS] " Mandeep Sandhu
2009-10-01 8:32 ` John Dallaway [this message]
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=4AC46921.8080109@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mandeepsandhu.chd@gmail.com \
/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).