FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 08-05-2008, 09:12 PM
billium
 
Default FTDI jtag

Has anybody got a usb jtag working in Gentoo, who could give me some
handy tips.


The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
FT2232 USB device.


I have tried to follow the Amotec documentation, but is oldish and not
completely logical.


It all works on WinXP (using VirtualBox) but as it uses gdb I would like
to use Gentoo only.



Many thanks


Billium
 
Old 08-07-2008, 02:30 PM
Jason
 
Default FTDI jtag

billium wrote:
Has anybody got a usb jtag working in Gentoo, who could give me some
handy tips.


The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
FT2232 USB device.


I use a similar device based on the same chip.

I have tried to follow the Amotec documentation, but is oldish and not
completely logical.


It all works on WinXP (using VirtualBox) but as it uses gdb I would like
to use Gentoo only.


The following works for me:

~
[jason@phoenix] $ find /lib/modules/`uname -r`/ -name "*ftdi*"
/lib/modules/2.6.26/kernel/drivers/usb/serial/ftdi_sio.ko
~
[jason@phoenix] $ grep -rni ftdi /usr/src/linux/.config
1693:CONFIG_USB_SERIAL_FTDI_SIO=m
1754:# CONFIG_USB_FTDI_ELAN is not set

It should auto-load when you plug the cable in. Then udev will create
/dev/ttyUSB0 .


hth,

Jason.
 
Old 08-16-2008, 09:26 PM
wireless
 
Default FTDI jtag

billium wrote:
Has anybody got a usb jtag working in Gentoo, who could give me some
handy tips.


The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
FT2232 USB device.



Make sure you have support built into the kernel on the Gentoo
development hosts.

something like this:
make menuconfig
--> device drivers
--> usb support
--> usb serial converter support
--> USB FTDI Single Port Serial Driver

'lsusb' should show something like this:

#lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 006 Device 001: ID 1d6b:0001
Bus 004 Device 003: ID 0403:6001 Future Technology Devices
International, Ltd FT232 USB-Serial (UART) IC



One you have it hooked into your kernel,
Then follow the vendor stuff.


hth,

James
 
Old 08-19-2008, 08:08 PM
Mike Frysinger
 
Default FTDI jtag

On Tuesday 05 August 2008, billium wrote:
> Has anybody got a usb jtag working in Gentoo, who could give me some
> handy tips.
>
> The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
> FT2232 USB device.
>
> I have tried to follow the Amotec documentation, but is oldish and not
> completely logical.
>
> It all works on WinXP (using VirtualBox) but as it uses gdb I would like
> to use Gentoo only.

i havent used that particular device, but the "urjtag" package
(with "libftdi") works just fine with another FT2232 USB device (the gnICE).
no need for kernel drivers.
-mike
 
Old 09-12-2008, 09:32 AM
billium
 
Default FTDI jtag

Mike Frysinger wrote:

On Tuesday 05 August 2008, billium wrote:


Has anybody got a usb jtag working in Gentoo, who could give me some
handy tips.

The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
FT2232 USB device.

I have tried to follow the Amotec documentation, but is oldish and not
completely logical.

It all works on WinXP (using VirtualBox) but as it uses gdb I would like
to use Gentoo only.



i havent used that particular device, but the "urjtag" package
(with "libftdi") works just fine with another FT2232 USB device (the gnICE).
no need for kernel drivers.

-mike


Thanks for the replies.

Jason & James you are writing about the normal ftdi usb-serial drivers,
which I already use for other things.
Mike is correct.

Just in case anybody else searches here is what I did to get it working.

get driver, libftd2xx0.4.13.tar.gz and extract.
get openocd from respository, svn checkout
svn://svn.berlios.de/openocd/trunk/openocd and extract
copy ftd2xx.h & WinTypes.h from driver tar to trunk/src/jtag
copy libftd2xx.so.0.13 to /usr/local/lib & sym link to libftd2xx.so &
libftd2xx.so.0 also create sym links in /usr/lib
in trunk directory
./bootstrap
./configure --enable-ft2232-ftd2xx
make then su to make install
get insight and untar (cannot emerge for arm debugging)
create directory to configure into then
../insight-6.8/configure --target=arm-elf --prefix=/opt/insight-arm
make then su to make install

