Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Broken IO Pins?

2006-05-22 by Dave Such

I found that 1K works well running clock rates of 400K.  Anything larger 
caused slow rise times.


John Stamos wrote:

> Can someone recommend a good resistor value to use for the pullup 
> resistor?
>  
>   Much Thanks.
>
> Robert Adsett <subscriptions@...> wrote:        At 
> 06:36 PM 5/20/06 +0000, jstamos111 wrote:
>   >Hey guys,
>   >
>   >This problem has me completely baffled.  Hopefully you can help.
>   >
>   >I have an LPC2106 running on a board of my own design and am using
>   >Keil tools to compile the code.  Here's my very short code:
>   >
>   >void main() {
>   >PINSEL0 &= 0x00000000;
>   >IODIR0 = 0xFFFFFFFF;
>   >IOSET0 = 0xFFFFFFFF;
>   >while(1);
>   >}
>   >
>   >The problems when I run this code all IO ports turn on except P0.2,
>   >P0.3 and P0.26.  Any idea why?  I tried looking in the documentation
>   >but couldn't find anything specific about these ports not working for
>   >IO.  I thought maybe the problem was what I had the pins connected to
>   >(a CPLD) so I made sure to put the connected CPLD pins as inputs and
>   >even disconnected one pin completely and still the same problem.  I
>   >have multiple boards and it does it for at least two of them.
>  
>   Well P0.2 & P0.3 are open collector so they'll need pull-ups.  See
>   http://www.open-research.org.uk/ARMuC/LPC2100Tips.html
>  
>   P0.26 I don't see anything off hand unless you have JTAG enabled.
>  
>   Robert
>  
>   " 'Freedom' has no meaning of itself.  There are always 
> restrictions,   be
>   they legal, genetic, or physical.  If you don't believe me, try to 
> chew a
>   radio signal. "  -- Kelvin Throop, III
>   http://www.aeolusdevelopment.com/
>  
>                  
>
>           SPONSORED LINKS   
>                                                         
> Microcontrollers                                          
> Microprocessor                                          Intel 
> microprocessors                                                                             
>
>        
> ---------------------------------
>     YAHOO! GROUPS LINKS 
>  
>      
>     Visit your group "lpc2000" on the web.
>     
>     To unsubscribe from this group, send an email to:
> lpc2000-unsubscribe@yahoogroups.com
>     
>     Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 
>  
>      
> ---------------------------------
>  
>  
>          
>
>            
> ---------------------------------
> Love cheap thrills? Enjoy PC-to-Phone  calls to 30+ countries for just 
> 2ยข/min with Yahoo! Messenger with Voice.
>
> [Non-text portions of this message have been removed]
>
>
>
> SPONSORED LINKS
> Microcontrollers 
> <http://groups.yahoo.com/gads?t=ms&k=Microcontrollers&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&c=3&s=69&.sig=c-HXthtbZy4TZbI3ib0PMg> 
> 	Microprocessor 
> <http://groups.yahoo.com/gads?t=ms&k=Microprocessor&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&c=3&s=69&.sig=ijt0SspWtjogcHCuFD0lUQ> 
> 	Intel microprocessors 
> <http://groups.yahoo.com/gads?t=ms&k=Intel+microprocessors&w1=Microcontrollers&w2=Microprocessor&w3=Intel+microprocessors&c=3&s=69&.sig=WOZdpklkgHbXR5quAgrl5w> 
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "lpc2000
>       <http://groups.yahoo.com/group/lpc2000>" on the web.
>        
>     *  To unsubscribe from this group, send an email to:
>        lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>


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

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.