From: "Sid" <sid@siddhartha.8m.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: MPC860 - minicom
Date: Mon, 26 Feb 2001 11:33:18 +0800 [thread overview]
Message-ID: <004501c09fa4$df5fe2f0$2501000a@sid> (raw)
Hi,
I have an MBX860 board.
After powering up the board, lights DS1 and DS2 light up.
When I connect the board to the serial port of my host via COM/SMC1, minicom
shows a target online, but I do not get a debug prompt on minicom. And there
seems to be no activity at all on the board.
Is this a common problem? What steps should I take for troubleshooting?
Thank you for your time.
regards,
Sid
--
sid@siddhartha.8m.com
Q: "Don't fret, Riker. My good fortune is your good fortune."
--"Deja Q", Stardate 43539.1
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-02-26 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 3:33 Sid [this message]
2001-02-26 12:25 ` MPC860 - minicom Karl-Heinz Krempels
2001-02-26 17:06 ` MBX860 " Sid
2001-02-28 2:14 ` MBX860 - minicom trouble continues Sid
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='004501c09fa4$df5fe2f0$2501000a@sid' \
--to=sid@siddhartha.8m.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).