to run:
openocd -f/pathtoconfigfile
it returns the jtag device found

now run /opt/insight-arm/bin/arm-elf-insight and connect to target on
localhost:3333

I am now able to debug ADuC chips, have not tried loading flash with
this yet.

Billy
 
Old 09-12-2008, 01:46 PM
wireless
 
Default FTDI jtag

billium wrote:

Mike Frysinger wrote:

On Tuesday 05 August 2008, billium wrote:


Has anybody got a usb jtag working in Gentoo, who could give me some
handy tips.

The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
FT2232 USB device.

I have tried to follow the Amotec documentation, but is oldish and not
completely logical.

It all works on WinXP (using VirtualBox) but as it uses gdb I would like
to use Gentoo only.



i havent used that particular device, but the "urjtag" package (with
"libftdi") works just fine with another FT2232 USB device (the
gnICE). no need for kernel drivers.

-mike


Thanks for the replies.

Jason & James you are writing about the normal ftdi usb-serial drivers,
which I already use for other things.
Mike is correct.

Just in case anybody else searches here is what I did to get it working.

get driver, libftd2xx0.4.13.tar.gz and extract.
get openocd from respository, svn checkout
svn://svn.berlios.de/openocd/trunk/openocd and extract
copy ftd2xx.h & WinTypes.h from driver tar to trunk/src/jtag
copy libftd2xx.so.0.13 to /usr/local/lib & sym link to libftd2xx.so &
libftd2xx.so.0 also create sym links in /usr/lib
in trunk directory
./bootstrap
./configure --enable-ft2232-ftd2xx
make then su to make install
get insight and untar (cannot emerge for arm debugging)
create directory to configure into then
../insight-6.8/configure --target=arm-elf --prefix=/opt/insight-arm
make then su to make install

to run:
openocd -f/pathtoconfigfile
it returns the jtag device found

now run /opt/insight-arm/bin/arm-elf-insight and connect to target on
localhost:3333

I am now able to debug ADuC chips, have not tried loading flash with
this yet.

Billy



Thanks for the info, Billy. Maybe this little bit of prose could be
added to the gentoo documentation? I think it would be great to list
JTAG devices/boards/processors that folks have gotten to work with
embedded Gentoo....


just a thought,

James
 
Old 10-26-2008, 06:51 AM
Mike Frysinger
 
Default FTDI jtag

On Friday 12 September 2008, wireless wrote:
> billium wrote:
> > Mike Frysinger wrote:
> >> On Tuesday 05 August 2008, billium wrote:
> >>> Has anybody got a usb jtag working in Gentoo, who could give me some
> >>> handy tips.
> >>>
> >>> The device I have is an Amotec JTAGkey-Tiny which is based on a FTDI
> >>> FT2232 USB device.
> >>>
> >>> I have tried to follow the Amotec documentation, but is oldish and not
> >>> completely logical.
> >>>
> >>> It all works on WinXP (using VirtualBox) but as it uses gdb I would
> >>> like to use Gentoo only.
> >>
> >> i havent used that particular device, but the "urjtag" package (with
> >> "libftdi") works just fine with another FT2232 USB device (the
> >> gnICE). no need for kernel drivers.
> >> -mike
> >
> > Thanks for the replies.
> >
> > Jason & James you are writing about the normal ftdi usb-serial drivers,
> > which I already use for other things.
> > Mike is correct.
> >
> > Just in case anybody else searches here is what I did to get it working.
> >
> > get driver, libftd2xx0.4.13.tar.gz and extract.
> > get openocd from respository, svn checkout
> > svn://svn.berlios.de/openocd/trunk/openocd and extract
> > copy ftd2xx.h & WinTypes.h from driver tar to trunk/src/jtag
> > copy libftd2xx.so.0.13 to /usr/local/lib & sym link to libftd2xx.so &
> > libftd2xx.so.0 also create sym links in /usr/lib
> > in trunk directory
> > ./bootstrap
> > ./configure --enable-ft2232-ftd2xx
> > make then su to make install
> > get insight and untar (cannot emerge for arm debugging)
> > create directory to configure into then
> > ../insight-6.8/configure --target=arm-elf --prefix=/opt/insight-arm
> > make then su to make install
> >
> > to run:
> > openocd -f/pathtoconfigfile
> > it returns the jtag device found
> >
> > now run /opt/insight-arm/bin/arm-elf-insight and connect to target on
> > localhost:3333
> >
> > I am now able to debug ADuC chips, have not tried loading flash with
> > this yet.
>
> Thanks for the info, Billy. Maybe this little bit of prose could be
> added to the gentoo documentation? I think it would be great to list
> JTAG devices/boards/processors that folks have gotten to work with
> embedded Gentoo....

