Ccs Help

[lsis]

Any idea for assign (pin_c0, pin_b2 , pin_d3 .....) with int16 variable.

[metal]

Hi

The guy needs to do the following;

He creats a 16 bit variable:

int16 var;

Now he wants to assign PIN_A0 for example to one of the var bits, say:

PIN_A0 = var.3; or vice versa.

So that PIN_A0 will change when the 3rd bit in var is changed, or viceversa.

How can he do such a thing ?

Thanks to all

[lsis]

Thank's METAL.

Now the solution.

// ISD25120 TO PIC18F452 ADDRESS PINS. //
#BIT ISDADRS0 = 0XF82.0
#BIT ISDADRS1 = 0XF84.2
#BIT ISDADRS2 = 0XF84.1
#BIT ISDADRS3 = 0XF84.0
#BIT ISDADRS4 = 0XF80.5
#BIT ISDADRS5 = 0XF80.4
#BIT ISDADRS6 = 0XF80.3
#BIT ISDADRS7 = 0XF80.2
#BIT ISDADRS8 = 0XF80.1
#BIT ISDADRS9 = 0XF80.0
// ISD25120 DIRECT ADDRESS MACRO FUNCTION. //
#define ISDADRS(x) \
ISDADRS0 = x & 1; \
ISDADRS1 = (x >> 1) & 1; \
ISDADRS2 = (x >> 2) & 1; \
ISDADRS3 = (x >> 3) & 1; \
ISDADRS4 = (x >> 4) & 1; \
ISDADRS5 = (x >> 5) & 1; \
ISDADRS6 = (x >> 6) & 1; \
ISDADRS7 = (x >> 7) & 1; \
ISDADRS8 = (x >> & 1; \
ISDADRS9 = (x >> 9) & 1

With this macro we have only to change x at ISDADRS(x).

[metal]

Hi isis

Can you explain more plz, I don't understand any thing now  :confused:

[lsis]

What is so dificult ?

// ISD25120 TO PIC18F452 ADDRESS PINS. //
#BIT ISDADRS0 = 0XF82.0                                  // here is the address of pin_c0
#BIT ISDADRS1 = 0XF84.2                                  // here is the address of pin_e3
#BIT ISDADRS2 = 0XF84.1
#BIT ISDADRS3 = 0XF84.0
#BIT ISDADRS4 = 0XF80.5
#BIT ISDADRS5 = 0XF80.4
#BIT ISDADRS6 = 0XF80.3
#BIT ISDADRS7 = 0XF80.2
#BIT ISDADRS8 = 0XF80.1
#BIT ISDADRS9 = 0XF80.0
// ISD25120 DIRECT ADDRESS MACRO FUNCTION. //
#define ISDADRS(x) \
ISDADRS0 = x & 1; \
ISDADRS1 = (x >> 1) & 1; \
ISDADRS2 = (x >> 2) & 1; \
ISDADRS3 = (x >> 3) & 1; \
ISDADRS4 = (x >> 4) & 1; \
ISDADRS5 = (x >> 5) & 1; \
ISDADRS6 = (x >> 6) & 1; \
ISDADRS7 = (x >> 7) & 1; \
ISDADRS8 = (x >> & 1; \
ISDADRS9 = (x >> 9) & 1

[metal]

Hi isis

I understand this part and know it already:

// ISD25120 TO PIC18F452 ADDRESS PINS. //
#BIT ISDADRS0 = 0XF82.0 // here is the address of pin_c0
#BIT ISDADRS1 = 0XF84.2 // here is the address of pin_e3
#BIT ISDADRS2 = 0XF84.1
#BIT ISDADRS3 = 0XF84.0
#BIT ISDADRS4 = 0XF80.5
#BIT ISDADRS5 = 0XF80.4
#BIT ISDADRS6 = 0XF80.3
#BIT ISDADRS7 = 0XF80.2
#BIT ISDADRS8 = 0XF80.1
#BIT ISDADRS9 = 0XF80.0

But how to use this in order to assign a pin to a bit in a variable, thats what I meant:

// ISD25120 DIRECT ADDRESS MACRO FUNCTION. //
#define ISDADRS(x) \
ISDADRS0 = x & 1; \
ISDADRS1 = (x >> 1) & 1; \
ISDADRS2 = (x >> 2) & 1; \
ISDADRS3 = (x >> 3) & 1; \
ISDADRS4 = (x >> 4) & 1; \
ISDADRS5 = (x >> 5) & 1; \
ISDADRS6 = (x >> 6) & 1; \
ISDADRS7 = (x >> 7) & 1; \
ISDADRS8 = (x >> & 1; \
ISDADRS9 = (x >> 9) & 1

[lsis]

We can't do that.
For this reason we make the macro and now the x is variable.

void main()
{

int16 x = 0;

SET_TRIS_A(0B11000000);
SET_TRIS_B(0B11111111);
SET_TRIS_C(0B10101110);
SET_TRIS_D(0B11100111);
SET_TRIS_E(0B11111000);

   DO {
   ISDADRS(x);
   x=x+1;
   delay_ms(10);
      }
      WHILE (x<1024);
 
}

I don't know how can we do that you are ask for now.
I am new in ccs.

[metal]

Hi isis

me too  

thanx

[Faros]

Hi metal



Those posts were just superb  â€¦:D  .....   well play man ....  

[metal]

Faros,

Really, aint a play, I am new to CCS, I see that these things are easily done with basic language VAR.3 = PORTA.0 , I don't know why C tries to complicate such things !! What do you think faros...

[Faros]

I believe you are write… the time/benefit ratio writing codes in C is very high … to high for the number of boards to be produced for limited projects …. I guess it has been used by people who were already familiar with C before switching to microcontroller code writing … I can write in assembly but it dose not bay off for the time wasted in debugging and optimizing …. I use your version of proton+ … it is by far undersized in generated codes than Mikrobasic … more featured …and more stable   …. By the way thank you for Mikrobasic crack … only now it works fine for sources over the 2 pages

[pama]

Hi,
 
thanks for your good work, I started to learn CCS and after several month spend on assembly, it's more easily to write code in CCS. CCS has a very-very good forum on their web pages (not just in CCs quetions), with helpfull members. But  i don't know anything about microbasic.
have a good day
pama

[Faros]

Hi  pama …

Nothing wrong about using C … if you can write in C the fastest, then it is better than any basic .

as a rule ....…" The best code writing tool is the one that you master the most " …anyhow  in IT world C is much better than basic for many rezones … one of them is that it has optimized generated codes …  you C what i mean?

[pama]

Hi Faros,
 
yes, i agree with you.That was the reason why i started pic-ing with C. But to be able to run a code, also have to be done the hardware, which is a little difficult for me
pama

[metal]

Hi

I think its the mistake of basic compiler writers in deed, I can see that people who wrote PICBasic Pro used C, but most compilers in basic didn't pay attention to code optimizing issues, I see that proton did, but its still young and needs alot of work to do with it.

Another thing I noticed is that coding in C looks more neaty and tidy than basic for PIC, but as long as I mastered basic for PIC in most basic compilers, I can say that its easier for me. I also managed to make my basic codes more neaty than those found in C.

The past experience in C for an engineer is not that big important, I did a lot of C in deed, when looking to PICs C, one has to read and read, as did with C for microsoft, as the two of them may have the same syntax, but they are for different platforms. what makes C more neat is the use of organised functions, I can say that mikrobasic did right when implemented procedures and functions.

last word to say is this, the best compiler is that the one you most master, there is no specific compiler that serves all projects on mind, so we better know what each project needs, and decide what compiler to use which best suites our project needs.

C U

[lsis]

Hi FAROS.
Before talk so easy for everything simply think that exists also other side in the same currency.

L.S.

[picstudent]

humm i think i 'll try CSS ....