Apr 27, 2011 #1 tahir4awan Full Member level 4 Joined Nov 29, 2010 Messages 209 Helped 16 Reputation 32 Reaction score 17 Trophy points 1,308 Location Germany Activity points 3,096 There is a confusion when assigning individual pins of Port. PORTB.RB0 and PORTB.F0 both works same. But I dont understand the term F0 What does it mean?
There is a confusion when assigning individual pins of Port. PORTB.RB0 and PORTB.F0 both works same. But I dont understand the term F0 What does it mean?
Apr 27, 2011 #2 bigdogguru Administrator Joined Mar 12, 2010 Messages 9,821 Helped 2,350 Reputation 4,694 Reaction score 2,272 Trophy points 1,413 Location Southwest, USA Activity points 62,387 Just another #define in the header file, probably kept for legacy code. Find the header for the PIC you're using and take a look inside.
Just another #define in the header file, probably kept for legacy code. Find the header for the PIC you're using and take a look inside.
Apr 27, 2011 #3 tahir4awan Full Member level 4 Joined Nov 29, 2010 Messages 209 Helped 16 Reputation 32 Reaction score 17 Trophy points 1,308 Location Germany Activity points 3,096 I think it is built in function of mikroC and it works without defining it.
Apr 27, 2011 #4 bigdogguru Administrator Joined Mar 12, 2010 Messages 9,821 Helped 2,350 Reputation 4,694 Reaction score 2,272 Trophy points 1,413 Location Southwest, USA Activity points 62,387 You don't have to #define PORTB.F0, like you don't have to #define PORTB.RB0. MikroE likes to hide their inner works of their compilers, so if it's not in a header, .c or asm file, it's a precompiled lib which is then linked with your code.
You don't have to #define PORTB.F0, like you don't have to #define PORTB.RB0. MikroE likes to hide their inner works of their compilers, so if it's not in a header, .c or asm file, it's a precompiled lib which is then linked with your code.