--- In lpc2000@yahoogroups.com, "rtstofer" <rstofer@...> wrote: > > --- In lpc2000@yahoogroups.com, "Doug Collins" <dougc@> wrote: > > > > > > Richard wrote: > > > > >I'm looking at Table 48 Pin Description For LPC2131/2132/2138 > > >(page 77) and the entry for P0.14 where there is an 'Important' > > >note describing the use of P0.14. This is in the User Manual > > >dated November 22, 2004. Am I looking at the wrong thing? > > > > Yep, that's the wrong thing, or at least the old thing. The current > user > > manual is Rev 0.1, 11 - January 2006 > > > > I do see the comment you're referring to in the System Control Block > section > > of the manual, section 3.2. It's also discussed in Chapter 19, > Flash Memory > > System and Programming. What I don't see is a single word about the > special > > usage of this pin in Chapter 6 or 7 which deal directly with > configuring pin > > functionality. A note in section 6.2 "Pin Descriptions" would > certainly be > > nice. > > > > Assuming that table 58 in the current manual corresponds to table 48 old > > manual it looks like Philips removed this "Important Note". Maybe they > > should put it back? > > > > Doug > > > > A Mind is Like A Parachute. Works Best When Open > > > > Ah! Now I understand. The really good news is that I can't even find > the Jan 2006 edition. I have wandered all over Google and a couple of > Philips sites and not a trace. > > I even started at the recommended site with no luck. I did find a > newer version (24 JUN 2005) where the bootloader function of P0.14 is > now just a "Note:..." > > Richard > How in the world I got off on the wrong chip completely escapes me! Duh! I did find the LPC2103 User Manual dated Jan 2006. A perfectly good warning in an older User Manual is certainly omitted in the 2103. I see the other requirement is to provide a pull-up resistor so the pin doesn't float into an undefined state during reset. I think I knew that but now I'm certain. Richard
Message
Re: LPC2103 users manual sucks
2006-04-11 by rtstofer
Attachments
- No local attachments were found for this message.