Lpc2000

Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now

On Fri, 27 Feb 2004 11:32:26 +0000 (GMT), Aminder Athwal wrote:

Hi,
I am using the LCP2106 and am having trouble getting the SPI to work,
I will be using it to control a nokia 3310 LCD screen I have got this
screen to work with out using the SPI but wanted to use SPI as I have
two other components that will also need to use this.

=====================================================================

I think this showed up on the list a while back.  To operate as a SPI
MASTER, the SSEL pin must be enabled (not left as a GPIO pin) and be
held LOW throughout the data transfer.  If it goes high during the
transfer, the transfer will abort.  The LPC data book I have has
conflicting information about at which level the SSEL signal must be
held (high or low) but the rest is spelled out plainly.

-Bill Knight
R O SoftWare

I have got the SPI working and the Nokia screen now display 
characters fine. No problem with the software, when running the SPI 
on the LPC2106 in master mode - P0.7 needs to be pulled up to 3.3v!


--- In lpc2000@yahoogroups.com, Aminder Athwal <aminderathwal@y...> 
wrote:
> Hi,
> I am using the LCP2106 and am having trouble getting the SPI to 
work,
> I will be using it to control a nokia 3310 LCD screen I have got 
this screen to work with out using the SPI but wanted to use SPI as I 
have two other components that will also need to use this.
>  
>  
> Can any one offer any help???
>  
> Thanks
>  
> Aminder
> 
> 		
> ---------------------------------
>   Yahoo! Messenger - Communicate instantly..."Ping" your friends 
today! Download Messenger Now

Reading through the message archives, I see conflicting information on
the SPI SSEL pin.  Bill Knight says the SPI SSEL pin must be pulled low
for the LPC210X to operate as an SPI master, but Aminder says it needs
to be pulled to 3.3V.  Page 127 of the user manual (that I have) implies
that this pin could be used as a GPIO in SPI master mode, and the manual
gives no mandate on the use of this pin in master mode.

What should I do with this pin?

I think I know the answer, but just to be perfectly clear..

Is there any way to disable the ETM port and use these pins for other
functions when using the primary JTAG port?

The SPI SSEL pin must be high in Master mode!
If it goes low in master mode the SPI will change
to slave mode.

//Helge

-----Ursprungligt meddelande-----
Fran: James Dabbs [mailto:jdabbs@...]
Skickat: den 2 mars 2004 14:10
Till: lpc2000@yahoogroups.com
Amne: [lpc2000] SPI SSEL Pin


Reading through the message archives, I see conflicting information on
the SPI SSEL pin.  Bill Knight says the SPI SSEL pin must be pulled low
for the LPC210X to operate as an SPI master, but Aminder says it needs
to be pulled to 3.3V.  Page 127 of the user manual (that I have) implies
that this pin could be used as a GPIO in SPI master mode, and the manual
gives no mandate on the use of this pin in master mode.

What should I do with this pin?




 
Yahoo! Groups Links

The purpose of my post was to indicate the SSEL pin must be used
and tied to the appropriate level for the SPI to operate.  Even if
used in MASTER mode.  I had remembered the level incorrectly but
thought the message indicated it was a guess and should be checked.
I found the following in my LPC2114/2124/2212/2214 manual.

Note: LPC___ configured to operate as SPI master MUST select SSEL functionality on
an apropriate pin and have HIGH level on this pin in order to act as a master.


Sorry about the confusion.

-Bill Knight
R O SoftWare



On Tue, 2 Mar 2004 08:10:22 -0500, James Dabbs wrote:

Reading through the message archives, I see conflicting information on
the SPI SSEL pin.  Bill Knight says the SPI SSEL pin must be pulled low
for the LPC210X to operate as an SPI master, but Aminder says it needs
to be pulled to 3.3V.  Page 127 of the user manual (that I have) implies
that this pin could be used as a GPIO in SPI master mode, and the manual
gives no mandate on the use of this pin in master mode.

What should I do with this pin?





Yahoo! Groups Links

