From: niky <b4506051@csie.ntu.edu.tw>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: I cant use gdb stubs to load hello
Date: Wed, 06 Dec 2000 03:42:00 -0000 [thread overview]
Message-ID: <200012061142.TAA15277@ntucst.csie.ntu.edu.tw> (raw)
>Have you ever tried to download any test, which comes with eCos. Try
>
>make tests
>
>in your ecos build directory to compile the tests. After this, download one
>of the test applications located in the install/tests/ directory. If this
>works, maybe your makefile for building your hello application is not ok.
>
>Chris
After I make tests, I got three test files: cache, context, intr.
I try all of them.
When I download cache to the target pc, the pc reboot.
I download context/intr to the target pc, it cant finish, and I see
$OK#9a repeat from the serial port.
next reply other threads:[~2000-12-06 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 3:42 niky [this message]
2000-12-06 3:52 ` Christian Plessl
2000-12-09 6:38 [ECOS] " niky
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=200012061142.TAA15277@ntucst.csie.ntu.edu.tw \
--to=b4506051@csie.ntu.edu.tw \
--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).