Lpc2000

Hello group!

I am working on a design with LPC2114 and I want to use the MULTI
development environment for
the device.
I have connected the JTAG signals and the RTCK to a 20-pins connector,
ref. the ARM 20-pins connector refered to by Green Hills.

There are a few questions I want to put before the group:
- Is correct to force the RTCK signal low via 4.7 ohm resistor to enable
the debug port?

- The DBGSEL signal is described in the LPC2114/2124/2212/2214 manual, but
I can not find it on the LPC2114.
- Can I use the debug/Jtag signal for other purposes when the debug bus is
disabled?

- Does anybody have any experience with the LPC2000 and MULTI environment?

Best regards
Kirsti

Hi Kirsti,

you found a flaw in the User Manual pin description, sorry one of the
cut and paste errors.  Will be changed but might take a few weeks
until visible on the WWW.

The DBGSEL is a dedicated pin on the LPC2104/5/6 but entering debug
mode on the LPC2114 (all 64-pin devices) is different. Please check
the description of pins 1.20 and 1.26 in the data sheet. This
functionality replaces the DBGSEL pin.

Forcing RTCK low is necessary to enter debug mode.

The other answer whether you can use the JTAG pins for GP I/O if not
in debug mode, Yes you can, but think about it wheteher you really
want to do this. no more debugging of this functionality.

We decided (with some headache) to enable I/O on JTAG pins while not
in debug mode. 

Regards, Robert

--- In lpc2000@yahoogroups.com, kiaa@n... wrote:
> 
> 
> 
> 
> Hello group!
> 
> I am working on a design with LPC2114 and I want to use the MULTI
> development environment for
> the device.
> I have connected the JTAG signals and the RTCK to a 20-pins connector,
> ref. the ARM 20-pins connector refered to by Green Hills.
> 
> There are a few questions I want to put before the group:
> - Is correct to force the RTCK signal low via 4.7 ohm resistor to enable
> the debug port?
> 
> - The DBGSEL signal is described in the LPC2114/2124/2212/2214
manual, but
> I can not find it on the LPC2114.
> - Can I use the debug/Jtag signal for other purposes when the debug
bus is
> disabled?
> 
> - Does anybody have any experience with the LPC2000 and MULTI
environment?

> 
> Best regards
> Kirsti

10K pull down resistor on the RTCK pin is good enough to enable the 
debug port.
If the RTCK pin is connected to your JTAG box make sure
that when the sRST is asserted, the RTCK pin pulldown resistor
is good enough to fight the drive applied by the JTAG box on the RTCK 
pin. RTCK pin is an input to the JTAG box but this is something to 
watch out for.

A simple way to determine if your pulldown is effective (to enable 
the jtag port) or not is to hold the chip in reset with the JTAG box 
connected and measuring the voltage level on the RTCK pin. It should 
be in the range of 0.7-0.8 V.

--- In lpc2000@yahoogroups.com, kiaa@n... wrote:
> 
> 
> 
> 
> Hello group!
> 
> I am working on a design with LPC2114 and I want to use the MULTI
> development environment for
> the device.
> I have connected the JTAG signals and the RTCK to a 20-pins 
connector,
> ref. the ARM 20-pins connector refered to by Green Hills.
> 
> There are a few questions I want to put before the group:
> - Is correct to force the RTCK signal low via 4.7 ohm resistor to 
enable
> the debug port?
> 
> - The DBGSEL signal is described in the LPC2114/2124/2212/2214 
manual, but
> I can not find it on the LPC2114.
> - Can I use the debug/Jtag signal for other purposes when the debug 
bus is
> disabled?
> 
> - Does anybody have any experience with the LPC2000 and MULTI 
environment?

> 
> Best regards
> Kirsti

Hi Kirsti
Only bad experiences I'm afraid. We have purchased GreenHills Multi 2000 and
the probe for a couple of projects but I have been trying to use it along
with the LPC2106.
We had to get a firmware update for the probe before it would reliably reset
and run with the device, and now it has all been shipped off to GreenHills
technical support in the states so that they can get the probe to work with
breakpoints properly. Straightline code seems OK, but anything using
interrupts causes breakpoints to be skipped, wrong addresses to be
incremented, all sorts of fun.
At the moment it is also not possible to use the probe to program the device
flash. This means if you want to build and run from flash you have to use
the Philips bootloader to program the flash, then reconnect the probe and
start debugging with the hardware breakpoint.

We first received the kit before Christmas and still haven't had it back
again. We are not happy bunnies.

If you or anyone else do get it to work reliably please drop a note into the
group. We would be very grateful for any news, as at the moment we are at a
dead end.

Cheers
Simon

-----Original Message-----
--- In lpc2000@yahoogroups.com, kiaa@n... wrote:
> Hello group!
>
> I am working on a design with LPC2114 and I want to use the MULTI
> development environment for
> the device.

<snip!>
> - Does anybody have any experience with the LPC2000 and MULTI
environment?

>
> Best regards
> Kirsti