public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tim Drury <tdrury@siliconmotorsports.com>
To: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] eb40a target submitted
Date: Mon, 22 Jul 2002 11:14:00 -0000	[thread overview]
Message-ID: <200207221413.05569.tdrury@siliconmotorsports.com> (raw)
In-Reply-To: <1027360998.25316.60.camel@hermes.chez-thomas.org>


> >
> > 2. When building the tests, the resulting elf image is not runnable
> > by redboot.  It has to be converted to srecs first.  Here is how
> > I built the tests:
>
> What's the problem?  What errors are you getting?
>
> If arm-elf-objcopy can read the file, GDB should be able to as well,
> since they use the same library for reading ELF images.

It's not gdb reading it, it's redboot.  Redboot (ROMRAM) appears
to load the elf image, but 'g' does nothing.  Looking at my (kick ass!)
logic analyzer, it's caught in a tight loop of running off in the sticks
then jumping back into the exception hander code in low memory.
I can look into this deeper if necessary.

> > A few things I love to see here: a) what is the proper way to
> > make the process create srecs instead of elf images?
>
> Why would you want to do this?  It seems to me that effort should be
> spent figuring out what problems you are having with GDB.

Well for one, the srecs are much smaller than the elf files so they load
much faster at 38kbaud.  But mainly because of the problem I'm having
with elf images.

>
> > b) can we have each test end by returning to redboot so the
> > target board doesn't have to be reset after each run?
>
> You could easily define it to work this way.  All tests go to
> 'cyg_test_exit()', which is currently defined as a hard loop.

I'd like to do this.  What I'm afraid of doing is making a change to the
entire ecos tree and screwing someone up.  Can I do this in such a
way that only the eb40a (or at91) targets do this?  Or would anyone
care whether I make the change to the entire tree?

> > c) can we automate this in Linux?

The running of _all_ the test cases.  I've been really spoiled with java
and junit.  junit defines a interface that all your test cases must implement,
then running junit's test runner program executes all your test cases
for you.  I'm looking at some c-equivalent programs right now, but that
won't help the test cases that have already been written.

-tim


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

  reply	other threads:[~2002-07-22 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22 10:37 Tim Drury
2002-07-22 11:03 ` Gary Thomas
2002-07-22 11:14   ` Tim Drury [this message]
2002-07-22 11:24     ` Gary Thomas
2002-07-22 11:28       ` Mark Salter
2002-07-22 11:32         ` Gary Thomas
2002-07-22 19:30 ` Tim Drury
2002-07-23 10:40   ` James
2002-07-24  7:18     ` Tim Drury
2002-07-22 15:20 GREGHOL

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=200207221413.05569.tdrury@siliconmotorsports.com \
    --to=tdrury@siliconmotorsports.com \
    --cc=ecos-discuss@sources.redhat.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).