From: "Алёна Никифорова" <alyona.nikiforova@planar.chel.ru>
To: insight@sourceware.org
Subject: Insight questions
Date: Tue, 16 Oct 2012 07:54:00 -0000 [thread overview]
Message-ID: <507D12BA.5040401@planar.chel.ru> (raw)
Hello!
I read about the product Insight GDB on
http://sources.redhat.com/insight/aboutus.php, looked up all FAQs, but
still have a question.
There is an issue that I connected the board to be debugged to COM3 on
my computer and try to launch "run" in Insight GDB, but it doesn't
recognize COM3 and says that the file "COM3" was not found or that a
malformed answer got.
The reason why I'm sure that it is exactly COM3 is that I can connect to
the board via Terminal ("PUTTY") with parameters COM3 and 115200 baudrate.
Thanks in advance, I would really appreciate any help.
--
Regards,
Nikiforova Alyona
PLANAR, LLC
www.planar.chel.ru
next reply other threads:[~2012-10-16 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:54 Алёна Никифорова [this message]
2012-10-16 13:56 ` Keith Seitz
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=507D12BA.5040401@planar.chel.ru \
--to=alyona.nikiforova@planar.chel.ru \
--cc=insight@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).