[U-Boot] omap3 i2c issues

[Heiko Schocher <hs@denx.de>]

Hello Murali,

Murali K. Vemuri wrote:
> I am using a omap3 based board and U-Boot version 03.00.02.07.

There is no such a version in mainline ...

> when I do "i2c probe", this results in : 38  3C  3D  3F.
> 
> I found that Kernel TWL is dumping messages to 48  49  4A & 4B.
> 
> I tried the the same on the "reference board and the corresponding
> u-boot" supplied from Mistral , when I type "iprobe", I get the
> output: 48 49 4A 4B.

here on my omap3_beagle board:

U-Boot 2010.09-05496-gbafe743-dirty (Oct 14 2010 - 09:26:57)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Beagle Rev C1/C2/C3
Die ID #00b000030000000004013f8a1700900c
Hit any key to stop autoboot:  0
OMAP3 beagleboard.org # i2c probe
Valid chip addresses: 48 49 4A 4B
OMAP3 beagleboard.org #

So, I think, i2c driver should be ok.

> I further verified that on my board, if I do "i2c mw 0x3C 0 0x34 0x10"
> I am able to write into I2C and "i2c md 0x3C 0 0x10" I am able to read
> back . This however, works only on 0x3c. "mw" & "md" are working on
> 0x3c only. 38, 3d & 3f are returning error.
> 
> I could not understand what is missing here? How come my board U-boot
> is getting a chip id different?
> is there a setting that I can do? my Hardware engineer says the OMAP3
> connections are same between our board and evm board.

pinsetup, clock setup?

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany