From: Andrew Liu <shengping.liu@windriver.com>
To: linuxppc-embedded@ozlabs.org
Subject: The ds1337 chip on fsl_mp8313E RDB REVA 3 doesn't work properly
Date: Thu, 20 Sep 2007 17:09:15 +0800 [thread overview]
Message-ID: <46F238BB.4040007@windriver.com> (raw)
Hello All,
The same u-boot/kernel/rootfs on fsl_mp8313E RDB REVA 2, DS1337 RTC
chip can work,
but on sl_mp8313E RDB REVA 3, it doesn't work, its time don't change.
This RTC chip specific bad behavior on sl_mp8313E RDB REVA 3 as follows:
(1) On U-Boot (from Freescale), run command:
=> i2c md 0x68 0x0
0000: 32 33 10 04 20 89 08 84 00 20 53 00 42 16 18 80 23.. .... S.B...
after a while
=> i2c md 0x68 0x0
0000: 32 33 10 04 20 89 08 84 00 20 53 00 42 16 18 80 23.. .... S.B...
The first value(second value) is unchanged always, but on fsl_mp8313E
RDB REVA 2, it changes.
meanwhile, we can change this value through i2c nm 0x68 0xX on
fsl_mp8313E RDB REVA 3.
SO the core of this problem is the time always keeps same.
(2) during Linux kernel bootup, we can see:
oing write 0 bytes to 0x68 - 1 of 1 messages
i2c_adapter i2c-0: master_xfer[0] W, addr=0x68, len=1
i2c_adapter i2c-0: master_xfer[1] R, addr=0x68, len=8
Doing write 1 bytes to 0x68 - 1 of 2 messages
Doing read 8 bytes to 0x68 - 2 of 2 messages
i2c_adapter i2c-0: client [ds1307] registered with bus id 0-0068
ds1307 0-0068: rtc intf: sysfs
ds1307 0-0068: rtc intf: proc
ds1307 0-0068: rtc intf: dev (254:0)
ds1307 0-0068: rtc core: registered ds1307 as rtc0
i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x68
i2c_adapter i2c-1: master_xfer[0] W, addr=0x68, len=0
Doing write 0 bytes to 0x68 - 1 of 1 messages
I2C: No RXAK
..............................
i2c_adapter i2c-0: master_xfer[0] W, addr=0x68, len=1
i2c_adapter i2c-0: master_xfer[1] R, addr=0x68, len=7
Doing write 1 bytes to 0x68 - 1 of 2 messages
Doing read 7 bytes to 0x68 - 2 of 2 messages
ds1307 0-0068: read: 32 33 10 04 20 89 08
ds1307 0-0068: read secs=32, mins=33, hours=10, mday=20, mon=8,
year=108, wday=3
ds1307 0-0068: setting the system clock to 2008-09-20 10:33:32 (1221906812)
it indicates can read and write RTC chip through I2C. but after system
boot up, we can see the time always same.
After adjusting these configurations on U-Boot environment according
to fsl_mp8313E RDB REVA 2, it still doesn't work.
Who can give me some advice or suggestion ? currently I doubt this
hardware, but what a shame I have only one fsl_mp8313E RDB REVA 3 board,
can't do comparison experiment.
Thanks in advance.
Andrew Liu
next reply other threads:[~2007-09-20 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 9:09 Andrew Liu [this message]
2007-09-20 17:19 ` The ds1337 chip on fsl_mp8313E RDB REVA 3 doesn't work properly Kim Phillips
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=46F238BB.4040007@windriver.com \
--to=shengping.liu@windriver.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.