2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

Hi Group,

I am new to embedded linux and hence stuck trying to get my setup
working.
My problem is every so often when I try and lunch openocd I get the
following error output.

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
jtag_speed: 2
Error: JTAG communication failure, check connection, JTAG interface,
target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x3f
Error: Could not validate JTAG chain, continuing anyway...
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:no tcl port specified, using default port 6666

And on the rare occasion I get the following output

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
jtag_speed: 2
Warning:Device does not have IDCODE
Warning:Device does not have IDCODE
" " " " " "

" " " "

Warning:Device does not have IDCODE
Warning:Device does not have IDCODE

Warning:Device does not have IDCODE
Info: JTAG device found: 0xffffff03 (Manufacturer: 0x781, Part:
0xffff, Version: 0xf)
Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
0xffff, Version: 0xf)
"" "" ""
Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
0xffff, Version: 0xf)

Error: number of discovered devices in JTAG chain (180) doesn't match
configuration (1)
Error: check the config file and ensure proper JTAG communication
(connections, speed, ...)
Error: trying to validate configured JTAG chain anyway...
Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x3f
Error: Could not validate JTAG chain, continuing anyway...
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:no tcl port specified, using default port 6666
I have the following setup.

(1) Olimex dev board LPC-MT 2106 (Powered by 9V from Olimex debugger)
(2) Olimex ARM-USB_OCD
(3) OpenOCD svn version 1083
(4) Using libftd2xx.so.0.4.13
(5) Running on a HP TC1100 tablet PC (ubuntu 8.04)
(6) Configuration file is named openocd.cfg (stored in home directory)

I invoke openocd from my home directory by running the command shown
below:-

host@user:~$ openocd

or

host@user:~$ openocd -f openocd.cfg

below is the content of my configuration file:-

//////////////// Start of Configuration file ////////////////////////

# daemon configuration
telnet port 4444
gdb_port 3333

# jtag debugger configuration
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15ba 0x0003

jtag_speed 2

reset_config trst_and_srst srst_pulls_trst

#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe

#target
#target arm7tdmi
target arm7tdmi little 0 arm7tdmi-s_r4
working_area 0 0x40000000 0x4000 nobackup

#flash configuration
#flash bank lpc2000 0 0
flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum

//////////////// End of Configuration file ////////////////////////

I will appreciate any help I have spent a few days on this without any
success.

Many thanks in advance.
Regards
Ola Oni

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

change your config file to:
ft2232_device_desc "Olimex OpenOCD JTAG A"
And use another power source for your board.

Harrie
----- Original Message -----
From: oladipo_oni
To: l...@yahoogroups.com
Sent: Thursday, October 23, 2008 8:39 PM
Subject: [lpc2000] Problem using Olimex-ARM-USB-OCD with OpenOCD in ubuntu 8.04
Hi Group,

I am new to embedded linux and hence stuck trying to get my setup
working.
My problem is every so often when I try and lunch openocd I get the
following error output.

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
jtag_speed: 2
Error: JTAG communication failure, check connection, JTAG interface,
target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x3f
Error: Could not validate JTAG chain, continuing anyway...
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:no tcl port specified, using default port 6666

And on the rare occasion I get the following output

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
jtag_speed: 2
Warning:Device does not have IDCODE
Warning:Device does not have IDCODE
" " " " " "

" " " "

Warning:Device does not have IDCODE
Warning:Device does not have IDCODE

Warning:Device does not have IDCODE
Info: JTAG device found: 0xffffff03 (Manufacturer: 0x781, Part:
0xffff, Version: 0xf)
Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
0xffff, Version: 0xf)
"" "" ""
Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
0xffff, Version: 0xf)

Error: number of discovered devices in JTAG chain (180) doesn't match
configuration (1)
Error: check the config file and ensure proper JTAG communication
(connections, speed, ...)
Error: trying to validate configured JTAG chain anyway...
Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x3f
Error: Could not validate JTAG chain, continuing anyway...
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x0f check_value: 0x01 check_mask: 0x0f
Warning:in_handler reported a failed check
Warning:no tcl port specified, using default port 6666

I have the following setup.

(1) Olimex dev board LPC-MT 2106 (Powered by 9V from Olimex debugger)
(2) Olimex ARM-USB_OCD
(3) OpenOCD svn version 1083
(4) Using libftd2xx.so.0.4.13
(5) Running on a HP TC1100 tablet PC (ubuntu 8.04)
(6) Configuration file is named openocd.cfg (stored in home directory)

I invoke openocd from my home directory by running the command shown
below:-

host@user:~$ openocd

or

host@user:~$ openocd -f openocd.cfg

below is the content of my configuration file:-

//////////////// Start of Configuration file ////////////////////////

# daemon configuration
telnet port 4444
gdb_port 3333

# jtag debugger configuration
interface ft2232
ft2232_device_desc "Olimex OpenOCD JTAG"
ft2232_layout olimex-jtag
ft2232_vid_pid 0x15ba 0x0003

