Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
02/18/08 20:03
Modified:
  02/18/08 20:12

Read: times


 
#151044 - Couldn\'t use of a different crystal solve this?
Responding to: ???'s previous message
If there's a timer or two available for an ISR, couldn't that also serve to create the required baud rates (the O/P hasn't said whether that's even called-for) and then allow the core to be clocked at some rate that's a harmonic of the desired counter frequencies? If one 16-bit counter can create the interrupt that software counts, having it at an integral multiple of the desired interval would be useful, wouldn't it?

Locking one's timing to a specific baud-rate generator crystal can prove a serious disadvantage under some circumstances, e.g. this case. It is not unsolvable with the "old, tried-and-true" crystal but if it's convenient, why not try, say, 24 MHz? You can get "close enough" to standard baud rates with that. Aside from that, dividing 11059200 by 49152 in a 16-bit counter leaves a divide-by-225 to generate 1 second.

RE


List of 10 messages in thread
TopicAuthorDate
11.059Mhz clock to create 1-30 second delay in C?            01/01/70 00:00      
   as far as I remember...            01/01/70 00:00      
      It's worse than that, Jim            01/01/70 00:00      
   solution?            01/01/70 00:00      
   Not nested loops!            01/01/70 00:00      
      I'll check those out tonight after work            01/01/70 00:00      
         delay needs to be centered around 5 seconds or so            01/01/70 00:00      
            Samuel Clemens said            01/01/70 00:00      
               Couldn\'t use of a different crystal solve this?            01/01/70 00:00      
                  I wonder            01/01/70 00:00      

Back to Subject List