I did that too. I uninstalled the drivers and installed them again
and I tried using it with my desktop instead of my laptop and it still
didn't work.

--- In A..., "predator_mf2000"
wrote:
>
> Well, all I want to do is help you, since I've worked with this JTAG
> (purchased from Olimex),
> and I had no problems using it.
> Its a shot in the dark, but try reinstalling FTDI's drivers or change
> the USB port
>
> --- In A..., "Ryan" wrote:
> >
> > The numbers in the device manager match the numbers in my .cfg file...
> > I got really excited for a minute when I read your post but it doesn't
> > seem to be the answer.
> >
> >
> > --- In A..., "predator_mf2000"
> > wrote:
> > >
> > > Hi Ryan,
> > >
> > > Try replacing in "at91sam7s256-armusbocd.cfg" this line:
> > > ft2232_vid_pid 0x15BA 0x0004
> > > with this one:
> > > ft2232_vid_pid 0x0403 0xcff8
> > >
> > > If it doesn't work, open your Device Manager, you should see two
> > > devices on the olimex jtag, one should be a virtual COM port, the
> > > second one should be FTDI device (or something like that), click on
> > > it's properties and see the first property (Device instance ID) and
> > > see what the PID and the VID numbers are (eventually use them in
your
> > > cfg for Open OCD.
> > >
> > > PS: Sorry for the mixed up explanaion, I'm not in front of my PC
right
> > > now :)
> > >
> > > --- In A..., "Ryan" wrote:
> > > >
> > > > I have also tried connecting from the windows command line
with the
> > > > following command:
> > > >
> > > > openocd-ftd2xx -f at91sam7s256-armusbocd.cfg
> > > >
> > > > This is the error that I get:
> > > >
> > > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05
> 09:00
> > > > CEST)
> > > > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> > > device: 2
> > > > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> > > >
> > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD
JTAG
> > > TINY A
> > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD
JTAG
> > > TINY B
> > > >
> > > > Here is the "at91sam7s256-armusbocd.cfg" file:
> > > >
> > > > #define our ports
> > > > telnet_port 4444
> > > > gdb_port 3333
> > > >
> > > > #commands specific to the Amontec JTAGKey
> > > > interface ft2232
> > > > ft2232_device_desc "Olimex OpenOCD JTAG TINY"
> > > > ft2232_layout "olimex-jtag"
> > > > ft2232_vid_pid 0x15BA 0x0004
> > > > jtag_speed 2
> > > > jtag_nsrst_delay 200
> > > > jtag_ntrst_delay 200
> > > >
> > > > #reset_config [combination] [trst_type] [srst_type]
> > > > reset_config srst_only srst_pulls_trst
> > > >
> > > > #jtag_device instruction>
> > > > jtag_device 4 0x1 0xf 0xe
> > > >
> > > > #daemon_startup <'attach'|'reset'>
> > > > daemon_startup reset
> > > >
> > > > #target [variant]
> > > > target arm7tdmi little run_and_init 0 arm7tdmi_r4
> > > >
> > > > #run_and_halt_time
> > > > run_and_halt_time 0 30
> > > >
> > > > The hardware appears to be properly installed when I look in the
> > > > device manager. I just don't know whats going on.
> > > >
> > > >
> > > > --- In A..., "Ryan" wrote:
> > > > >
> > > > > I am stepping through the "Using Open Source Tools for AT91SAM7S
> > Cross
> > > > > Development" tutorial by James P. Lynch and I am getting hung up
> > when
> > > > > I try to program the board. I keep getting the following error:
> > > > >
> > > > >
> > > > > **** Build of configuration MinGW GCC for project
> > > > > demo_at91sam7_blink_flash ****
> > > > >
> > > > > make -k program
> > > > > Flash Programming with OpenOCD...
> > > > > 'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
> > > > > 'c:/Program
> > > > >
> > >
> Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
> > > > > # program the onchip FLASH here
> > > > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05
> > 09:00
> > > > > CEST)
> > > > > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> > > > device: 2
> > > > > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> > > > >
> > > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD
> JTAG
> > > > TINY A
> > > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD
> JTAG
> > > > TINY B
> > > > > make: *** [program] Error 1
> > > > >
> > > > > I think that the problem lies in my
> > > > > at91sam7s256-armusbocd-flash-program.cfg file but I am not
> sure what
> > > > > needs to change. I am using the AT91SAM7S-EK Evaluation
Kit. Can
> > > > > someone please point me in the right direction?
> > > > >
> > > > > P.S. For those of you following my "Loaded SAM-BA in the wrong
> spot"
> > > > > post, this is not the same board.
> > > > >
> > > >
> > >
> Start a New Thread