jtag_speed 2

reset_config trst_and_srst srst_pulls_trst

#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe

#target
#target arm7tdmi
target arm7tdmi little 0 arm7tdmi-s_r4

working_area 0 0x40000000 0x4000 nobackup

#flash configuration
#flash bank lpc2000 0 0
flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum

//////////////// End of Configuration file ////////////////////////

I will appreciate any help I have spent a few days on this without any
success.

Many thanks in advance.

Regards
Ola Oni

[Non-text portions of this message have been removed]
------------------------------------

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hey Harrie,

Thanks for the suggestions. But the problem still persists.
For powering my LPC-MT 2106 development board I am now using a 9V 2.2A
dc block. The documentation for the board recommend 6Vac/9Vdc.

I also changed the ft2232_device_desc to "Olimex OpenOCD JTAG A" as
advised but no show.

Is there anybody in this group that uses this dev board and debugger
combination.
There is a jumper label JRST on the board that I can't find in the
schematic diagram.

The only two pin jumpers that I can see in the schematic diagram is
the DEBUG and the BSL.

Many thanks in advance
--- In l...@yahoogroups.com, "Harrie Geerts" wrote:
>
> change your config file to:
> ft2232_device_desc "Olimex OpenOCD JTAG A"
> And use another power source for your board.
>
> Harrie
> ----- Original Message -----
> From: oladipo_oni
> To: l...@yahoogroups.com
> Sent: Thursday, October 23, 2008 8:39 PM
> Subject: [lpc2000] Problem using Olimex-ARM-USB-OCD with OpenOCD
in ubuntu 8.04
> Hi Group,
>
> I am new to embedded linux and hence stuck trying to get my setup
> working.
> My problem is every so often when I try and lunch openocd I get the
> following error output.
>
> $URL:
http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> jtag_speed: 2
> Error: JTAG communication failure, check connection, JTAG interface,
> target power etc.
> Error: trying to validate configured JTAG chain anyway...
> Error: Error validating JTAG scan chain, IR mismatch, scan
returned 0x3f
> Error: Could not validate JTAG chain, continuing anyway...
> Warning:value captured during scan didn't pass the requested check:
> captured: 0x0f check_value: 0x01 check_mask: 0x0f
> Warning:in_handler reported a failed check
> Warning:value captured during scan didn't pass the requested check:
> captured: 0x0f check_value: 0x01 check_mask: 0x0f
> Warning:in_handler reported a failed check
> Warning:no tcl port specified, using default port 6666
>
> And on the rare occasion I get the following output
>
> $URL:
http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> jtag_speed: 2
> Warning:Device does not have IDCODE
> Warning:Device does not have IDCODE
> " " " " " "
>
> " " " "
>
> Warning:Device does not have IDCODE
> Warning:Device does not have IDCODE
>
> Warning:Device does not have IDCODE
> Info: JTAG device found: 0xffffff03 (Manufacturer: 0x781, Part:
> 0xffff, Version: 0xf)
> Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> 0xffff, Version: 0xf)
> "" "" ""
> Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> 0xffff, Version: 0xf)
>
> Error: number of discovered devices in JTAG chain (180) doesn't match
> configuration (1)
> Error: check the config file and ensure proper JTAG communication
> (connections, speed, ...)
> Error: trying to validate configured JTAG chain anyway...
> Error: Error validating JTAG scan chain, IR mismatch, scan
returned 0x3f
> Error: Could not validate JTAG chain, continuing anyway...
> Warning:value captured during scan didn't pass the requested check:
> captured: 0x0f check_value: 0x01 check_mask: 0x0f
> Warning:in_handler reported a failed check
> Warning:value captured during scan didn't pass the requested check:
> captured: 0x0f check_value: 0x01 check_mask: 0x0f
> Warning:in_handler reported a failed check
> Warning:no tcl port specified, using default port 6666
>
> I have the following setup.
>
> (1) Olimex dev board LPC-MT 2106 (Powered by 9V from Olimex debugger)
> (2) Olimex ARM-USB_OCD
> (3) OpenOCD svn version 1083
> (4) Using libftd2xx.so.0.4.13
> (5) Running on a HP TC1100 tablet PC (ubuntu 8.04)
> (6) Configuration file is named openocd.cfg (stored in home directory)
>
> I invoke openocd from my home directory by running the command shown
> below:-
>
> host@user:~$ openocd
>
> or
>
> host@user:~$ openocd -f openocd.cfg
>
> below is the content of my configuration file:-
>
> //////////////// Start of Configuration file ////////////////////////
>
> # daemon configuration
> telnet port 4444
> gdb_port 3333
>
> # jtag debugger configuration
> interface ft2232
> ft2232_device_desc "Olimex OpenOCD JTAG"
> ft2232_layout olimex-jtag
> ft2232_vid_pid 0x15ba 0x0003
>
> jtag_speed 2
>
> reset_config trst_and_srst srst_pulls_trst
>
> #jtag scan chain
> #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask,
IDCODE)
> jtag_device 4 0x1 0xf 0xe
>
> #target
> #target arm7tdmi
> target arm7tdmi little 0 arm7tdmi-s_r4
>
> working_area 0 0x40000000 0x4000 nobackup
>
> #flash configuration
> #flash bank lpc2000 0 0
> flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum
>
> //////////////// End of Configuration file ////////////////////////
>
> I will appreciate any help I have spent a few days on this without any
> success.
>
> Many thanks in advance.
>
> Regards
> Ola Oni
>
>
>
> [Non-text portions of this message have been removed]
>

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi All,

