From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] PPC4XX Custom Board - Failing to read I2C
Date: Tue, 09 Apr 2013 17:49:07 +0200 [thread overview]
Message-ID: <51643873.4000801@denx.de> (raw)
In-Reply-To: <1365450848269-151862.post@n7.nabble.com>
Greg,
On 08.04.2013 21:54, txcotrader wrote:
> Yes, I am working with a 460SX and a board based off of AMCC Eiger
> (unsupported as of 2010).
460SX is quite untested these days I'm afraid. I don't have such a board
here as well.
> IICx_STS Register settings:
> 04 = MDBF Full = Master data buffer contains data
> 40 = IRQA Active = An IIC interrrupt has been sent to the UIC
>
> I'm clearing the IIC register early on in my code:
> mtdcr(UIC0SR, 0xffffffff); /* clear all */
> mtdcr(UIC0ER, 0x00000000); /* disable all */
> mtdcr(UIC0CR, 0x00000005); /* ATI & UIC1 crit are critical */
> mtdcr(UIC0PR, 0xffffffff); /* per ref-board manual */
> mtdcr(UIC0TR, 0x00000000); /* per ref-board manual */
> mtdcr(UIC0VR, 0x00000000); /* int31 highest, base=0x000 */
> mtdcr(UIC0SR, 0xffffffff); /* clear all */
>
> mtdcr(UIC1SR, 0xffffffff); /* clear all */
> mtdcr(UIC1ER, 0x00000000); /* disable all */
> mtdcr(UIC1CR, 0x00000000); /* all non-critical */
> mtdcr(UIC1PR, 0xffffffff); /* per ref-board manual */
> mtdcr(UIC1TR, 0x00000000); /* per ref-board manual */
> mtdcr(UIC1VR, 0x00000000); /* int31 highest, base=0x000 */
> mtdcr(UIC1SR, 0xffffffff); /* clear all */
Ughh! This is not IIC (I2C) but UIC released code. So its for the
interrupt controller and not I2C controller. But nevertheless this
should not matter.
> I'm really not sure what to look for at this point, any additional tips you
> might have would be extremely helpful. I truly appreciate your help to this
> point.
As mentioned above I don't have such a board here, so I can't really
test anything. Sorry.
Best regards,
Stefan
next prev parent reply other threads:[~2013-04-09 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:48 [U-Boot] PPC4XX Custom Board - Failing to read I2C txcotrader
2013-04-03 0:51 ` Stefan Roese
2013-04-03 16:15 ` txcotrader
2013-04-03 17:08 ` Stefan Roese
2013-04-03 17:29 ` txcotrader
2013-04-03 17:54 ` Anatolij Gustschin
2013-04-03 19:09 ` txcotrader
2013-04-04 17:43 ` txcotrader
2013-04-04 22:18 ` Rommel Custodio
2013-04-04 22:26 ` txcotrader
2013-04-05 0:04 ` txcotrader
2013-04-05 6:04 ` Stefan Roese
2013-04-08 12:26 ` txcotrader
2013-04-08 13:33 ` Stefan Roese
2013-04-08 14:16 ` txcotrader
2013-04-08 14:34 ` Stefan Roese
2013-04-08 19:54 ` txcotrader
2013-04-09 15:49 ` Stefan Roese [this message]
2013-07-24 22:58 ` txcotrader
2013-07-25 4:33 ` Stefan Roese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51643873.4000801@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox