AnsweredAssumed Answered

imx53  i2c-1  busy ,

Question asked by 潘 紫东 on Jun 16, 2013
Latest reply on Jan 21, 2015 by vipermania

hello everyone,i have a problem in i2c1 in  imx53.

when i operation i2c bus , i2sr_ibb   alway   is detect   ibb=1;   i do not why ?

i don't know this is a  software problem or hardware problem ?   i need help.

root@freescale ~$ hwclock -w
rtc-pcf8563 1-0051: pcf8563_set_datetime: secs=13, mins=11, hours=11, mday=1, mon=0, year=70, wday=4
i2c i2c-1: master_xfer[0] W, addr=0x51, len=2
i2c i2c-1: <i2c_imx_xfer>
i2c i2c-1: <i2c_imx_start>
i2c i2c-1: <i2c_imx_bus_busy>
i2c i2c-1: <i2c_imx_bus_busy> I2C bus is busy
i2c i2c-1: <i2c_imx_stop>
i2c i2c-1: <i2c_imx_bus_busy>
i2c i2c-1: <i2c_imx_xfer> exit with: error: -110
rtc-pcf8563 1-0051: pcf8563_set_datetime: err=-110 addr=02, data=13
hwclock: RTC_SET_TIME: Input/output error

 

i2c devices addr is  right,and    i use eim_d16  and  eim_eb2     as i2c-1   pin

 

MX53_PAD_EIM_D16__I2C2_SDA,

#define MX53_PAD_EIM_D16__I2C2_SDA              (_MX53_PAD_EIM_D16__I2C2_SDA | MUX_PAD_CTRL(MX53_I2C_PAD_CTRL_1))

 


#define _MX53_PAD_EIM_D16__I2C2_SDA                     IOMUX_PAD(0x460, 0x118, 5, 0x820, 1, 0)

 

 

  MX53_PAD_EIM_EB2__I2C2_SCL,

 


#define MX53_PAD_EIM_EB2__I2C2_SCL              (_MX53_PAD_EIM_EB2__I2C2_SCL | MUX_PAD_CTRL(MX53_I2C_PAD_CTRL_1))

 


#define _MX53_PAD_EIM_EB2__I2C2_SCL                     IOMUX_PAD(0x45C, 0x114, 5 | IOMUX_CONFIG_SION, 0x81C, 1, 0)

Outcomes