On Mon, Apr 15, 2013 at 4:39 PM, Grant Edwards <[email protected]>wrote:
> On 2013-04-13, Andreas Fritiofson <[email protected]> wrote:
> > On Fri, Apr 12, 2013 at 11:59 PM, Grant Edwards <
> [email protected]>
> > wrote:
> >
> >> On 2013-04-12, Grant Edwards <[email protected]> wrote:
> >>
> >> > I'm trying to use an Olimex JTAG TINY with an NXP LPC1830 board.
> >> > It's a GIT snapshot from earlier today:
> >> >
> >> > openocd-code-441914978d1b0debc2c40ef5a660165d53baad27.tar.gz
> >>
> >
> > Where does this snapshot come from?
>
> I followed think link on http://openocd.sourceforge.net/ to the GIT
> repository and clicked the "download a snapshot" link at the top of
> the page:
>
> http://sourceforge.net/p/openocd/code/ci/master/tree/
>
> I asked on the mailing list a few days ago about using 0.6.1 vs git
> head, and was told to use a git snapshot. So I used a git snapshot.
>
> > The bootstrap script seems to require a
> > real git repo, not just a snapshot.
>
> Apparently so.
>
> > It's better supported and probably easier to do a git clone instead
> > of messing with snapshots.
>
> Well, downlaoding a snapshot requires a single click and doesn't
> require that you have git installed, so I don't think it's "easier".
> It does seem to be better supported. :)
Yeah sure, tools and basic git knowledge were assumed. Considering that
you'll have to get the submodules separately if you get a snapshot (as you
noticed), I still think it's easier to
sudo apt-get install git (and libusb-1.0-0-dev libftdi-dev while you're at
it)
git clone git://git.code.sf.net/p/openocd/code openocd
bootstrap, configure and make
Of course, still assuming knowledge (and a suitable OS).
The real win is when you decide to update to get some recent fixes: git
pull.
Or when you want to contribute a fix you've had to make; just set up a
gerrit account (once), commit your fix and git push.
> Rats. I forgot to enable ft2232 support when I ran the ./configure.
> >> After reconfiguring with --enable-ft2232_libftdi it looks like it's
> >> working.
> >
> > The ft2232 driver is more or less deprecated. It's slow and has a
> > number of problems.
>
> > I recommend using --enable-ftdi instead of (or in addition to)
> > --enable-ft2232_libftdi.
>
> Um, OK, but how can you use an Olimex JTAG tiney without an ft2232
> driver when that device is based on the ft2232?
> Don't you still end up with an ft2232 driver?
When we say driver we mean the interface driver inside OpenOCD. Lousy name,
since they're easily confused with operating system drivers with similar
names.
OpenOCD has several interface (adapter) drivers such as jlink, ft2232,
ftdi, rlink etc. All needs to be explicitly enabled at configure time.
The ftdi driver is a rewrite of the old ft2232 driver. Both support all
types of FTDI chips with an MPSSE mode (FT2232, FT232H, FT4232, ...)
The old ft2232 driver could talk to the hardware through either libftdi (in
turn using libusb) or the proprietary D2XX library from ftdichip (in turn
using libusb under linux, or the FTDI operating system drivers under
Windows).
The new ftdi driver uses libusb directly to talk raw USB with the chip. So
no, there's no ft2232 specific code involved other than the ftdi driver in
OpenOCD.
/Andreas
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