Can any confirm which svn version of openocd is being used.
I am still having problem trying to connect my dev board to my olimex
usb arm debugger.
Many thanks in advance.

Regards
Ola Oni

--- In l...@yahoogroups.com, "oladipo_oni" wrote:
>
> Hey Harrie,
>
> Thanks for the suggestions. But the problem still persists.
> For powering my LPC-MT 2106 development board I am now using a 9V 2.2A
> dc block. The documentation for the board recommend 6Vac/9Vdc.
>
> I also changed the ft2232_device_desc to "Olimex OpenOCD JTAG A" as
> advised but no show.
>
> Is there anybody in this group that uses this dev board and debugger
> combination.
> There is a jumper label JRST on the board that I can't find in the
> schematic diagram.
>
> The only two pin jumpers that I can see in the schematic diagram is
> the DEBUG and the BSL.
>
> Many thanks in advance
> --- In l...@yahoogroups.com, "Harrie Geerts" wrote:
> >
> > change your config file to:
> > ft2232_device_desc "Olimex OpenOCD JTAG A"
> > And use another power source for your board.
> >
> > Harrie
> > ----- Original Message -----
> > From: oladipo_oni
> > To: l...@yahoogroups.com
> > Sent: Thursday, October 23, 2008 8:39 PM
> > Subject: [lpc2000] Problem using Olimex-ARM-USB-OCD with OpenOCD
> in ubuntu 8.04
> >
> >
> > Hi Group,
> >
> > I am new to embedded linux and hence stuck trying to get my setup
> > working.
> > My problem is every so often when I try and lunch openocd I get the
> > following error output.
> >
> > $URL:
> http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> > jtag_speed: 2
> > Error: JTAG communication failure, check connection, JTAG interface,
> > target power etc.
> > Error: trying to validate configured JTAG chain anyway...
> > Error: Error validating JTAG scan chain, IR mismatch, scan
> returned 0x3f
> > Error: Could not validate JTAG chain, continuing anyway...
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:no tcl port specified, using default port 6666
> >
> > And on the rare occasion I get the following output
> >
> > $URL:
> http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> > jtag_speed: 2
> > Warning:Device does not have IDCODE
> > Warning:Device does not have IDCODE
> > " " " " " "
> >
> > " " " "
> >
> > Warning:Device does not have IDCODE
> > Warning:Device does not have IDCODE
> >
> > Warning:Device does not have IDCODE
> > Info: JTAG device found: 0xffffff03 (Manufacturer: 0x781, Part:
> > 0xffff, Version: 0xf)
> > Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> > 0xffff, Version: 0xf)
> > "" "" ""
> > Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> > 0xffff, Version: 0xf)
> >
> > Error: number of discovered devices in JTAG chain (180) doesn't
match
> > configuration (1)
> > Error: check the config file and ensure proper JTAG communication
> > (connections, speed, ...)
> > Error: trying to validate configured JTAG chain anyway...
> > Error: Error validating JTAG scan chain, IR mismatch, scan
> returned 0x3f
> > Error: Could not validate JTAG chain, continuing anyway...
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:no tcl port specified, using default port 6666
> >
> > I have the following setup.
> >
> > (1) Olimex dev board LPC-MT 2106 (Powered by 9V from Olimex
debugger)
> > (2) Olimex ARM-USB_OCD
> > (3) OpenOCD svn version 1083
> > (4) Using libftd2xx.so.0.4.13
> > (5) Running on a HP TC1100 tablet PC (ubuntu 8.04)
> > (6) Configuration file is named openocd.cfg (stored in home
directory)
> >
> > I invoke openocd from my home directory by running the command shown
> > below:-
> >
> > host@user:~$ openocd
> >
> > or
> >
> > host@user:~$ openocd -f openocd.cfg
> >
> > below is the content of my configuration file:-
> >
> > //////////////// Start of Configuration file
////////////////////////
> >
> > # daemon configuration
> > telnet port 4444
> > gdb_port 3333
> >
> > # jtag debugger configuration
> > interface ft2232
> > ft2232_device_desc "Olimex OpenOCD JTAG"
> > ft2232_layout olimex-jtag
> > ft2232_vid_pid 0x15ba 0x0003
> >
> > jtag_speed 2
> >
> > reset_config trst_and_srst srst_pulls_trst
> >
> > #jtag scan chain
> > #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask,
> IDCODE)
> > jtag_device 4 0x1 0xf 0xe
> >
> > #target
> > #target arm7tdmi
> > target arm7tdmi little 0 arm7tdmi-s_r4
> >
> > working_area 0 0x40000000 0x4000 nobackup
> >
> > #flash configuration
> > #flash bank lpc2000 0 0
> > flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum
> >
> > //////////////// End of Configuration file ////////////////////////
> >
> > I will appreciate any help I have spent a few days on this
without any
> > success.
> >
> > Many thanks in advance.
> >
> > Regards
> > Ola Oni
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
>
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi All,

