topic Re: P. Expert I2C Bean problem. in CodeWarrior for MCU

P. Expert I2C Bean problem.

ecotecsa — Thu, 29 Apr 2010 04:00:02 GMT

Hello everybody,

JM60 I2C module connected to TMP100 I2C Temperature sensor.

Problem is that process EI2C1_RecvBlock(data,2,Rcv); disable my Port A when is excecuted.

All other comunication process with TMP100 temperature sensor work perfectly.

Part of code:

int Read_Temp (){

   int Tph,Tpl;
   error=EI2C1_SelectSlave(0x48);
   Pointer=0x00;
   error=EI2C1_SendChar(Pointer);
   error=EI2C1_RecvBlock(data,2,Rcv);     // Here disable Port A (in *Rcv0=

Temph=*data;
   Templ=*(data+1);
   Tph=(int)Temph;
   Tpl=(int)Templ;
   Tph <<= 4;
   Tpl >>= 4;
   Temp=Tph|Tpl;

   PTADD=0x18;                              //Enable PTAD because
   PTAD=0x18;                               // RecvBlock disable  this
   return (Temp);
}

Thank you very much for suggestions.

Best Regards

Eduardo.

Re: P. Expert I2C Bean problem.

CompilerGuru — Thu, 29 Apr 2010 10:00:06 GMT

What is data? Is it a NULL pointer?

The reason I ask is that PTAD/PTADD happen to be at address 0/1, so could it be that you are using the port registers as data buffer?

Re: P. Expert I2C Bean problem.

ecotecsa — Tue, 04 May 2010 00:23:18 GMT

Hi Compilerguru,

I was defined:

byte Datos[128];

and

data=&Datos[0]; // in main

Then

int leo_Temp { ...}

Thank you

Eduardo

Re: P. Expert I2C Bean problem.

DesignFeats — Tue, 31 Jul 2012 18:19:36 GMT

HI, I have attached a simple ...(or so I thought) I2C read of a temp semsor I have had no luck getting it going. 12Mhz Xtal 51Jm64 Coldfire v1 P Expert Bean I2C framework. Wont send byte after setting slave address? Any ideas? David

Re: P. Expert I2C Bean problem.

DesignFeats — Mon, 06 Aug 2012 10:45:39 GMT

http://www.freescale.com/infocenter/index.jsp?topic=%2Fcom.freescale.doc.mcu.processorexpert.components%2Fhtml%2FBeans%2FInternalI2C%2FInternalI2CTypical+Usage.html This is worth a read...

Re: P. Expert I2C Bean problem.

DesignFeats — Mon, 06 Aug 2012 11:37:49 GMT

Found error.. Microchip MCP9805 pinout is different to MCP9808, used MCP9805 for MCP9808 as it is missing in Microchip Altium Library Mistake - Altium Microchip Library has MCP9805 but not MCP9808, assumed that as chip is made in same package, same family and has same interface and pin labels...Missed pin swap on SCL/SDA as Altium Schematic in Microchip library has pins jumbled in logical fashion rather than physical position Arrgh..