From: "John" <john@imining.com.tw>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Can not connect to target x86 pc board
Date: Sun, 18 Feb 2001 19:19:00 -0000 [thread overview]
Message-ID: <NDBBKMEDOKEJKFEDGCLOAEKICDAA.john@imining.com.tw> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
Hi all:
I Have used Configuration Tool to make a boot floppy
(hardware --> i386 pc target ; package --> stubs)
and a eCos kernel without conflicts
(hardware --> i386 pc target ; package --> default).
I insert the boot floppy into my target Intel PII pc board and use a cable to connect my host(COM1) and target(COM1).
After booting my target, the target monitor shows
++$T0508:e03b0000;04:e00f0000;#44
And then I use Configuration Tool
Tools-->Run Tests-->Run
to test it and the following output message shows
*** 10:54:31 Run started
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i586-pc-cygwin --target=i386-elf"...
(gdb) set height 0
(gdb) set remotedebug 0
Warning: command 'set remotedebug' is deprecated.
Use 'set debug remote'.
(gdb) set remotebaud 38400
(gdb) target remote com1
Remote debugging using com1
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout
(gdb) load
You can't do that when your target is `exec'
(gdb) break cyg_test_exit
Breakpoint 1 at 0x138df: file //d/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 116.
(gdb) break cyg_assert_fail
Function "cyg_assert_fail" not defined.
(gdb) break cyg_test_init
Breakpoint 2 at 0x137fb: file //d/PROGRA~1/REDHAT~1/eCos/packages/infra/v1_3_1/src/tcdiag.cxx, line 62.
(gdb) cont
The program is not being run.
What's wrong?
Thanks in advance.
----
ÃÃȬÂõ
John Hsieh
µo²{ªÃ°ê»ÃªÃ¥÷¦³Â¤½¥q
iMining Technology Co., Ltd.
john@imining.com.tw
TEL: 886-2-27235122
FAX: 886-2-27232287
www.imining.com.tw
next reply other threads:[~2001-02-18 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 19:19 John [this message]
2001-02-18 20:38 Jitendra kanitkar
2001-02-18 22:30 ` John
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=NDBBKMEDOKEJKFEDGCLOAEKICDAA.john@imining.com.tw \
--to=john@imining.com.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).