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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
11/11/08 16:04
Read: times


 
#159952 - wrong, nonstandard and why
Responding to: ???'s previous message
ORL iram addr,#data

by using the ORL istruction you can SET any bit in any iram byte address 0x00 - 0xFF range.
the #data should be an ace '1' to the desired position.
eg:
Save This Code ORL 34h, #0b01000000

1) the above code is wrong for addresses 80-ff which is not stated
2) IRAM is the standard name for for addresses 80-ff for which the code example does not work
3) why even do these explanations, it is far better documented in "the bible" chapter 2

Erik

here are the links to "the bible"
Chapter 1 - 80C51 Family Architecture:
http://www.nxp.com/acrobat_d...ARCH_1.pdf

Chapter 2 - 80C51 Family Programmer’s Guide and Instruction Set:
http://www.nxp.com/acrobat_d...UIDE_1.pdf

Chapter 3 - 80C51 Family Hardware Description:
http://www.nxp.com/acrobat_d...WARE_1.pdf





List of 34 messages in thread
TopicAuthorDate
a simple SETB question            01/01/70 00:00      
   SETB from 20h to 2FH            01/01/70 00:00      
      assembler missed this one            01/01/70 00:00      
         I know of none that can't            01/01/70 00:00      
   what about this?            01/01/70 00:00      
      try ORL to set any bit in internal RAM            01/01/70 00:00      
         wrong, nonstandard and why            01/01/70 00:00      
            ORL, Set any bit (more informative)            01/01/70 00:00      
               iram            01/01/70 00:00      
                  Where is that defined?            01/01/70 00:00      
                     my word was not 'defined' but            01/01/70 00:00      
                        a rose, by any other name ...            01/01/70 00:00      
                           I think Erik has it?            01/01/70 00:00      
                              aliased/overlayed            01/01/70 00:00      
                                 Fair enough            01/01/70 00:00      
                              pDATA?            01/01/70 00:00      
                                 Why do you think 64TB would be enough?            01/01/70 00:00      
                                    It would not be            01/01/70 00:00      
                                       Tools are important for size            01/01/70 00:00      
                                          That's why there's ASM to use instead            01/01/70 00:00      
                                       this flies against some previous posts of yours            01/01/70 00:00      
                                          It's like herding cats            01/01/70 00:00      
                                             Flame bait?            01/01/70 00:00      
                                                No ... not really            01/01/70 00:00      
                                                   yes            01/01/70 00:00      
                                 PDATA & XDATA            01/01/70 00:00      
                                    I won't argue that ... but ...            01/01/70 00:00      
                                       Agreed, but...            01/01/70 00:00      
                                          It is seldom that simple ...            01/01/70 00:00      
                                             That's the point!            01/01/70 00:00      
                                             since you are really interested            01/01/70 00:00      
                                                Thanks!            01/01/70 00:00      
      Yes, that is the way I normally do it            01/01/70 00:00      
      WHY TO DISTURB ACC ?            01/01/70 00:00      

Back to Subject List