Hi guys,
I have a Olimex ARM-USB-TINY Jtag device and a LPC2478STK board, I want to
make them both work togheter but I am having problems.
I installed the Eclipse, OpenOCD and the cigwin from the CD that came with
the ARM-USB-TINY device.
The sample code that came in the CD is building ok, but I cant debug.
The ft232driver .c file is sayint that he couldn't find the ARM-USB-TINY
B
device, the A device is beeing found propely.
It is strange, becouse on the CFG there is no mention of a "B" device.
Can someone point me any direction? I am quite new at openocd.
Thanks
ARM-USB-TINY + LPC2478STK = Help!
Started by ●September 17, 2009
Reply by ●September 18, 20092009-09-18
Am 9/17/2009 7:31 PM, also sprach Felipe de Andrade Neves Lavratti:
> The ft232driver .c file is sayint that he couldn't find the ARM-USB-TINY B
> device, the A device is beeing found propely.
>
How is it that a .c file is trying to access a device? In what context
is this?
Does this mean you've got as far as starting openocd and have gdb via
eclipse connect to it?
> The ft232driver .c file is sayint that he couldn't find the ARM-USB-TINY B
> device, the A device is beeing found propely.
>
How is it that a .c file is trying to access a device? In what context
is this?
Does this mean you've got as far as starting openocd and have gdb via
eclipse connect to it?
Reply by ●September 22, 20092009-09-22
Sorry for the delay, I had such a busy week.
Follow precise information about my problem:
1) I am trying to debug using the olimex ARM-USB-TINY on the LPC2478-STK.
2) Everything is powered, drivers installed, and etc.
3) I am using eclipse, all I do is to click on the OpenOCD Tiny from the
External Tools on the Debug Perspective.
*I get the following error:*
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info: options.c:50 configuration_output_handler(): jtag_speed: 3, 3
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger 1.0
(2008-10-04-10:00) svn:exported
Error: ft2232.c:1419 ft2232_init_ftd2xx(): unable to open ftdi device: 2
Error: ft2232.c:1434 ft2232_init_ftd2xx(): ListDevices: 2
Error: ft2232.c:1436 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY B
Error: ft2232.c:1436 ft2232_init_ftd2xx(): 1: x?
*This is my .cfg file:*
**
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15BA 0x0004
jtag_speed 3
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst separate
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target
#target arm7tdmi
target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
run_and_halt_time 0 30
#target_script 0 reset oocd_flash2138.script
working_area 0 0x40000000 0x40000 nobackup
#flash configuration
flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v2 12000 calc_checksum
# For more information about the configuration files, take a look at:
# http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
Any direction would be of great hand.
Thanks.
Follow precise information about my problem:
1) I am trying to debug using the olimex ARM-USB-TINY on the LPC2478-STK.
2) Everything is powered, drivers installed, and etc.
3) I am using eclipse, all I do is to click on the OpenOCD Tiny from the
External Tools on the Debug Perspective.
*I get the following error:*
Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
Info: options.c:50 configuration_output_handler(): jtag_speed: 3, 3
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger 1.0
(2008-10-04-10:00) svn:exported
Error: ft2232.c:1419 ft2232_init_ftd2xx(): unable to open ftdi device: 2
Error: ft2232.c:1434 ft2232_init_ftd2xx(): ListDevices: 2
Error: ft2232.c:1436 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY B
Error: ft2232.c:1436 ft2232_init_ftd2xx(): 1: x?
*This is my .cfg file:*
**
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
ft2232_layout "olimex-jtag"
ft2232_vid_pid 0x15BA 0x0004
jtag_speed 3
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst separate
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target
#target arm7tdmi
target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
run_and_halt_time 0 30
#target_script 0 reset oocd_flash2138.script
working_area 0 0x40000000 0x40000 nobackup
#flash configuration
flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v2 12000 calc_checksum
# For more information about the configuration files, take a look at:
# http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
Any direction would be of great hand.
Thanks.
Reply by ●September 30, 20092009-09-30
nothing folks ?
2009/9/22 Felipe de A N L
> Sorry for the delay, I had such a busy week.
>
> Follow precise information about my problem:
>
> 1) I am trying to debug using the olimex ARM-USB-TINY on the LPC2478-STK.
> 2) Everything is powered, drivers installed, and etc.
> 3) I am using eclipse, all I do is to click on the OpenOCD Tiny from the
> External Tools on the Debug Perspective.
>
> *I get the following error:*
>
> Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
>
> $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> Info: options.c:50 configuration_output_handler(): jtag_speed: 3, 3
> Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger
> 1.0 (2008-10-04-10:00) svn:exported
> Error: ft2232.c:1419 ft2232_init_ftd2xx(): unable to open ftdi device: 2
> Error: ft2232.c:1434 ft2232_init_ftd2xx(): ListDevices: 2
> Error: ft2232.c:1436 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY B
> Error: ft2232.c:1436 ft2232_init_ftd2xx(): 1: x ?
>
> *This is my .cfg file:*
> **
> #daemon configuration
> telnet_port 4444
> gdb_port 3333
> #interface
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
> ft2232_layout "olimex-jtag"
> ft2232_vid_pid 0x15BA 0x0004
> jtag_speed 3
> #use combined on interfaces or targets that can't set TRST/SRST separately
> reset_config trst_and_srst separate
> #jtag scan chain
> #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
> jtag_device 4 0x1 0xf 0xe
> #target configuration
> daemon_startup reset
> #target
> #target arm7tdmi
> target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
> run_and_halt_time 0 30
> #target_script 0 reset oocd_flash2138.script
> working_area 0 0x40000000 0x40000 nobackup
> #flash configuration
> flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v2 12000 calc_checksum
> # For more information about the configuration files, take a look at:
> # http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
>
> Any direction would be of great hand.
> Thanks.
>
2009/9/22 Felipe de A N L
> Sorry for the delay, I had such a busy week.
>
> Follow precise information about my problem:
>
> 1) I am trying to debug using the olimex ARM-USB-TINY on the LPC2478-STK.
> 2) Everything is powered, drivers installed, and etc.
> 3) I am using eclipse, all I do is to click on the OpenOCD Tiny from the
> External Tools on the Debug Perspective.
>
> *I get the following error:*
>
> Open On-Chip Debugger 1.0 (2008-10-04-10:00) svn:exported
>
> $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> Info: options.c:50 configuration_output_handler(): jtag_speed: 3, 3
> Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger
> 1.0 (2008-10-04-10:00) svn:exported
> Error: ft2232.c:1419 ft2232_init_ftd2xx(): unable to open ftdi device: 2
> Error: ft2232.c:1434 ft2232_init_ftd2xx(): ListDevices: 2
> Error: ft2232.c:1436 ft2232_init_ftd2xx(): 0: Olimex OpenOCD JTAG TINY B
> Error: ft2232.c:1436 ft2232_init_ftd2xx(): 1: x ?
>
> *This is my .cfg file:*
> **
> #daemon configuration
> telnet_port 4444
> gdb_port 3333
> #interface
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG TINY A"
> ft2232_layout "olimex-jtag"
> ft2232_vid_pid 0x15BA 0x0004
> jtag_speed 3
> #use combined on interfaces or targets that can't set TRST/SRST separately
> reset_config trst_and_srst separate
> #jtag scan chain
> #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
> jtag_device 4 0x1 0xf 0xe
> #target configuration
> daemon_startup reset
> #target
> #target arm7tdmi
> target arm7tdmi little run_and_halt 0 arm7tdmi-s_r4
> run_and_halt_time 0 30
> #target_script 0 reset oocd_flash2138.script
> working_area 0 0x40000000 0x40000 nobackup
> #flash configuration
> flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v2 12000 calc_checksum
> # For more information about the configuration files, take a look at:
> # http://openfacts.berlios.de/index-en.phtml?title=Open+On-Chip+Debugger
>
> Any direction would be of great hand.
> Thanks.
>
Reply by ●September 30, 20092009-09-30
Felipe de A N L wrote:
> nothing folks ?
OpenOCD is a bit painful when it comes to giving helpful error information.
I have seen a similar error in many circumstances, such as still having
the openocd executable running (failed to kill it last time), not having
the JTAG device plugged in and registered properly, not having installed
the drivers with the right permissions (windows machine), faulty
hardware (the Olimex ARM-USB-* devices are not great), etc.
Your best bet is to try the OpenOCD forums and see what they say. I do
note that your configuration script looks like the old style (from what
I remember), so you might also want to consider upgrading to the latest
release.
Pete
> nothing folks ?
OpenOCD is a bit painful when it comes to giving helpful error information.
I have seen a similar error in many circumstances, such as still having
the openocd executable running (failed to kill it last time), not having
the JTAG device plugged in and registered properly, not having installed
the drivers with the right permissions (windows machine), faulty
hardware (the Olimex ARM-USB-* devices are not great), etc.
Your best bet is to try the OpenOCD forums and see what they say. I do
note that your configuration script looks like the old style (from what
I remember), so you might also want to consider upgrading to the latest
release.
Pete
Reply by ●September 30, 20092009-09-30
Thanks Pete!
2009/9/30 Pete Vidler
> Felipe de A N L wrote:
> > nothing folks ?
>
> OpenOCD is a bit painful when it comes to giving helpful error information.
>
> I have seen a similar error in many circumstances, such as still having
> the openocd executable running (failed to kill it last time), not having
> the JTAG device plugged in and registered properly, not having installed
> the drivers with the right permissions (windows machine), faulty
> hardware (the Olimex ARM-USB-* devices are not great), etc.
>
> Your best bet is to try the OpenOCD forums and see what they say. I do
> note that your configuration script looks like the old style (from what
> I remember), so you might also want to consider upgrading to the latest
> release.
>
> Pete
2009/9/30 Pete Vidler
> Felipe de A N L wrote:
> > nothing folks ?
>
> OpenOCD is a bit painful when it comes to giving helpful error information.
>
> I have seen a similar error in many circumstances, such as still having
> the openocd executable running (failed to kill it last time), not having
> the JTAG device plugged in and registered properly, not having installed
> the drivers with the right permissions (windows machine), faulty
> hardware (the Olimex ARM-USB-* devices are not great), etc.
>
> Your best bet is to try the OpenOCD forums and see what they say. I do
> note that your configuration script looks like the old style (from what
> I remember), so you might also want to consider upgrading to the latest
> release.
>
> Pete
