On Mon, 2010-12-13 at 04:12 -0500, Jon Masters wrote:
> On Mon, 2010-12-13 at 10:05 +0100, Marek Vasut wrote:
> > On Monday 13 December 2010 10:00:05 Jon Masters wrote:
> 
> > > <snip commented out code fixup>
> > > 
> > > > This is bogus ... I'd prefer extending the detection to be able to
> > > > identify imx51 in a more precise way.
> > > 
> > > Sure. I was just applying a hack in my local git branch for running the
> > > BeagleBoard-xM here with my Flyswatter. That was neither a patch nor
> > > intended for use other than with the xM if someone else is using a
> > > release of OpenOCD since the beginning of November. I really agree with
> > > you that the correct fix is to better determine an IMX51 for fixup.
> > > 
> > > FWIW, I got this wrong at first. I read the archives and assumed that
> > > the BeagleBoard was in need of some fixup, but actually it's fine. It's
> > > the logic intended to fixup the other part that is breaking Beagle.
> > 
> > Can you try checking how can that be fixed ? I believe it'd just be a 
> > matter of 
> > adding a few more identification information (check how the fixup loop 
> > detects the 
> > CPU, try extending it so it doesn't break beagle).
> 
> Sure. I don't have time today, but when I get chance this week I will
> take a look at better distinguishing the parts (I have only several of
> the Beagles here, but not the offending Freescale part so can send you a
> patch to test when I get chance to look at it).

Oh, on a randomly off-topic engineering note, I'd love to know why the
Flyswatter contains component Q1 (the NPN transistor) so that to do a
system reset you don't just pull nSRST low but actually set A_nSRST high
and have that go into Q1, which results in pulling system reset low
indirectly. Is this because we might end up sinking a lot of current?
Does anyone with an EE/circuit design background happen to know?

Jon.


_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to