From: Eugene Surovegin <ebs@ebshome.net>
To: Laurent Pinchart <laurent.pinchart@technotrade.biz>
Cc: "Morrison, Tom" <tmorrison@empirix.com>, linuxppc-embedded@ozlabs.org
Subject: Re: JTAG emulator for MPC8548E (v2)
Date: Wed, 24 Jan 2007 09:19:17 -0800 [thread overview]
Message-ID: <20070124171917.GB31703@gate.ebshome.net> (raw)
In-Reply-To: <200701241206.18167.laurent.pinchart@technotrade.biz>
On Wed, Jan 24, 2007 at 12:06:17PM +0100, Laurent Pinchart wrote:
> Hi Eugene,
>
> > > The new unit works *mostly* fine. No debugging issue (not that I use it
> > > that much anyway, now that the board boots Linux), but still a flash
> > > programming issue. Programming the target parallel NOR flash works in
> > > slow JTAG mode, but not in faster mode using the internal workspace. I
> > > reported the problem several months ago and still haven't received any
> > > solution.
> >
> > Most likely problem isn't in BDI but in your setup. Depending on
> > the particular chip model, to be able use workspace you must have
> > initialized memory first. In fact, I'm pretty sure you haven't
> > configured chip correctly to make workspace usable. I've been using
> > BDI with various PowerPC and MIPS SoCs for many years. It's an excellent
> > tool, you just have to use it correctly.
>
> I wish it was that simple.
Sorry, but it is. It's a low level tool which requires deep knowledge
of the chip.
> It is probably a target processor configuration
> issue, as I can use the workspace if
>
> a) the target flash has already been programmed with U-Boot
> b) the BDI-2000 is misconfigured and fails to stop the target processor at
> startup.
>
> I can thus use the workspace when U-Boot initializes the processor.
Wow, so you knew it wasn't BDI but a configuration problem from the
start. So it all was just a FUD, how low.
>
> I had a look at U-Boot code and tried to initialize the processor registers
> with the same values, without luck. I asked Abatron's French distributor for
> technical support, and they haven't been able to help me. They made me try
> lots of different initialization sequences. Several people online sent me
> their configuration file, and none of them worked for me.
>
> So, there must be a configuration problem somewhere, but even Abatron's
> technical support haven't been able to find it. That's why I complained about
> their support in my e-mail.
In your original e-mail you made it look like BDI has a bug in it,
which in fact isn't true. Bad support might be a concern, I agree, but
this doesn't make a tool bad, IMHO.
--
Eugene
next prev parent reply other threads:[~2007-01-24 17:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 17:07 JTAG emulator for MPC8548E (v2) Morrison, Tom
2007-01-23 17:56 ` Grant Likely
2007-01-23 18:02 ` Morrison, Tom
2007-01-23 18:14 ` Ben Warren
2007-01-24 7:57 ` Laurent Pinchart
2007-01-24 10:35 ` Eugene Surovegin
2007-01-24 11:06 ` Laurent Pinchart
2007-01-24 12:29 ` Morrison, Tom
2007-01-24 17:19 ` Eugene Surovegin [this message]
2007-01-24 18:28 ` Mark A. Greer
2007-01-24 19:38 ` Bill Gatliff
2007-01-25 9:24 ` Laurent Pinchart
2007-01-24 22:02 ` Frank
2007-01-24 20:49 ` Wolfgang Denk
2007-01-25 9:17 ` Laurent Pinchart
2007-01-23 18:39 ` Michael Galassi
-- strict thread matches above, loose matches on Subject: below --
2007-01-25 21:56 Ramirez-Ortiz, Jorge
2007-01-25 22:31 ` Dan Malek
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=20070124171917.GB31703@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=laurent.pinchart@technotrade.biz \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tmorrison@empirix.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