OK.  I am no convinced that this answer is NO.  I am now bringing the
secondary JTAG pins out to the debug header, instead of the primary JTAG
pins.  In my system, this seems to imply the following important
considerations:

1. I cannot image an unprogrammed part through my JTAG connector.  I
will have to do this through the serial port.

2. I need to leave DBGSEL unconnected or pull it low at all times.

3. I will have to put something in my code to select the secondary JTAG
pins in the PINSEL1 register EARLY in the boot process.  Once these
instructions have executed, my JTAG debugger will be able to communicate
with the chip.

4. If I push the reset button, I'll lose debug control of the chip until
#3 executes.  I.e., I won't be able to single step through the reset
vector, etc.

Is there anything else I need to think about?

Thanks.

Read this post about the RTCK if you want second and subsequent
flashing via the secondary JTAG port.

http://groups.yahoo.com/group/lpc2000/message/1067


--- In lpc2000@yahoogroups.com, "James Dabbs" <jdabbs@t...> wrote:
> OK.  I am no convinced that this answer is NO.  I am now bringing 
the
> secondary JTAG pins out to the debug header, instead of the primary 
JTAG
> pins.  In my system, this seems to imply the following important
> considerations:
> 
> 1. I cannot image an unprogrammed part through my JTAG connector.  I
> will have to do this through the serial port.
> 
> 2. I need to leave DBGSEL unconnected or pull it low at all times.
> 
> 3. I will have to put something in my code to select the secondary 
JTAG
> pins in the PINSEL1 register EARLY in the boot process.  Once these
> instructions have executed, my JTAG debugger will be able to 
communicate
> with the chip.
> 
> 4. If I push the reset button, I'll lose debug control of the chip 
until

> #3 executes.  I.e., I won't be able to single step through the reset
> vector, etc.
> 
> Is there anything else I need to think about?
> 
> Thanks.

> Read this post about the RTCK if you want second and subsequent
> flashing via the secondary JTAG port.

> http://groups.yahoo.com/group/lpc2000/message/1067

Ugh..

What is the *purpose* of RTCK, and why does it interfere with flashing the
chip?  Is this normal, or an LPC bug, or a Nohau issue?  Is there ever a
reason to connect it to the 20-way header?

--- In lpc2000@yahoogroups.com, "James Dabbs" <jdabbs@t...> wrote:
> > Read this post about the RTCK if you want second and subsequent
> > flashing via the secondary JTAG port.
> 
> > http://groups.yahoo.com/group/lpc2000/message/1067
> 
> Ugh..
> 
> What is the *purpose* of RTCK, and why does it interfere with 
flashing the
> chip?  Is this normal, or an LPC bug, or a Nohau issue?  Is there 
ever a
> reason to connect it to the 20-way header?

The RCTK is used by some debuggers for "adaptive clocking", in fact a 
clock feedback system enabling the debugger to run at highest 
possible speed. As far as I know, only a few high-end adapters are 
using this. Here is an answer to the same question from the ARM home 
page:

--------
"RTCK is only used by the JTAG emulator (Multi-ICE or RealView ICE) 
when it is configured in adaptive clocking mode. Adaptive clocking 
ensures that the TCK is slow enough to work with a synthesizable core 
and that its frequency is near the maximum possible. 

In most cases, adaptive clocking is "nice to have" but it is not 
really necessary. You just need to set up TCK with a frequency slow 
enough for your target. In this case you don't need to take RTCK to a 
pin of the ASIC. RTCK on the JTAG connector should be pulled-down."

However, adaptive clocking is necessary when debugging a target with 
variable clock speed. This way the JTAG frequency is always near the 
maximum possible. Without adaptive clocking you would need to set TCK 
at very low frequency, so that it works with all the possible clock 
speeds."
-------

As seen from this, connecting the RTCK is not required. However, I 
have been struggling with the "secondary JTAG problem" myself. And 
unfortunately, not connecting RTCK does not seem to have much effect. 

I have two IAR kick-start boards with the LPC2106 of the same batch. 
On one, the secondary JTAG works OK. On the other, it only works 
after first having used primary connector. See also message 1262. 

