public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Robert Brusa <bob.brusa@gmail.com>
To: MailingList:ecos-discuss <ecos-discuss@ecos.sourceware.org>;
Subject: [ECOS] run-tests in configtool
Date: Thu, 12 Jun 2008 13:09:00 -0000	[thread overview]
Message-ID: <op.ucmz5zbqkeg3uf@debi27.local.lan> (raw)

Hi
Using configtool on my debian etch system, I built an ecos and tests using  
the defaults for the AT91SAM7X-EK board. Then I click on run-tests and  
configure configtool to download using tty1 (where the serial debug-I/F of  
my board is connected). The output I get in the status column of the  
summary register of the "run tests-view" alway reads "NoResult". I did the  
tests with several programs - alsways "NoResult" and this in no time!

I then checked the serial i/o on tty1 with an oscilloscope and found: No  
download and no answer from the board. I also checked the interface by  
sending characters with minicom. The I/F is ok.

Then I changed the download interface to 192.168.0.21:2001, the address  
and port where my BDI2000 is connected. I launched wireshark, set its  
filter for this address and run again a test. Wireshark did not detect any  
packets to/from the BDI2000.

My first question: Why does configtool not tell me that it has no contact  
with the target. After all, there is a time out specified and it should at  
least hang until this timeout has elapsed. Thank you for your helpful  
answers and regards.

Second question: How can I fix the problem and run these tests?

Robert





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

             reply	other threads:[~2008-06-12 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 13:09 Robert Brusa [this message]
2008-06-12 14:11 ` Andrew Lunn
2008-06-16 11:02 ` [ECOS] " John Dallaway

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=op.ucmz5zbqkeg3uf@debi27.local.lan \
    --to=bob.brusa@gmail.com \
    --cc=ecos-discuss@ecos.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).