From: Roman Kolesnikov <romank@randrlabs.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] lowlevel init and reboot issue
Date: Thu, 06 Jul 2006 17:59:56 -0700 [thread overview]
Message-ID: <44ADB20C.7080601@randrlabs.com> (raw)
Hello,
I am running a board similar to the at91rm9200ek board. It has been
stripped down of few peripherials for minimal power consumption purpose.
I am running uboot 1.1.4 and linux 2.6.16. U boot loads directly from
parallel flash into ram.
My problem is that I cannot restart the chip from linux. I followed the
watchdog code, and it does execute. Linux also closes up fine. However,
the processor does not reset at the end. The weird thing is that a reset
works fine from uboot. The code is almost identical between the uboot
reset and the linux system call. Both set the reset pin and make a
watchdog overflow.
I believe that my issue lies in a uboot setting somewhere in the initial
linux setup. If I load ubott 1.1.4 without low level init by means of
yet another loader loading uboot from flash to ram, the reset runs but
very slow. However, my uboot utilizes the lowlevel init. Somehow it
affects my watchdog timer and stops me from resetting the chip.
Has anyone run into this issue? What could be stopping me from resetting?
I thought that the watchdog timer was a purely hardware tool. I thought
that setting and overflowing the timer would reset the chip on a
hardware level. Please help. I have spent a week or so on this and
cannot figure out the issue. It is probably very simple and is my
oversight, however, I cannot see it yet.
Thanks again,
Roman
reply other threads:[~2006-07-07 0:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44ADB20C.7080601@randrlabs.com \
--to=romank@randrlabs.com \
--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