ETM and IO pins in debug mode

Started by Helge Fabricius-Hansen February 9, 2004
Hi,

In the manual it says that the ETM pins (P0.22-P0.32) are active
when DBGSEL and RTCK is high during RESET!

I am reading page 72 and page 206 in the LPC210x manual from Oct.
02, 2003.

Does this mean that P0.22 - P0.31 not can be used when using a JTAG
debugger?

My problem is that I get no respons on these pins when my jtag
debugger is connected. Nor can I change the value of them from
inside the debugger....!

Anyone with the same problem???

//Helge



An Engineer's Guide to the LPC2100 Series

Those pins are used for debuging, and can't be used during debuging.

Monday, February 9, 2004, 4:25:39 PM, si napisal:
> Hi,

> In the manual it says that the ETM pins (P0.22-P0.32) are active
> when DBGSEL and RTCK is high during RESET!

> I am reading page 72 and page 206 in the LPC210x manual from Oct.
> 02, 2003.

> Does this mean that P0.22 - P0.31 not can be used when using a JTAG
> debugger?

> My problem is that I get no respons on these pins when my jtag
> debugger is connected. Nor can I change the value of them from
> inside the debugger....!

> Anyone with the same problem???

> //Helge


> Yahoo! Groups Links





Is there no way to disable the ETM to be able to use the IO pins?

If not, I need to make a new target...

//Helge

--- In , "Helge Fabricius-Hansen"
<helge.fabricius@t...> wrote:
> Hi,
>
> In the manual it says that the ETM pins (P0.22-P0.32) are active
> when DBGSEL and RTCK is high during RESET!
>
> I am reading page 72 and page 206 in the LPC210x manual from Oct.
> 02, 2003.
>
> Does this mean that P0.22 - P0.31 not can be used when using a
JTAG
> debugger?
>
> My problem is that I get no respons on these pins when my jtag
> debugger is connected. Nor can I change the value of them from
> inside the debugger....!
>
> Anyone with the same problem???
>
> //Helge





As I know JTAG uses pin 0.17 to 0.21. Those are primary JTAG pins. If
you use secondary jtag pins, you get some pins othervise used by ETM
freed. Secondary JTAG is configured in software(pin connect block).
Secondary JTAG pins are 0.27 to 0.31.

Pero

> Is there no way to disable the ETM to be able to use the IO pins?

> If not, I need to make a new target...

> //Helge

> --- In , "Helge Fabricius-Hansen"
> <helge.fabricius@t...> wrote:
>> Hi,
>>
>> In the manual it says that the ETM pins (P0.22-P0.32) are active
>> when DBGSEL and RTCK is high during RESET!
>>
>> I am reading page 72 and page 206 in the LPC210x manual from Oct.
>> 02, 2003.
>>
>> Does this mean that P0.22 - P0.31 not can be used when using a
> JTAG
>> debugger?
>>
>> My problem is that I get no respons on these pins when my jtag
>> debugger is connected. Nor can I change the value of them from
>> inside the debugger....!
>>
>> Anyone with the same problem???
>>
>> //Helge


> Yahoo! Groups Links




--- In , "Helge Fabricius-Hansen"
<helge.fabricius@t...> wrote:
> Hi,
>
> In the manual it says that the ETM pins (P0.22-P0.32) are active
> when DBGSEL and RTCK is high during RESET!
>
> I am reading page 72 and page 206 in the LPC210x manual from Oct.
> 02, 2003.
>
> Does this mean that P0.22 - P0.31 not can be used when using a JTAG
> debugger?
>
> My problem is that I get no respons on these pins when my jtag
> debugger is connected. Nor can I change the value of them from
> inside the debugger....!
>
> Anyone with the same problem???
>
> //Helge

Helge,
To use those pins durring debug, you must use the secondary JTAG
port, to do this you must have connections for BOTH primary, and
secondary JTAG ports. Your code must enable the PIN Sel functions for
the secondary JTAG port, and then it may be used, and you only lose
the upper pins.

Scan the previous posts, as we have discussed the solution before.



Jim Beagley wrote:

> Helge,
> To use those pins durring debug, you must use the secondary JTAG
> port, to do this you must have connections for BOTH primary, and
> secondary JTAG ports. Your code must enable the PIN Sel functions for
> the secondary JTAG port, and then it may be used, and you only lose
> the upper pins.
>
> Scan the previous posts, as we have discussed the solution before.
>