Is there anyway of testing Olimex LPC-MT2106 development board in
isolation?
What I want is tool that will allow me to program the flash with a
program that exercises the LCD and LED.
This will allow me to eliminate the dev board from my list of suspect
in my setup

Regards
Ola Oni

--- In l...@yahoogroups.com, "oladipo_oni" wrote:
>
> Hey Harrie,
>
> Thanks for the suggestions. But the problem still persists.
> For powering my LPC-MT 2106 development board I am now using a 9V 2.2A
> dc block. The documentation for the board recommend 6Vac/9Vdc.
>
> I also changed the ft2232_device_desc to "Olimex OpenOCD JTAG A" as
> advised but no show.
>
> Is there anybody in this group that uses this dev board and debugger
> combination.
> There is a jumper label JRST on the board that I can't find in the
> schematic diagram.
>
> The only two pin jumpers that I can see in the schematic diagram is
> the DEBUG and the BSL.
>
> Many thanks in advance
> --- In l...@yahoogroups.com, "Harrie Geerts" wrote:
> >
> > change your config file to:
> > ft2232_device_desc "Olimex OpenOCD JTAG A"
> > And use another power source for your board.
> >
> > Harrie
> > ----- Original Message -----
> > From: oladipo_oni
> > To: l...@yahoogroups.com
> > Sent: Thursday, October 23, 2008 8:39 PM
> > Subject: [lpc2000] Problem using Olimex-ARM-USB-OCD with OpenOCD
> in ubuntu 8.04
> >
> >
> > Hi Group,
> >
> > I am new to embedded linux and hence stuck trying to get my setup
> > working.
> > My problem is every so often when I try and lunch openocd I get the
> > following error output.
> >
> > $URL:
> http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> > jtag_speed: 2
> > Error: JTAG communication failure, check connection, JTAG interface,
> > target power etc.
> > Error: trying to validate configured JTAG chain anyway...
> > Error: Error validating JTAG scan chain, IR mismatch, scan
> returned 0x3f
> > Error: Could not validate JTAG chain, continuing anyway...
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:no tcl port specified, using default port 6666
> >
> > And on the rare occasion I get the following output
> >
> > $URL:
> http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
> > jtag_speed: 2
> > Warning:Device does not have IDCODE
> > Warning:Device does not have IDCODE
> > " " " " " "
> >
> > " " " "
> >
> > Warning:Device does not have IDCODE
> > Warning:Device does not have IDCODE
> >
> > Warning:Device does not have IDCODE
> > Info: JTAG device found: 0xffffff03 (Manufacturer: 0x781, Part:
> > 0xffff, Version: 0xf)
> > Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> > 0xffff, Version: 0xf)
> > "" "" ""
> > Info: JTAG device found: 0xffffffff (Manufacturer: 0x7ff, Part:
> > 0xffff, Version: 0xf)
> >
> > Error: number of discovered devices in JTAG chain (180) doesn't
match
> > configuration (1)
> > Error: check the config file and ensure proper JTAG communication
> > (connections, speed, ...)
> > Error: trying to validate configured JTAG chain anyway...
> > Error: Error validating JTAG scan chain, IR mismatch, scan
> returned 0x3f
> > Error: Could not validate JTAG chain, continuing anyway...
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:value captured during scan didn't pass the requested check:
> > captured: 0x0f check_value: 0x01 check_mask: 0x0f
> > Warning:in_handler reported a failed check
> > Warning:no tcl port specified, using default port 6666
> >
> > I have the following setup.
> >
> > (1) Olimex dev board LPC-MT 2106 (Powered by 9V from Olimex
debugger)
> > (2) Olimex ARM-USB_OCD
> > (3) OpenOCD svn version 1083
> > (4) Using libftd2xx.so.0.4.13
> > (5) Running on a HP TC1100 tablet PC (ubuntu 8.04)
> > (6) Configuration file is named openocd.cfg (stored in home
directory)
> >
> > I invoke openocd from my home directory by running the command shown
> > below:-
> >
> > host@user:~$ openocd
> >
> > or
> >
> > host@user:~$ openocd -f openocd.cfg
> >
> > below is the content of my configuration file:-
> >
> > //////////////// Start of Configuration file
////////////////////////
> >
> > # daemon configuration
> > telnet port 4444
> > gdb_port 3333
> >
> > # jtag debugger configuration
> > interface ft2232
> > ft2232_device_desc "Olimex OpenOCD JTAG"
> > ft2232_layout olimex-jtag
> > ft2232_vid_pid 0x15ba 0x0003
> >
> > jtag_speed 2
> >
> > reset_config trst_and_srst srst_pulls_trst
> >
> > #jtag scan chain
> > #format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask,
> IDCODE)
> > jtag_device 4 0x1 0xf 0xe
> >
> > #target
> > #target arm7tdmi
> > target arm7tdmi little 0 arm7tdmi-s_r4
> >
> > working_area 0 0x40000000 0x4000 nobackup
> >
> > #flash configuration
> > #flash bank lpc2000 0 0
> > flash bank lpc2000 0x0 0x40000 0 0 0 lpc2000_v1 14765 calc_checksum
> >
> > //////////////// End of Configuration file ////////////////////////
> >
> > I will appreciate any help I have spent a few days on this
without any
> > success.
> >
> > Many thanks in advance.
> >
> > Regards
> > Ola Oni
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
>
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi,

