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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
09/08/09 00:45
Modified:
  09/08/09 00:46

Read: times


 
#168787 - Well, what you CAN do ...
Responding to: ???'s previous message
How about just the
movx a,@dptr
followed by
movx @dptr,a
1024 times?

I don't know that there are other MCU's that offer the same automatic DPTR manipulations but if there were a 24 MHz 12-clocker MCU with those features it would still be quite advantageous, wouldn't it, at least if you were in a terrible hurry.

There's no counting, no testing, no nothing. Just the consumption of 2KB of code space. You can, of course, count just a little bit, and use only 512 bytes, or more, or less, depending on how much time you want to save. If you do the 1k repetitions, it's not even a loop, so it's really not "unrolled."

On a 12-clocker, that would be 24 clock cycles per byte, wouldn't it? or, at 24 MHz, it would be 1k microseconds, don't you think? It could be tailored to the timing constraints in order to conserve code space. Of course, if he doesn't want to use the Maxim/Dallas part, or if he needs features it doesn't offer ...

RE


List of 11 messages in thread
TopicAuthorDate
Fastest way to fill buffer            01/01/70 00:00      
   something like this            01/01/70 00:00      
   when software hits limits...            01/01/70 00:00      
      auto-increment            01/01/70 00:00      
         Two questions ..            01/01/70 00:00      
         But Gonzallo unrolled it already isn't it?            01/01/70 00:00      
            Yes, but not with the hardware increment            01/01/70 00:00      
                be specific            01/01/70 00:00      
                  Don't forget about the Maxim/Dallas parts!            01/01/70 00:00      
            what to unroll            01/01/70 00:00      
               Well, what you CAN do ...            01/01/70 00:00      

Back to Subject List