Different strokes for different folks, and even those folks differ their strokes for different folk. The cpu shouldn't be constrained by something that really is an easy fix just because it's not an issue in some apps. The next app that comes along it can be a real issue, such as this one. I don't live in a purist world where bit-banging is something odious, it may be down there and dirty, but it works. This is where little 8-bit'ers such as the ubicom and silabs parts don't hold back, grrrhhhh grrrhhh, lol. *Peter* Robert Adsett wrote: >Well I do embedded real-time control and pin toggling speed is not of great >importance for what I do. Different problem areas have different >constraints. I would expect that in some real-time embedded environments >that the capability to do high rate pin toggling would be seen as a reason >for caution since high toggling rates may imply fast edge rates with all >the implications that those have. > >I don't think Philips was expecting people to do a lot of high rate >bit-banging with these chips, but high-rate bit-banging and embedded >real-time are two different, but not exclusive, markets. You can have >either one without the other. >
Message
Re: [lpc2000] Re: port timing
2005-04-11 by Peter Jakacki
Attachments
- No local attachments were found for this message.