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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
08/25/06 05:52
Read: times


 
#122986 - Looks clear enough to me
Responding to: ???'s previous message
Jon Ledbetter said:
yeah, I read that. Now show me how that answers the original question that I asked.

OK: the original question was:
... I want to call P2.4 by a name like SW1?

Now, you say
It just seems so much more complicated to get the desired results than from assembler.

If you're happy that you could easily do this in assembler, then you must understand that you're trying to access an individual bit within an SFR - this should take you directly to the manual section on SFRs:
http://sdcc.sourceforge.net/doc/sdccm...0000000000

There you will see the syntax for an SFR bit:
__sbit __at (0xd7) CY; /* CY (Carry Flag) */ 
That seems clear enough to me - you just need to change the CY bit address in that example from 0xD7 to the bit address that you require; ie,
__sbit __at (0xA4) SW1; /* P2.4 */ 
QED!

List of 32 messages in thread
TopicAuthorDate
SDCC Nooby Question            01/01/70 00:00      
   Ok got it            01/01/70 00:00      
      it\'s ok in Keil            01/01/70 00:00      
         Yes...            01/01/70 00:00      
            The reason is...            01/01/70 00:00      
               C first            01/01/70 00:00      
                  Learning C            01/01/70 00:00      
                     if this is cut and paste then            01/01/70 00:00      
                        Semi-colon was it            01/01/70 00:00      
                           C is fidgety about error declaration            01/01/70 00:00      
                           Syntax error            01/01/70 00:00      
                              Going back and looking...            01/01/70 00:00      
                                 It means            01/01/70 00:00      
                                    Preprocessor output            01/01/70 00:00      
                                 explanation            01/01/70 00:00      
                        Semicolon            01/01/70 00:00      
                           yes, Andy you are absolutely correct            01/01/70 00:00      
                              Semicolon - example            01/01/70 00:00      
                           backwards            01/01/70 00:00      
                              HUH?            01/01/70 00:00      
                                 try this            01/01/70 00:00      
                     Dallas app notes            01/01/70 00:00      
                     False economy            01/01/70 00:00      
                        OK            01/01/70 00:00      
                     Learning from the tools            01/01/70 00:00      
                        #define and the preprocessor            01/01/70 00:00      
                           are you sure?            01/01/70 00:00      
                              Yes!            01/01/70 00:00      
                           Hmmm...            01/01/70 00:00      
   SDCC Manual            01/01/70 00:00      
      Err... ya think?            01/01/70 00:00      
         Looks clear enough to me            01/01/70 00:00      

Back to Subject List