Well, all I want to do is help you, since I've worked with this JTAG
(purchased from Olimex),
and I had no problems using it.
Its a shot in the dark, but try reinstalling FTDI's drivers or change
the USB port

--- In A..., "Ryan" wrote:
>
> The numbers in the device manager match the numbers in my .cfg file...
> I got really excited for a minute when I read your post but it doesn't
> seem to be the answer.
> --- In A..., "predator_mf2000"
> wrote:
> >
> > Hi Ryan,
> >
> > Try replacing in "at91sam7s256-armusbocd.cfg" this line:
> > ft2232_vid_pid 0x15BA 0x0004
> > with this one:
> > ft2232_vid_pid 0x0403 0xcff8
> >
> > If it doesn't work, open your Device Manager, you should see two
> > devices on the olimex jtag, one should be a virtual COM port, the
> > second one should be FTDI device (or something like that), click on
> > it's properties and see the first property (Device instance ID) and
> > see what the PID and the VID numbers are (eventually use them in your
> > cfg for Open OCD.
> >
> > PS: Sorry for the mixed up explanaion, I'm not in front of my PC right
> > now :)
> >
> > --- In A..., "Ryan" wrote:
> > >
> > > I have also tried connecting from the windows command line with the
> > > following command:
> > >
> > > openocd-ftd2xx -f at91sam7s256-armusbocd.cfg
> > >
> > > This is the error that I get:
> > >
> > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05
09:00
> > > CEST)
> > > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> > device: 2
> > > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> > >
> > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
> > TINY A
> > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
> > TINY B
> > >
> > > Here is the "at91sam7s256-armusbocd.cfg" file:
> > >
> > > #define our ports
> > > telnet_port 4444
> > > gdb_port 3333
> > >
> > > #commands specific to the Amontec JTAGKey
> > > interface ft2232
> > > ft2232_device_desc "Olimex OpenOCD JTAG TINY"
> > > ft2232_layout "olimex-jtag"
> > > ft2232_vid_pid 0x15BA 0x0004
> > > jtag_speed 2
> > > jtag_nsrst_delay 200
> > > jtag_ntrst_delay 200
> > >
> > > #reset_config [combination] [trst_type] [srst_type]
> > > reset_config srst_only srst_pulls_trst
> > >
> > > #jtag_device
> > > jtag_device 4 0x1 0xf 0xe
> > >
> > > #daemon_startup <'attach'|'reset'>
> > > daemon_startup reset
> > >
> > > #target [variant]
> > > target arm7tdmi little run_and_init 0 arm7tdmi_r4
> > >
> > > #run_and_halt_time
> > > run_and_halt_time 0 30
> > >
> > > The hardware appears to be properly installed when I look in the
> > > device manager. I just don't know whats going on.
> > >
> > >
> > > --- In A..., "Ryan" wrote:
> > > >
> > > > I am stepping through the "Using Open Source Tools for AT91SAM7S
> Cross
> > > > Development" tutorial by James P. Lynch and I am getting hung up
> when
> > > > I try to program the board. I keep getting the following error:
> > > >
> > > >
> > > > **** Build of configuration MinGW GCC for project
> > > > demo_at91sam7_blink_flash ****
> > > >
> > > > make -k program
> > > > Flash Programming with OpenOCD...
> > > > 'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
> > > > 'c:/Program
> > > >
> >
Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
> > > > # program the onchip FLASH here
> > > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05
> 09:00
> > > > CEST)
> > > > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> > > device: 2
> > > > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> > > >
> > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD
JTAG
> > > TINY A
> > > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD
JTAG
> > > TINY B
> > > > make: *** [program] Error 1
> > > >
> > > > I think that the problem lies in my
> > > > at91sam7s256-armusbocd-flash-program.cfg file but I am not
sure what
> > > > needs to change. I am using the AT91SAM7S-EK Evaluation Kit. Can
> > > > someone please point me in the right direction?
> > > >
> > > > P.S. For those of you following my "Loaded SAM-BA in the wrong
spot"
> > > > post, this is not the same board.
> > > >
> > >
> Start a New Thread

