From: Scott Wood <scottwood@freescale.com>
To: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Cannot wake-up from standby with MPC8313
Date: Fri, 20 Jan 2012 14:05:12 -0600 [thread overview]
Message-ID: <4F19C8F8.1090801@freescale.com> (raw)
In-Reply-To: <4F169BE3.30102@aimvalley.nl>
On 01/18/2012 04:16 AM, Norbert van Bolhuis wrote:
> Yes this is it!
> You mentioned mpc8313erdb bug before, I guess you had to mention it
> twice before
> I looked at mpc8313erdb bug description.
>=20
> The mpc8313erdb bug is described as follows:
>=20
> 3.5 Power management control (PMC) registers cannot be
> accessed?
> The PMC registers range from IMMR + 0x0B00 to IMMR + 0x0BFF. When this
> area is accessed in u-boot,
> the RDB hangs up. It appears that the PMC block is related to the JTAG
> interface; TRST must not be pulled
> down for normal operation of the PMC block. Possible workarounds are as
> follows:
> =95 Attach a debugger to drive TRST high during normal operation.
> =95 Remove the pull-down resistor (R37) for TRST. Although this tested =
on
> some RDBs without any
> problem, it violates the hardware specification. If it does not work on
> your RDB, use another workaround.
>=20
>=20
> I guess this is an MPC8313 problem rather than an MPC8313E-RDB problem =
?
> and I would expect it to be mentioned in MPC8313E Errata (which isn't t=
he
> case).
It is mentioned in the MPC8313E manual (4.2.2 step #10) that TRST must
not be asserted except when PORESET is asserted. The mpc8313erdb bug
was that the board was not complying with this.
-Scott
next prev parent reply other threads:[~2012-01-20 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 16:19 Cannot wake-up from standby with MPC8313 Norbert van Bolhuis
2012-01-04 21:08 ` Scott Wood
2012-01-05 15:58 ` Norbert van Bolhuis
2012-01-05 18:22 ` Scott Wood
2012-01-06 13:53 ` Norbert van Bolhuis
2012-01-06 21:03 ` Scott Wood
2012-01-13 14:13 ` Norbert van Bolhuis
2012-01-16 20:22 ` Scott Wood
2012-01-17 16:56 ` Norbert van Bolhuis
2012-01-17 22:09 ` Scott Wood
2012-01-18 10:16 ` Norbert van Bolhuis
2012-01-20 20:05 ` Scott Wood [this message]
2012-01-23 10:08 ` ehodys
-- strict thread matches above, loose matches on Subject: below --
2012-01-23 9:34 nvbolhuis
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=4F19C8F8.1090801@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nvbolhuis@aimvalley.nl \
/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.