> Is there anyway of testing Olimex LPC-MT2106 development board in
> isolation?
> What I want is tool that will allow me to program the flash with a
> program that exercises the LCD and LED.

IIRC the LCD on that board is connected to the 2106's ETM pins and cannot,
therefore, be accessed while debugging with a JTAG adapter connected.

> This will allow me to eliminate the dev board from my list of suspect
> in my setup

Have you tried using ISP?

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi Paul,

Thanks for your response.
I am not sure I understand the contents of your Posted message, please
remember I am new to the whole Linux environment development.

What do you mean? IIRC the LCD on that board is connected to the
2106's ETM pins..
Accordingly to the schematic diagram P0.17 to P0.21 is connected to
the Jtag connector
While P0.4 to P0.7 is connected to the LCD data bus and P0.22 to P0.24
are connected to the LCD control line namely E, RS, and R/W respectively.
Let me know if you want me to send you the schematic diagram for your
reference.
And just in case I have missed something in your message what is IIRC
and am I correct in understanding ETM as Enable Trace Module.

Which application do you recommend that is free for ISP.

Regards
Ola

--- In l...@yahoogroups.com, "Paul Curtis" wrote:
>
> Hi,
>
> > Is there anyway of testing Olimex LPC-MT2106 development board in
> > isolation?
> > What I want is tool that will allow me to program the flash with a
> > program that exercises the LCD and LED.
>
> IIRC the LCD on that board is connected to the 2106's ETM pins and
cannot,
> therefore, be accessed while debugging with a JTAG adapter connected.
>
> > This will allow me to eliminate the dev board from my list of suspect
> > in my setup
>
> Have you tried using ISP?
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi Paul,

I think I now understand your message after doing a Google search on
IIRC I found that it is an acronym for "If I Recall Correctly".
The schematic diagram can be view using the following url.
http://www.olimex.com/dev/images/lpc-mt-2106-sch.gif

Many thanks in advance.

Regards
Ola

--- In l...@yahoogroups.com, "oladipo_oni" wrote:
>
> Hi Paul,
>
> Thanks for your response.
> I am not sure I understand the contents of your Posted message, please
> remember I am new to the whole Linux environment development.
>
> What do you mean? IIRC the LCD on that board is connected to the
> 2106's ETM pins..
> Accordingly to the schematic diagram P0.17 to P0.21 is connected to
> the Jtag connector
> While P0.4 to P0.7 is connected to the LCD data bus and P0.22 to P0.24
> are connected to the LCD control line namely E, RS, and R/W
respectively.
> Let me know if you want me to send you the schematic diagram for your
> reference.
> And just in case I have missed something in your message what is IIRC
> and am I correct in understanding ETM as Enable Trace Module.
>
> Which application do you recommend that is free for ISP.
>
> Regards
> Ola
>
> --- In l...@yahoogroups.com, "Paul Curtis" wrote:
> >
> > Hi,
> >
> > > Is there anyway of testing Olimex LPC-MT2106 development board in
> > > isolation?
> > > What I want is tool that will allow me to program the flash with a
> > > program that exercises the LCD and LED.
> >
> > IIRC the LCD on that board is connected to the 2106's ETM pins and
> cannot,
> > therefore, be accessed while debugging with a JTAG adapter connected.
> >
> > > This will allow me to eliminate the dev board from my list of
suspect
> > > in my setup
> >
> > Have you tried using ISP?
> >
> > --
> > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
------------------------------------

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi,

You cannot control the RS, R/W, and E signals from the LPC2106 as these are
connected to TRACECLK, PIPESTAT0, and PIPESTAT1. Unfortunately, with
primary JTAG enabled, the ETM is also enabled and thus whatever you do to
try to control P0.22 through P0.24 won't work because the ETM is hardwired
to them (with JTAG enabled).