The numbers in the device manager match the numbers in my .cfg file...
I got really excited for a minute when I read your post but it doesn't
seem to be the answer.
--- In A..., "predator_mf2000"
wrote:
>
> Hi Ryan,
>
> Try replacing in "at91sam7s256-armusbocd.cfg" this line:
> ft2232_vid_pid 0x15BA 0x0004
> with this one:
> ft2232_vid_pid 0x0403 0xcff8
>
> If it doesn't work, open your Device Manager, you should see two
> devices on the olimex jtag, one should be a virtual COM port, the
> second one should be FTDI device (or something like that), click on
> it's properties and see the first property (Device instance ID) and
> see what the PID and the VID numbers are (eventually use them in your
> cfg for Open OCD.
>
> PS: Sorry for the mixed up explanaion, I'm not in front of my PC right
> now :)
>
> --- In A..., "Ryan" wrote:
> >
> > I have also tried connecting from the windows command line with the
> > following command:
> >
> > openocd-ftd2xx -f at91sam7s256-armusbocd.cfg
> >
> > This is the error that I get:
> >
> > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
> > CEST)
> > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> device: 2
> > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> >
> > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
> TINY A
> > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
> TINY B
> >
> > Here is the "at91sam7s256-armusbocd.cfg" file:
> >
> > #define our ports
> > telnet_port 4444
> > gdb_port 3333
> >
> > #commands specific to the Amontec JTAGKey
> > interface ft2232
> > ft2232_device_desc "Olimex OpenOCD JTAG TINY"
> > ft2232_layout "olimex-jtag"
> > ft2232_vid_pid 0x15BA 0x0004
> > jtag_speed 2
> > jtag_nsrst_delay 200
> > jtag_ntrst_delay 200
> >
> > #reset_config [combination] [trst_type] [srst_type]
> > reset_config srst_only srst_pulls_trst
> >
> > #jtag_device
> > jtag_device 4 0x1 0xf 0xe
> >
> > #daemon_startup <'attach'|'reset'>
> > daemon_startup reset
> >
> > #target [variant]
> > target arm7tdmi little run_and_init 0 arm7tdmi_r4
> >
> > #run_and_halt_time
> > run_and_halt_time 0 30
> >
> > The hardware appears to be properly installed when I look in the
> > device manager. I just don't know whats going on.
> >
> >
> > --- In A..., "Ryan" wrote:
> > >
> > > I am stepping through the "Using Open Source Tools for AT91SAM7S
Cross
> > > Development" tutorial by James P. Lynch and I am getting hung up
when
> > > I try to program the board. I keep getting the following error:
> > >
> > >
> > > **** Build of configuration MinGW GCC for project
> > > demo_at91sam7_blink_flash ****
> > >
> > > make -k program
> > > Flash Programming with OpenOCD...
> > > 'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
> > > 'c:/Program
> > >
> Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
> > > # program the onchip FLASH here
> > > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05
09:00
> > > CEST)
> > > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> > device: 2
> > > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> > >
> > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
> > TINY A
> > > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
> > TINY B
> > > make: *** [program] Error 1
> > >
> > > I think that the problem lies in my
> > > at91sam7s256-armusbocd-flash-program.cfg file but I am not sure what
> > > needs to change. I am using the AT91SAM7S-EK Evaluation Kit. Can
> > > someone please point me in the right direction?
> > >
> > > P.S. For those of you following my "Loaded SAM-BA in the wrong spot"
> > > post, this is not the same board.
> > >
> Start a New Thread

Hi Ryan,

Try replacing in "at91sam7s256-armusbocd.cfg" this line:
ft2232_vid_pid 0x15BA 0x0004
with this one:
ft2232_vid_pid 0x0403 0xcff8

If it doesn't work, open your Device Manager, you should see two
devices on the olimex jtag, one should be a virtual COM port, the
second one should be FTDI device (or something like that), click on
it's properties and see the first property (Device instance ID) and
see what the PID and the VID numbers are (eventually use them in your
cfg for Open OCD.

PS: Sorry for the mixed up explanaion, I'm not in front of my PC right
now :)