Hope Philips can give a good advice!

Jon

--- In lpc2000@yahoogroups.com, "Helge Fabricius-Hansen" 
<helge.fabricius@t...> wrote:
> 
> The SPI SSEL pin must be high in Master mode!
> If it goes low in master mode the SPI will change
> to slave mode.
> 
> //Helge
> 
> -----Ursprungligt meddelande-----
> Fran: James Dabbs [mailto:jdabbs@t...]
> Skickat: den 2 mars 2004 14:10
> Till: lpc2000@yahoogroups.com
> Amne: [lpc2000] SPI SSEL Pin
> 
> 
> Reading through the message archives, I see conflicting 
information on
> the SPI SSEL pin.  Bill Knight says the SPI SSEL pin must be 
pulled low
> for the LPC210X to operate as an SPI master, but Aminder says it 
needs
> to be pulled to 3.3V.  Page 127 of the user manual (that I have) 
implies
> that this pin could be used as a GPIO in SPI master mode, and the 
manual
> gives no mandate on the use of this pin in master mode.
> 
> What should I do with this pin?
> 
> 
> 
> 
>  
> Yahoo! Groups Links

The SPI SSEL pin must be pulled high in MASTER mode.  Also this 
pins  could not be used  as a GPIO pins in SPI mode. You have to 
set 14 bit  in PINSEL0 register.

And final question! Can someone put here the exact init code for the 
SPI regs.
 I use:
  PINSEL0 = 0x00005500;
  IODIR = 0x00000080; // pin P0.3 is IO driven CS
  S0SPCR = 0x78;
  S0SPCCR = 0x0F;
****************************************************
pin P0.7 is conected to +3.3V!
But still no activity on SPI bus :(

Hello,

I need to capture a single frame from live PAL video signal and store as 
a bitmap. Any ideas for interfacing video signal to LPC2138?

Thanks.

Marko

Zivjo Marko !

Zposlen sem v podjetju kjer razvijamo/izdelujemo merilce gledanosti TV. Na podrocju zajema in obdelave slike imamo kar nekaj izkusenj, tako da ce malo boljse opises problem, ti lahko kaj svetujem oz. namignem kaj, kar smo mi uporabili pri nasi resitvi.

lp,
marko

> 
> Od: Marko Pavlin <mp@...>
> Datum: 2005/03/21 Pon PM 02:26:16 CET
> Za: lpc2000@yahoogroups.com
> Zadeva: [lpc2000] Capturing image with LPC2100
> 
> 
> Hello,
> 
> I need to capture a single frame from live PAL video signal and store as 
> a bitmap. Any ideas for interfacing video signal to LPC2138?
> 
> Thanks.
> 
> Marko
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
>

Hi All,

I am verry sorry for this mail. I was not intending to replay to the LPC group.

Sorry again !

marko

> 
> Od: Marko Panger <marko.panger@...>
> Datum: 2005/03/21 Pon PM 02:57:58 CET
> Za: <lpc2000@yahoogroups.com>
> Zadeva: [lpc2000] Capturing image with LPC2100
> 
> 
> Zivjo Marko !
> 
> Zposlen sem v podjetju kjer razvijamo/izdelujemo merilce gledanosti TV. Na podrocju zajema in obdelave slike imamo kar nekaj izkusenj, tako da ce malo boljse opises problem, ti lahko kaj svetujem oz. namignem kaj, kar smo mi uporabili pri nasi resitvi.
> 
> lp,
> marko
> 
> 
> > 
> > Od: Marko Pavlin <mp@...>
> > Datum: 2005/03/21 Pon PM 02:26:16 CET
> > Za: lpc2000@yahoogroups.com
> > Zadeva: [lpc2000] Capturing image with LPC2100
> > 
> > 
> > Hello,
> > 
> > I need to capture a single frame from live PAL video signal and store as 
> > a bitmap. Any ideas for interfacing video signal to LPC2138?
> > 
> > Thanks.
> > 
> > Marko
> > 
> > 
> >  
> > Yahoo! Groups Links
> > 
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
>