Hence, the *only* way to display data on the LCD is to program the
application over JTAG or ISP, then reset the part without JTAG debug enabled
and see if your LCD works.

It took me about 30 minutes to do this, but then I did have the code written
and working on an LPC-2138-MT and many other boards.

As for ISP, I don't know, I never use ISP to program NXP parts.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

> -----Original Message-----
> From: l...@yahoogroups.com [mailto:l...@yahoogroups.com] On Behalf
Of
> oladipo_oni
> Sent: 27 October 2008 22:22
> To: l...@yahoogroups.com
> Subject: [lpc2000] Re: Problem using Olimex-ARM-USB-OCD with OpenOCD in
ubuntu
> 8.04
>
> Hi Paul,
>
> I think I now understand your message after doing a Google search on
> IIRC I found that it is an acronym for "If I Recall Correctly".
> The schematic diagram can be view using the following url.
> http://www.olimex.com/dev/images/lpc-mt-2106-sch.gif
>
> Many thanks in advance.
>
> Regards
> Ola
>
> --- In l...@yahoogroups.com, "oladipo_oni" wrote:
> >
> > Hi Paul,
> >
> > Thanks for your response.
> > I am not sure I understand the contents of your Posted message, please
> > remember I am new to the whole Linux environment development.
> >
> > What do you mean? IIRC the LCD on that board is connected to the
> > 2106's ETM pins..
> > Accordingly to the schematic diagram P0.17 to P0.21 is connected to
> > the Jtag connector
> > While P0.4 to P0.7 is connected to the LCD data bus and P0.22 to P0.24
> > are connected to the LCD control line namely E, RS, and R/W
> respectively.
> > Let me know if you want me to send you the schematic diagram for your
> > reference.
> > And just in case I have missed something in your message what is IIRC
> > and am I correct in understanding ETM as Enable Trace Module.
> >
> > Which application do you recommend that is free for ISP.
> >
> > Regards
> > Ola
> >
> > --- In l...@yahoogroups.com, "Paul Curtis" wrote:
> > >
> > > Hi,
> > >
> > > > Is there anyway of testing Olimex LPC-MT2106 development board in
> > > > isolation?
> > > > What I want is tool that will allow me to program the flash with a
> > > > program that exercises the LCD and LED.
> > >
> > > IIRC the LCD on that board is connected to the 2106's ETM pins and
> > cannot,
> > > therefore, be accessed while debugging with a JTAG adapter connected.
> > >
> > > > This will allow me to eliminate the dev board from my list of
> suspect
> > > > in my setup
> > >
> > > Have you tried using ISP?
> > >
> > > --
> > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > > CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
> > >
> > ------------------------------------

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi Paul,

Based on your message about you having flashed this board (lpc-mt
2106) in the past I was wondering if it was possible for you to give
me your binary file, so all I have to do is find an application that
will allow me to program the on board flash through ISP.

I don't need the code just the hex file, as I can write one when I am
up and running with the board.

My main objective is to get my olimex-arm usb JTAG debugger working.
As for now what I noticed is that openocd is not detecting the targets
power hence the error.

Error: JTAG communication failure, check connection, JTAG interface,
target power etc.

This error is consistent whether the debugger is connected to the
target or not.
Regards
Ola

--- In l...@yahoogroups.com, "Paul Curtis" wrote:
>
> Hi,
>
> You cannot control the RS, R/W, and E signals from the LPC2106 as
these are
> connected to TRACECLK, PIPESTAT0, and PIPESTAT1. Unfortunately, with
> primary JTAG enabled, the ETM is also enabled and thus whatever you
do to
> try to control P0.22 through P0.24 won't work because the ETM is
hardwired
> to them (with JTAG enabled).
>
> Hence, the *only* way to display data on the LCD is to program the
> application over JTAG or ISP, then reset the part without JTAG debug
enabled
> and see if your LCD works.
>
> It took me about 30 minutes to do this, but then I did have the code
written
> and working on an LPC-2138-MT and many other boards.
>
> As for ISP, I don't know, I never use ISP to program NXP parts.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
> > -----Original Message-----
> > From: l...@yahoogroups.com [mailto:l...@yahoogroups.com] On
Behalf
> Of
> > oladipo_oni
> > Sent: 27 October 2008 22:22
> > To: l...@yahoogroups.com
> > Subject: [lpc2000] Re: Problem using Olimex-ARM-USB-OCD with
OpenOCD in
> ubuntu
> > 8.04
> >
> > Hi Paul,
> >
> > I think I now understand your message after doing a Google search on
> > IIRC I found that it is an acronym for "If I Recall Correctly".
> > The schematic diagram can be view using the following url.
> > http://www.olimex.com/dev/images/lpc-mt-2106-sch.gif
> >
> > Many thanks in advance.
> >
> > Regards
> > Ola
> >
> >
> >
> > --- In l...@yahoogroups.com, "oladipo_oni" wrote:
> > >
> > > Hi Paul,
> > >
> > > Thanks for your response.
> > > I am not sure I understand the contents of your Posted message,
please
> > > remember I am new to the whole Linux environment development.
> > >
> > > What do you mean? IIRC the LCD on that board is connected to the
> > > 2106's ETM pins..
> > > Accordingly to the schematic diagram P0.17 to P0.21 is connected to
> > > the Jtag connector
> > > While P0.4 to P0.7 is connected to the LCD data bus and P0.22 to
P0.24
> > > are connected to the LCD control line namely E, RS, and R/W
> > respectively.
> > > Let me know if you want me to send you the schematic diagram for
your
> > > reference.
> > > And just in case I have missed something in your message what is
IIRC
> > > and am I correct in understanding ETM as Enable Trace Module.
> > >
> > > Which application do you recommend that is free for ISP.
> > >
> > > Regards
> > > Ola
> > >
> > > --- In l...@yahoogroups.com, "Paul Curtis" wrote:
> > > >
> > > > Hi,
> > > >
> > > > > Is there anyway of testing Olimex LPC-MT2106 development
board in
> > > > > isolation?
> > > > > What I want is tool that will allow me to program the flash
with a
> > > > > program that exercises the LCD and LED.
> > > >
> > > > IIRC the LCD on that board is connected to the 2106's ETM pins and
> > > cannot,
> > > > therefore, be accessed while debugging with a JTAG adapter
connected.
> > > >
> > > > > This will allow me to eliminate the dev board from my list of
> > suspect
> > > > > in my setup
> > > >
> > > > Have you tried using ISP?
> > > >
> > > > --
> > > > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > > > CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3
processors
> > > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> >



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi Ola,