--- In A..., "Ryan" wrote:
>
> I have also tried connecting from the windows command line with the
> following command:
>
> openocd-ftd2xx -f at91sam7s256-armusbocd.cfg
>
> This is the error that I get:
>
> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
> CEST)
> Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
device: 2
> Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
>
> Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
TINY A
> Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
TINY B
>
> Here is the "at91sam7s256-armusbocd.cfg" file:
>
> #define our ports
> telnet_port 4444
> gdb_port 3333
>
> #commands specific to the Amontec JTAGKey
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG TINY"
> ft2232_layout "olimex-jtag"
> ft2232_vid_pid 0x15BA 0x0004
> jtag_speed 2
> jtag_nsrst_delay 200
> jtag_ntrst_delay 200
>
> #reset_config [combination] [trst_type] [srst_type]
> reset_config srst_only srst_pulls_trst
>
> #jtag_device
> jtag_device 4 0x1 0xf 0xe
>
> #daemon_startup <'attach'|'reset'>
> daemon_startup reset
>
> #target [variant]
> target arm7tdmi little run_and_init 0 arm7tdmi_r4
>
> #run_and_halt_time
> run_and_halt_time 0 30
>
> The hardware appears to be properly installed when I look in the
> device manager. I just don't know whats going on.
> --- In A..., "Ryan" wrote:
> >
> > I am stepping through the "Using Open Source Tools for AT91SAM7S Cross
> > Development" tutorial by James P. Lynch and I am getting hung up when
> > I try to program the board. I keep getting the following error:
> >
> >
> > **** Build of configuration MinGW GCC for project
> > demo_at91sam7_blink_flash ****
> >
> > make -k program
> > Flash Programming with OpenOCD...
> > 'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
> > 'c:/Program
> >
Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
> > # program the onchip FLASH here
> > Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
> > CEST)
> > Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
> device: 2
> > Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
> >
> > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
> TINY A
> > Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
> TINY B
> > make: *** [program] Error 1
> >
> > I think that the problem lies in my
> > at91sam7s256-armusbocd-flash-program.cfg file but I am not sure what
> > needs to change. I am using the AT91SAM7S-EK Evaluation Kit. Can
> > someone please point me in the right direction?
> >
> > P.S. For those of you following my "Loaded SAM-BA in the wrong spot"
> > post, this is not the same board.
> Start a New Thread

I have also tried connecting from the windows command line with the
following command:

openocd-ftd2xx -f at91sam7s256-armusbocd.cfg

This is the error that I get:

Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
CEST)
Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi device: 2
Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2

Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY A
Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG TINY B

Here is the "at91sam7s256-armusbocd.cfg" file:

#define our ports
telnet_port 4444
gdb_port 3333

#commands specific to the Amontec JTAGKey
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY"
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15BA 0x0004
jtag_speed 2
jtag_nsrst_delay 200
jtag_ntrst_delay 200

#reset_config [combination] [trst_type] [srst_type]
reset_config srst_only srst_pulls_trst

#jtag_device
jtag_device 4 0x1 0xf 0xe

#daemon_startup <'attach'|'reset'>
daemon_startup reset

#target [variant]
target arm7tdmi little run_and_init 0 arm7tdmi_r4

#run_and_halt_time
run_and_halt_time 0 30

The hardware appears to be properly installed when I look in the
device manager. I just don't know whats going on.
--- In A..., "Ryan" wrote:
>
> I am stepping through the "Using Open Source Tools for AT91SAM7S Cross
> Development" tutorial by James P. Lynch and I am getting hung up when
> I try to program the board. I keep getting the following error:
> **** Build of configuration MinGW GCC for project
> demo_at91sam7_blink_flash ****
>
> make -k program
> Flash Programming with OpenOCD...
> 'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
> 'c:/Program
> Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
> # program the onchip FLASH here
> Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
> CEST)
> Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi
device: 2
> Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2
>
> Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG
TINY A
> Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG
TINY B
> make: *** [program] Error 1
>
> I think that the problem lies in my
> at91sam7s256-armusbocd-flash-program.cfg file but I am not sure what
> needs to change. I am using the AT91SAM7S-EK Evaluation Kit. Can
> someone please point me in the right direction?
>
> P.S. For those of you following my "Loaded SAM-BA in the wrong spot"
> post, this is not the same board.
> Start a New Thread

I am stepping through the "Using Open Source Tools for AT91SAM7S Cross
Development" tutorial by James P. Lynch and I am getting hung up when
I try to program the board. I keep getting the following error:
**** Build of configuration MinGW GCC for project
demo_at91sam7_blink_flash ****

make -k program
Flash Programming with OpenOCD...
'c:/Program Files/openocd-2007re204/bin/'openocd-ftd2xx.exe -f
'c:/Program
Files/openocd-2007re204/bin/'at91sam7s256-armusbocd-flash-program.cfg
# program the onchip FLASH here
Info: openocd.c:93 main(): Open On-Chip Debugger (2007-09-05 09:00
CEST)
Error: ft2232.c:1341 ft2232_init_ftd2xx(): unable to open ftdi device: 2
Error: ft2232.c:1356 ft2232_init_ftd2xx(): ListDevices: 2

Error: ft2232.c:1358 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY A
Error: ft2232.c:1358 ft2232_init_ftd2xx(): 1: Olimex OpenOCD JTAG TINY B
make: *** [program] Error 1

I think that the problem lies in my
at91sam7s256-armusbocd-flash-program.cfg file but I am not sure what
needs to change. I am using the AT91SAM7S-EK Evaluation Kit. Can
someone please point me in the right direction?

P.S. For those of you following my "Loaded SAM-BA in the wrong spot"
post, this is not the same board. Start a New Thread