From: "G.Muruganandam" <gmuruga@gdatech.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] MPC555 board hardware configuration
Date: Thu, 04 May 2006 17:09:00 -0000 [thread overview]
Message-ID: <7.0.0.16.0.20060504100029.01d20e68@gdatech.com> (raw)
In-Reply-To: <E4E80F1F1B58FB4C923D2BCC860530A854333B@il06exm63.ds.mot.co m>
Hello,
I have a customer board based on PB-0555 reference platform ( MPC555).
I have copied the debug monitor from the PB-0555 reference platform to the
target board's internal flash.
I am using Metrowerks codewarrier IDE and Wiggler debugger for the test and
development.
Working condition:
============
If I connect the wiggler debugger to the target board's BDM connector and
run it using Metrowerks codewarrier , the debug monitor gets executed from the
internal flash, and there are serial output from the board. I mean,
the code is
executed from the internal flash.
Non working condition:
==============
if I remove the wiggler debugger from the target board and power
cycle the board,
I am not seeing any serial output from the board.
So I would like to know whether I am missing anything in terms of
reset strap options
or hardware configurations in the board.
Pl let me your suggestions.
Thanks
G.Muruganandam
-----------------------------------------------------------------------------------------------------------
"Get 99% spam blocking without tuning, or it's FREE. http://epg.propel.com"
-----------------------------------------------------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2006-05-04 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 16:11 [ECOS] Write to Data bus in MPC565 Rycerz Roman-G11565
[not found] ` <E4E80F1F1B58FB4C923D2BCC860530A854333B@il06exm63.ds.mot.co m>
2006-05-04 17:09 ` G.Muruganandam [this message]
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=7.0.0.16.0.20060504100029.01d20e68@gdatech.com \
--to=gmuruga@gdatech.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).