i could not communicate 18f2550 and 16f877 via i2c

[ugur]

Please help me,

I was communicated 2 877 each other in CCS. I tryed circuit in proteus. It's worked. And then I tryed communicate 18f2550 and 16f877 via i2c in CCS. 2550 is master. 877 is slave. But it's not worked.

SDA and SCL pins are true. is there an update in CCS or Proteus?

[lead_inovation]

Ugur! i can help u, but i would like u upload your source code!

[Parmin]

make sure of the following.
- the clock and data line "high" pulses are in fact high on the receiving end.
- the tris of each pin are correct for the purpose.

Communication is simple but before you jump into large codes, try small one byte (or even a bit) transfer.
Small steps make it easier to debug.

Good luck

[snoopy]

Do you have pull up in SDA and SCL lines, if not try with 10k.

Snoopy

[hate]

I guess you mentioned '16f877' not '18f877'? If that's true there is a bug in '16f877' hardware which you have to implement an 'i2c_stop()' function in standart CCS i2c functions. Below is the edited functions I used for 'eeprom' read and writes with '16f877', modify these functions for your own needs and give them a try. I recomend using a real hardware for the tests as 'proteus' in not very reliable for this kind of tasks!

Code:

void write_ext_eeprom(long int address, BYTE data, int dev_adr)
{
   short int status;
   i2c_start();
   i2c_write(0xa0|((dev_adr&0x03)<<1));
   i2c_write(address>>8);
   i2c_write(address);
   i2c_write(data);
   i2c_stop();
   do {
      i2c_start();
      status=i2c_write(0xa0|((dev_adr&0x03)<<1));
      i2c_stop();
   } while(status==1);
}

BYTE read_ext_eeprom(long int address, int dev_adr) {
   BYTE data;
   i2c_start();
   i2c_write(0xa0|((dev_adr&0x03)<<1));
   i2c_write(address>>8);
   i2c_write(address);
   i2c_start();
   i2c_write(0xa1|((dev_adr&0x03)<<1));
   data=i2c_read(0);
   i2c_stop();
   return(data);
}

'dev_adr' is the device address which you set by connecting the appropriate eeprom pins to GND or VDD. You can get rid of that if you don't need it. The important part here is the 'i2c_stop()' function in the 'write_ext_eeprom' function in the 'do...while' loop. That's the part to fix the bug in '16f877' hardware!

Regards...

[ugur]

thanks all,

for master (2550); some of my codes;

   #use i2c(Master,Fast,sda=PIN_B0,scl=PIN_B1)

int8 Birim_Oku(int8 BirimID, int8 Komut)
{
int Deger_Donen, Deger_Birim_Adresi;
         Deger_Birim_Adresi = Birim_Tablosu[BirimID];
         i2c_start ();           
         i2c_write (Deger_Birim_Adresi);       //Köle adresi
         i2c_write (Komut);       //Komut  gönder
         i2c_stop();             
//         delay_us(50);
         i2c_start ();           
         i2c_write (Deger_Birim_Adresi + 1);       
         Deger_Donen = i2c_read();   
         i2c_stop ();           
return Deger_Donen;         
}



Posted on: August 15, 2008, 09:10:35 21:10 - Automerged
for slave (877) some of my codes

#INT_SSP
void ssp_interupt ()
{
   I2C_Durumu = i2c_isr_state();
   if(I2C_Durumu < 0x80)                 //efendi bilgi gönderiyor
   {
   if(I2C_Durumu == 0)
   {
   }
   if(I2C_Durumu == 1)                   //ilk bayt komut
   {
      Komut = i2c_read();
      Tampon_Gonder  = BK_KOMUT_YOK;
      switch(Komut)
      {
..........................
            break;
      default: break;
      }
   }
   if(I2C_Durumu == 2)                   //alınan ikinci byte
   {
      buffer[Adres] = i2c_read();
   }
   }
   if(I2C_Durumu == 0x80)                //efendi bilgi istiyor
   {     
      switch(Tampon_Gonder)
      {
.......................
            i2c_write (Donecek_Deger);
            break;
      default: break;
      }
   
   }
}


Posted on: August 15, 2008, 09:16:53 21:16 - Automerged
i used these codes for communicate 877 (master) with 877 (slave). And there isn't any problem. it is working with 877 to 877. but not worked 2550 (master) to 877 (slave).



Posted on: August 15, 2008, 09:20:57 21:20 - Automerged
i tryed with 3k...

i'm building aircraft cockpit...

[omeryld]

hi,
i think your code is right. sometimes proteus is working wrong with i2c.
try it in a breadboard. it must work.