meh ... it'd be duplicating the lists available at the respective upstream
projects (openocd and urjtag) ...
-mike
 
Old 10-26-2008, 06:52 AM
Mike Frysinger
 
Default FTDI jtag

On Friday 12 September 2008, billium wrote:
> get openocd from respository, svn checkout
> svn://svn.berlios.de/openocd/trunk/openocd and extract

why ? we have an openocd-9999.ebuild which fetches straight from the upstream
site ...
-mike
 
Old 10-26-2008, 02:17 PM
Jason
 
Default FTDI jtag

Mike Frysinger wrote:
> On Friday 12 September 2008, billium wrote:
>> get openocd from respository, svn checkout
>> svn://svn.berlios.de/openocd/trunk/openocd and extract
>
> why ? we have an openocd-9999.ebuild which fetches straight from the upstream
> site ...
> -mike

Just tried to emerge it. Here are two small patches to the ebuilds to
make it compile on amd64.

Let me know if it looks good and I'll hit bugzilla.

Jason.

--- /usr/portage/dev-embedded/libftd2xx/libftd2xx-0.4.13-r1.ebuild 2007-12-29 07:27:16.000000000 -0500
+++ /usr/local/portage/dev-embedded/libftd2xx/libftd2xx-0.4.13-r1.ebuild 2008-10-26 10:59:06.000000000 -0400
@@ -12,14 +12,18 @@

LICENSE="as-is"
SLOT="0"
-KEYWORDS="~x86"
+KEYWORDS="~x86 ~amd64"
IUSE="examples"

-DEPEND=""
+DEPEND="amd64? ( app-emulation/emul-linux-x86-baselibs)"
RDEPEND="${DEPEND}"

S="${WORKDIR}/${MY_P}"

+pkg_setup() {
+ has_multilib_profile && ABI="x86"
+}
+
src_install() {
ftdifile="${PN}.so.${PV}"
ftdisym="${PN}.so.0 ${PN}.so"
--- /usr/portage/dev-embedded/openocd/openocd-9999.ebuild 2008-06-04 13:05:41.000000000 -0400
+++ /usr/local/portage/dev-embedded/openocd/openocd-9999.ebuild 2008-10-26 11:12:02.000000000 -0400
@@ -24,6 +24,13 @@
ewarn "You enabled libftdi but not ft2232!"
ewarn "libftdi is only used for ft2232, so this is meaningless!"
fi
+
+ if use ft2232 && has_multilib_profile ; then
+ ABI="x86"
+ if use ftdi ; then
+ die "ft2232 is x86 and ftdi is amd64, choose one or the other!"
+ fi
+ fi
}

src_unpack() {
 
Old 10-26-2008, 07:06 PM
Mike Frysinger
 
Default FTDI jtag

On Sunday 26 October 2008, Jason wrote:
> Mike Frysinger wrote:
> > On Friday 12 September 2008, billium wrote:
> >> get openocd from respository, svn checkout
> >> svn://svn.berlios.de/openocd/trunk/openocd and extract
> >
> > why ? we have an openocd-9999.ebuild which fetches straight from the
> > upstream site ...
>
> Just tried to emerge it. Here are two small patches to the ebuilds to
> make it compile on amd64.

looks good to me, thanks
http://sources.gentoo.org/dev-embedded/libftd2xx/libftd2xx-0.4.13-r1.ebuild?r1=1.1&r2=1.2
http://sources.gentoo.org/dev-embedded/openocd/openocd-9999.ebuild?r1=1.2&r2=1.3
-mike
 

Thread Tools




All times are GMT. The time now is 01:16 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org