I think it was operator error. I can't reproduce the problem.
On Mon, Sep 27, 2010 at 2:06 PM, John Rigby wrote:
> I'm using OpenOCD and a Flyswatter to debug some new code that is
> based on the u-boot-next tree. The board is a Beagle C4. The problem
> that I am seein
I'm using OpenOCD and a Flyswatter to debug some new code that is
based on the u-boot-next tree. The board is a Beagle C4. The problem
that I am seeing is that I can not access memory from the telnet
sesson to OpenOCD or from an attached gdb session. I believe the
problem is that in the -next u-
Doh! Working now. I had the beagle board adapter plugged into the
beagle instead of the flyswatter.
On Tue, Dec 1, 2009 at 1:49 PM, John Rigby wrote:
> I already tried that:
>
> $ telnet localhost
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
>
that I got from tincantools. And I have all the
pin 1s matched up.
On Tue, Dec 1, 2009 at 1:41 PM, David Brownell wrote:
> On Tuesday 01 December 2009, John Rigby wrote:
>> I'm trying to use OpenOCD with a Flyswatter and a beagleboard and I get this:
>>
>> # openocd -
I'm trying to use OpenOCD with a Flyswatter and a beagleboard and I get this:
# openocd -f ./tcl/interface/flyswatter.cfg -f ./tcl/board/ti_beagleboard.cfg
Open On-Chip Debugger 0.4.0-dev-00740-ga65e75e (2009-12-01-12:05)
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.htm
The attached config for imx25 works with your latest. Thanks for you
efforts.
On Wed, Oct 7, 2009 at 4:03 PM, David Brownell wrote:
> On Wednesday 07 October 2009, John Rigby wrote:
> > If the hard coded mask of 0x3 and value of 0x1 are changed to
> > ir_capture_mask and i
If the hard coded mask of 0x3 and value of 0x1 are changed to
ir_capture_mask and ir_capture_value respectively then mx25,31,35
should work. Here is an untested patch. The diagnostic is wrong
since it still has the hardcoded 0x..1 expected value in it. Sorry I
intended to send a tested patch yes
I agree that using the expected capture value makes a lot more sense than
using the zero id. I'll send a patch later today.
On Tue, Oct 6, 2009 at 12:49 AM, David Brownell wrote:
> On Saturday 03 October 2009, John Rigby wrote:
> > You were right about the ir lengths, but I a
wrote:
> On Saturday 03 October 2009, John Rigby wrote:
> > > is there; it looks bizarre, that *is* an LSB of b0001, it's
> > > the next bits that are odd.
> >
> > This diagnostic is misleading. It does not give the position where it
> was
> > expec
David,
Thanks for the info. I'm slowly making progress.
On Fri, Oct 2, 2009 at 4:58 AM, David Brownell wrote:
..
>
> I'm not sure why that diagnostic
>
> Error: imx25.cpu: IR capture error; saw 0x3E1011 not 0x..1
>
> is there; it looks bizarre, that *is* an LSB of b0001, it's
> the next
I'm trying to create a config file for a Freescale i.mx25. Using info from
a number of other i.mx platform configs and the reference manual and some
trial and error I have come up with the attached file. When I use it I get
this:
$ openocd --file flyswatter.cfg --file imx25.cfg
Open On-Chip Deb
11 matches
Mail list logo
