Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-30 Thread Antonio Borneo
On Thu, Dec 30, 2010 at 3:42 PM, Peter Stuge wrote: > Jon Masters wrote: >> 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 >>

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-29 Thread Peter Stuge
Jon Masters wrote: > 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

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-29 Thread Øyvind Harboe
Try with OpenOCD master branch now. Should be fixed. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Jon Masters
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: > > > > > > > > > > > This is bogus ... I'd prefer extending the detection to be able to > > > > identify imx51 in a more preci

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Marek Vasut
On Monday 13 December 2010 10:12:57 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: > > > > > > > > > > This is bogus ... I'd prefer extending the detection to be able to > > > > identify imx51 in a more precise

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Jon Masters
On Mon, 2010-12-13 at 10:05 +0100, Marek Vasut wrote: > On Monday 13 December 2010 10:00:05 Jon Masters wrote: > > > > > > > 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 br

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Marek Vasut
On Monday 13 December 2010 10:00:05 Jon Masters wrote: > On Mon, 2010-12-13 at 09:45 +0100, Marek Vasut wrote: > > On Monday 13 December 2010 03:27:17 Jon Masters wrote: > > > Some logic is added to detect CPU cores that report an incorrect ARM > > > DAP (Debug Access Port, exposed behind something

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Jon Masters
On Mon, 2010-12-13 at 09:45 +0100, Marek Vasut wrote: > On Monday 13 December 2010 03:27:17 Jon Masters wrote: > > Some logic is added to detect CPU cores that report an incorrect ARM DAP > > (Debug Access Port, exposed behind something called an ICEPick which > > sits on the JTAG chain and allows

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Marek Vasut
On Monday 13 December 2010 03:27:17 Jon Masters wrote: > On Wed, 2010-11-24 at 23:59 -0500, Jon Masters wrote: > > Has anyone managed to get the TinCanTools Flyswatter working with the > > XM? I did with the original Beagle, but upstream OCD does this with XM: > > > > [...@constitution openocd]$ s

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-12 Thread Jon Masters
On Wed, 2010-11-24 at 23:59 -0500, Jon Masters wrote: > Has anyone managed to get the TinCanTools Flyswatter working with the > XM? I did with the original Beagle, but upstream OCD does this with XM: > > [...@constitution openocd]$ sudo /usr/local/bin/openocd > -s /usr/local/lib/openocd > -f /usr