From: Juergen Beisert <jbe@pengutronix.de>
To: Andre Schwarz <andre.schwarz@matrix-vision.de>
Cc: linuxppc-dev@ozlabs.org, u-boot@lists.denx.de
Subject: Re: MPC5200B: Trouble with config pins
Date: Fri, 21 Nov 2008 17:38:09 +0100 [thread overview]
Message-ID: <200811211738.11049.jbe@pengutronix.de> (raw)
In-Reply-To: <4926DA98.4060401@matrix-vision.de>
Hi Andre,
On Freitag, 21. November 2008, Andre Schwarz wrote:
> Have a look at the manual chapter 4 (=3DReset + Config).
> SRESET (issued by gpt0 - watchdog) isn't supposed to do a full hardware
> reset.
> Looks like you should make use of the SRESET and trigger HRESET
> accordingly.
>
> I could solve this with _not_ using the internal watchdog but an
> external one (TPS3828),
> i.e. watchdog timeouts and reboots are always issued by PORESET.
We are using an external watchdog now. But same behaviour. It hurts less,=20
because we increase the length of the active reset signal to add more time =
to=20
let the pin "find" its low level. But I'm not really happy about this=20
solution...
Regards,
Juergen
=2D-=20
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
=A0Pengutronix - Linux Solutions for Science and Industry
=A0 Handelsregister: Amtsgericht Hildesheim, HRA 2686
=A0 =A0 =A0 Vertretung Sued/Muenchen, Germany
Phone: +49-8766-939 228 | Fax: +49-5121-206917-9
WARNING: multiple messages have this Message-ID (diff)
From: Juergen Beisert <jbe@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC5200B: Trouble with config pins
Date: Fri, 21 Nov 2008 17:38:09 +0100 [thread overview]
Message-ID: <200811211738.11049.jbe@pengutronix.de> (raw)
In-Reply-To: <4926DA98.4060401@matrix-vision.de>
Hi Andre,
On Freitag, 21. November 2008, Andre Schwarz wrote:
> Have a look at the manual chapter 4 (=Reset + Config).
> SRESET (issued by gpt0 - watchdog) isn't supposed to do a full hardware
> reset.
> Looks like you should make use of the SRESET and trigger HRESET
> accordingly.
>
> I could solve this with _not_ using the internal watchdog but an
> external one (TPS3828),
> i.e. watchdog timeouts and reboots are always issued by PORESET.
We are using an external watchdog now. But same behaviour. It hurts less,
because we increase the length of the active reset signal to add more time to
let the pin "find" its low level. But I'm not really happy about this
solution...
Regards,
Juergen
--
Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
?Pengutronix - Linux Solutions for Science and Industry
? Handelsregister: Amtsgericht Hildesheim, HRA 2686
? ? ? Vertretung Sued/Muenchen, Germany
Phone: +49-8766-939 228 | Fax: +49-5121-206917-9
next prev parent reply other threads:[~2008-11-21 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 12:36 MPC5200B: Trouble with config pins Juergen Beisert
2008-11-21 12:36 ` [U-Boot] " Juergen Beisert
2008-11-21 15:09 ` Grant Likely
2008-11-21 15:09 ` Grant Likely
2008-11-21 15:26 ` Juergen Beisert
2008-11-21 15:26 ` Juergen Beisert
2008-11-26 15:11 ` Wolfram Sang
2008-11-26 15:11 ` Wolfram Sang
2008-11-21 15:58 ` Andre Schwarz
2008-11-21 15:58 ` [U-Boot] " Andre Schwarz
2008-11-21 16:38 ` Juergen Beisert [this message]
2008-11-21 16:38 ` Juergen Beisert
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=200811211738.11049.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=andre.schwarz@matrix-vision.de \
--cc=linuxppc-dev@ozlabs.org \
--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 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.