I've not yet read that section of the LPC manual in detail (I aim to use
the UART for ISP rather than JTAG), so would anyone fancy writing a
short paragraph about the primary/secondary JTAG and what pins they use
up that I can put on the Wiki?

If you don't fancy writing your own Wiki markup, just email me some text
and I'll put it in for you.

I think this is going to be a frequently asked question, you see...

ABS



If you're going to use UART ISP, just connect max3232 touart ena and
use lpc21xx isp utility. ISP is enter by holding P0.14 low during
reset. All other pins are free to use. Pero
---
http://www2.arnes.si/~pkuhar/

Monday, February 9, 2004, 7:19:33 PM, si napisal:
> Jim Beagley wrote:

>> Helge,
>> To use those pins durring debug, you must use the secondary JTAG
>> port, to do this you must have connections for BOTH primary, and
>> secondary JTAG ports. Your code must enable the PIN Sel functions for
>> the secondary JTAG port, and then it may be used, and you only lose
>> the upper pins.
>>
>> Scan the previous posts, as we have discussed the solution before.
>>

> I've not yet read that section of the LPC manual in detail (I aim to use
> the UART for ISP rather than JTAG), so would anyone fancy writing a
> short paragraph about the primary/secondary JTAG and what pins they use
> up that I can put on the Wiki?

> If you don't fancy writing your own Wiki markup, just email me some text
> and I'll put it in for you.

> I think this is going to be a frequently asked question, you see...

> ABS

> Yahoo! Groups Links





Peter Kuhar wrote:
> If you're going to use UART ISP, just connect max3232 touart ena and
> use lpc21xx isp utility. ISP is enter by holding P0.14 low during
> reset. All other pins are free to use.

I know - that's the one I *have* researched, since I plan to do it. I've
skimmed over the JTAG stuff, however!

Lots of people seem to be interested in the secondary JTAG interface, so
I'm keen to get a description of the tradeoffs and issues put up on a
page so we can just point people at it when they ask rather than needing
to go through it each time.

ABS



I you plan to use secodary JTAG:
- Seconday JTAG is enabled in software so you need same other way(UART) to
program it for the first time.

Pero

Monday, February 9, 2004, 7:42:15 PM, si napisal:
> Peter Kuhar wrote:
>> If you're going to use UART ISP, just connect max3232 touart ena and
>> use lpc21xx isp utility. ISP is enter by holding P0.14 low during
>> reset. All other pins are free to use.

> I know - that's the one I *have* researched, since I plan to do it. I've
> skimmed over the JTAG stuff, however!

> Lots of people seem to be interested in the secondary JTAG interface, so
> I'm keen to get a description of the tradeoffs and issues put up on a
> page so we can just point people at it when they ask rather than needing
> to go through it each time.

> ABS

> Yahoo! Groups Links





I have the same problem in my project : I plan to use P0.22 to P0.31
as GPIO, but when primary JTAG is pluged in those pins are unusable.
Well, I don't understand why Philips didn't think about this case,
we don't necessary need ETM port for debugging (just only 10 pins
lost ... this is the case the Ashling dev'card when you only use
embedded debugger).

Benjamin PRADAYROL

--- In , Peter Kuhar <peter.kuhar@g...> wrote:
> I you plan to use secodary JTAG:
> - Seconday JTAG is enabled in software so you need same other way
(UART) to
> program it for the first time.
>
> Pero
>
> Monday, February 9, 2004, 7:42:15 PM, si napisal:
> > Peter Kuhar wrote:
> >> If you're going to use UART ISP, just connect max3232 touart
ena and
> >> use lpc21xx isp utility. ISP is enter by holding P0.14 low
during
> >> reset. All other pins are free to use.
>
> > I know - that's the one I *have* researched, since I plan to do
it. I've
> > skimmed over the JTAG stuff, however!
>
> > Lots of people seem to be interested in the secondary JTAG
interface, so
> > I'm keen to get a description of the tradeoffs and issues put up
on a
> > page so we can just point people at it when they ask rather than
needing
> > to go through it each time.
>
> > ABS >
>
> > Yahoo! Groups Links