From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Thu, 25 Jul 2013 06:33:32 +0200
Subject: [U-Boot] PPC4XX Custom Board - Failing to read I2C
In-Reply-To: <1374706696995-159975.post@n7.nabble.com>
References: <1364939304023-151298.post@n7.nabble.com>
	<1365120299377-151609.post@n7.nabble.com>
	<515E6986.4050905@denx.de>
	<1365430593610-151814.post@n7.nabble.com>
	<5162D574.30702@gmail.com>
	<1365450848269-151862.post@n7.nabble.com>
	<51643873.4000801@denx.de>
	<1374706696995-159975.post@n7.nabble.com>
Message-ID: <51F0AA9C.3000902@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Greg,

On 07/25/2013 12:58 AM, txcotrader wrote:
> I know it's been awhile, but I do appreciate your previous help. I took some
> time off to complete other projects, now I'm back working on finishing this
> port. During the boot I'm seeing the value of &i2c->extsts is either 0x40 or
> 0x60 which equates to lost arbitration or lost arbitration and incomplete
> transfer. Have you seen this type of error based on a misconfiguration? Any
> help you're willing to provide is greatly appreciated. 

Sorry, I have no idea why this could be the case. Do you have another
4xx based board (some AMCC/APM eval board) to compare the "extsts"
register value? This might give you a clue.

Thanks,
Stefan