> Based on your message about you having flashed this board (lpc-mt
> 2106) in the past I was wondering if it was possible for you to give
> me your binary file, so all I have to do is find an application that
> will allow me to program the on board flash through ISP.

Before I do that, please see my note below.

> I don't need the code just the hex file, as I can write one when I am
> up and running with the board.
>
> My main objective is to get my olimex-arm usb JTAG debugger working.
> As for now what I noticed is that openocd is not detecting the targets
> power hence the error.

The one thing that I *know* about the LPC-2106-MT is that the Olimex site
says to power at 6VAC/+9VDC. THIS DOES NOT WORK WITH MY BOARD. I need to
power the board using at least 10.5V DC. I power this board from a standard
lab supply, and at 10.58V it takes 24mA when idling.

Powering the board at exactly 9V DOES NOT make the JTAG port work at all,
with any JTAG adapter I have tried.

See if that helps. Rgds,

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Ola,

> Hi Paul,
>
> Based on your message about you having flashed this board (lpc-mt
> 2106) in the past I was wondering if it was possible for you to give
> me your binary file, so all I have to do is find an application that
> will allow me to program the on board flash through ISP.
>
> I don't need the code just the hex file, as I can write one when I am
> up and running with the board.

I am sending you a hex file which exercises the LCD and the LED on the 2106
board.

Some notes on getting this to work on this particular board:

1. Program the hex file using ISP or whatever.
2. Remove the BSL jumper.
3. Remove the DBG jumper.
4. Apply power the board at AT LEAST 10.5V!
5. Turn on the power.
6. Press the RST button and see if the LCD & LED work.

Note that if don't follow these instructions, things won't work. You need
the 2106 not to go into the bootloader (BSL jumper), not to snatch the extra
pins for ETM (DBG jumper), it needs to be powered to work (10.5V) and it
doesn't start up using a POR (hence press the RST button).

Getting the LCD to work properly is fairly easy. And hopefully you should
be up and running with your stuff.

...heck, you're not even a CrossWorks customer!

Regards,

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi Paul,

Sorry for the late response. I just picked up your message and noticed
the power supply info that you gave.

I will start by using a lab power supply and see if the jtag works.
If that does work I will try programming the on board flash with your
supplied hex file.
I found a windows application that will allow me to program the flash.
I would have ideally preferred a program that will allow me to program
the flash in linux.

I will keep you informed on what progress I make.
Many thanks in advance.

Regards
Ola
--- In l...@yahoogroups.com, "Paul Curtis" wrote:
>
> Ola,
>
> > Hi Paul,
> >
> > Based on your message about you having flashed this board (lpc-mt
> > 2106) in the past I was wondering if it was possible for you to give
> > me your binary file, so all I have to do is find an application that
> > will allow me to program the on board flash through ISP.
> >
> > I don't need the code just the hex file, as I can write one when I am
> > up and running with the board.
>
> I am sending you a hex file which exercises the LCD and the LED on
the 2106
> board.
>
> Some notes on getting this to work on this particular board:
>
> 1. Program the hex file using ISP or whatever.
> 2. Remove the BSL jumper.
> 3. Remove the DBG jumper.
> 4. Apply power the board at AT LEAST 10.5V!
> 5. Turn on the power.
> 6. Press the RST button and see if the LCD & LED work.
>
> Note that if don't follow these instructions, things won't work.
You need
> the 2106 not to go into the bootloader (BSL jumper), not to snatch
the extra
> pins for ETM (DBG jumper), it needs to be powered to work (10.5V) and it
> doesn't start up using a POR (hence press the RST button).
>
> Getting the LCD to work properly is fairly easy. And hopefully you
should
> be up and running with your stuff.
>
> ...heck, you're not even a CrossWorks customer!
>
> Regards,
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>

------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )

Hi All

The problem with my olimex-arm-usb-ocd with olimex lpc-mt2106 board
has be fixed.
It turns out that the problem was in the hardware.
Initially I powered the target board with the 9Vdc output from the
olimex debugger.
When that didn't work I tried a 9V dc block which still didn't work.
The penny dropped when I got a response from Paul Curtis explaining that
he could not get his board to work until he applied 10.5V.

Up to this point I noticed that the supply voltage to the target which
was supposed to be 3.3Volts was reading as 2.4V.
I didn't take much notice of this because the olimex website said the
debugger should be able to operate from appox 2.0V.

So I dug up my old bench PSU and applied the suggested voltage and
still no show.
I then begin turning the voltage up bit by bit then I heard the buzzer
go and the lcd with the message "www.olimex.com". Whoa break through
at last.
Then inserted the BSL and DEBUG jumper run the openocd config file and
it worked.

I like to confirm if things really work by performing a couple of
attempts. So I unplug my whole setup and reconnected then re-ran the
test and this time nothing happened.

So I took of the jumpers and reset the board hoping to see the led and
lcd working and to my greatest disappointment no show.

So I took out the old good DMM and started tracing the voltage from
the bridge rectifier(DB104 G2) output. May I point out the actual
device on my boards is a DB107 and not a DB104 as the schematic shows.

I then realized that the voltage gets to the input of Z1 (IN7433) but
nothing on the output.

Looking at the schematic I noticed that output of the zener diode is
fed into LM117 regulators which are capable of maximum input voltage
of 40V. See http://www.national.com/mpf/LM/LM117.html

I then later replaced the zener diode with a copper link. Applied
power to the target and it worked happily ever after.

I am now using the PSU from the olimex debugger and its running fine.

I just thought I should share this information since many people have
helped me during this ARM trying times.

If any one decides to remove this zener diode please not it is at own
risk.
I will however recommend a fixed 9V power supply block and measured
with a DMM before applying to target or use the olimex debugger
voltage output with the jumper correctly set.

Enjoy.

NB:
I am not sure if the image that caused the lcd to display
"www.olimex.com" was preprogrammed by olimex or not. I did however
received a hex file from Paul Curtis which I used for messing around.
When I was playing with Philip Flash utility under windows.

The effects of the image is Buzzer on, LED On and LCD displays
www.olimex.com

Regards
Ola Oni
--- In l...@yahoogroups.com, "oladipo_oni" wrote:
>
> Hi Paul,
>
> Sorry for the late response. I just picked up your message and noticed
> the power supply info that you gave.
>
> I will start by using a lab power supply and see if the jtag works.
> If that does work I will try programming the on board flash with your
> supplied hex file.
> I found a windows application that will allow me to program the flash.
> I would have ideally preferred a program that will allow me to program
> the flash in linux.
>
> I will keep you informed on what progress I make.
> Many thanks in advance.
>
> Regards
> Ola
> --- In l...@yahoogroups.com, "Paul Curtis" wrote:
> >
> > Ola,
> >
> > > Hi Paul,
> > >
> > > Based on your message about you having flashed this board (lpc-mt
> > > 2106) in the past I was wondering if it was possible for you to give
> > > me your binary file, so all I have to do is find an application that
> > > will allow me to program the on board flash through ISP.
> > >
> > > I don't need the code just the hex file, as I can write one when
I am
> > > up and running with the board.
> >
> > I am sending you a hex file which exercises the LCD and the LED on
> the 2106
> > board.
> >
> > Some notes on getting this to work on this particular board:
> >
> > 1. Program the hex file using ISP or whatever.
> > 2. Remove the BSL jumper.
> > 3. Remove the DBG jumper.
> > 4. Apply power the board at AT LEAST 10.5V!
> > 5. Turn on the power.
> > 6. Press the RST button and see if the LCD & LED work.
> >
> > Note that if don't follow these instructions, things won't work.
> You need
> > the 2106 not to go into the bootloader (BSL jumper), not to snatch
> the extra
> > pins for ETM (DBG jumper), it needs to be powered to work (10.5V)
and it
> > doesn't start up using a POR (hence press the RST button).
> >
> > Getting the LCD to work properly is fairly easy. And hopefully you
> should
> > be up and running with your stuff.
> >
> > ...heck, you're not even a CrossWorks customer!
> >
> > Regards,
> >
> > --
> > Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> > CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
------------------------------------



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )