public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Roman Kolesnikov <romank@randrlabs.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] lowlevel init and reboot issue SOLVED
Date: Sun, 09 Jul 2006 11:30:26 -0700	[thread overview]
Message-ID: <44B14B42.6050001@randrlabs.com> (raw)

Hello I have solved my problem, and I am passing some experience to the 
group.

I have had trouble resetting the system through the Watchdog timer. My 
system was at91rm9200EK type board. The problem was caused by linux 
leaving the flash memory in an "unknown" and not ready state. Once the 
watchdog reset would occur, the system would not recover and hang. 
Because my parallel flash chip was different from the DK board flash 
chip, linux MTD support would cause the flash to go and not quit some 
operation. Also DK boards came with an outside reset pin, and the EK 
boards come with an outside pushbutton reset; watchdog would not be able 
to reset all the hardware on the ek board, it would only reset the 
processor (I think).

My solution was to disable the MTD Flash driver. Since I did not use the 
parallel flash from Linux, it was ok for me to do so. I have not made a 
new flash driver for linux. This change solved the problem.

Flash that DK and EK boards use are mature and will likely be replaced 
by new product. I noticed that newer Atmel flash comes with two to three 
cycle commands, instead of upto 5 cycle commands. We used newer flash, 
and that is why the Linux MTD support was working improperly.

Thanks for looking,
Roman

                 reply	other threads:[~2006-07-09 18:30 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=44B14B42.6050001@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