Lpc2000

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

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 lpc2100@yahoogroups.com, "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 lpc2100@yahoogroups.com, "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 lpc2100@yahoogroups.com, "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 lpc2000@yahoogroups.com, 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

Hi all ...

I have an application where I would like to use a GPRS modem coupled
directly to the UART1's modem interface etc...
I have never worked with such a full modem interface before (RTS,CTS,DTR
etc...) so I was curious ... Do one have to control the modem signals in
software or  does the modem control this in hardware (for example .. if the
modem asks the UART to stop transmitting i guess the uart stops until it can
see that the signal isnt present any more and then resumes automatically as
long as the FIFO is full ?)

Another question is ....

I have a commercial FAT12/16/32 file system I would like to implent into the
2106 it occupies about 40KB of code in an AvR 8bit processor do you have any
idea what that would relate to (in KB) in the LPC ? (disregarding the
compilers optimization) what I mean is ... is 40KB code in an AvR the same
as 40KB code in an LPC ARM ?

Another this ...

Has anyone tried to interface a MMC/SD card to the LPC ... i know its
possible ofcause but what im thinking of is if its possible to use the /SS
pin to drive the ChipSelect (CS) on the SD card (can the /SS pin be
configured as an output and controlled in software?)

regards
lasse madsen

> 
> Another question is ....
> 
> I have a commercial FAT12/16/32 file system I would like to 
implent into the
> 2106 it occupies about 40KB of code in an AvR 8bit processor do 
you have any
> idea what that would relate to (in KB) in the LPC ? (disregarding 
the
> compilers optimization) what I mean is ... is 40KB code in an AvR 
the same
> as 40KB code in an LPC ARM ?

This may or may not help, its the only 8-bit uP to ARM/Thumb 
comparison I have to hand.

In another lifetime I had to find a way to remove 80%fsd spikes from 
a flammable gas detector, with less than 200 bytes remaining in the 
ROM space of an 8051 device.

The method I used recorded four history values, and selected the 
closest to the currently displayed reading as the next value to 
display. This worked nicely and also clamped a wandering-zero 
problem. This is obviously a very small example but uses table 
indexing, loops and 16-bit comparisons.

Compiling the function with an early version of Keil's C51 produced 
a 220 byte lump of code. Three hours work produced hand-optimized 
assembly code generating 108 bytes of code.

Some years later, purely for personal interest I compiled the 
original C using the ARM SDT200 compiler - 120 bytes of code. 
Compiling as Thumb code gave 86 bytes of code.

Unless you're doing very simple bit or byte copying with no 
arithmetic and very little decision-making, I would suspect that the 
ARM, or certainly the Thumb code would be more compact than code for 
an accumulator-bound 8-bit micro.

Peter.