public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC85xx UPM NAND
Date: Mon, 12 Oct 2009 09:24:50 +0200	[thread overview]
Message-ID: <4AD2D9C2.7030802@tqs.de> (raw)
In-Reply-To: <d970ff420910091537o13d87fdcsb2da764f9b2aa107@mail.gmail.com>

Hi Alemao,

Alemao schrieb:
> Hi all,
> 
> I have used UPM in a MPC83xx with LBC running at 64MHz.
> 
> Now I have a MPC85xx, with LBC at 41MHz.
> 
> It only works if I put a delay in drivers/mtd/nand/fsl_upm.c :
> nand_write_buf(), otherwise I lost one byte. But it takes toooo long
> writing, which makes their use impractical.
> 
> I saw in board/tqc/tqm85xx/nand.c that the driver use an UPM
> configuration for each frequency.
> 
> Can some one tell me what signals I have to change or just some hint
> about what could be causing this behavior?
> 
> Im using UPM waveform editor and u-boot-2009-03.

The UPM tables and ORx settings for TQM85xx are optimized for each
LBC frequency, the used NAND chips and the used PCB.

To get the right timing for *your* HW you probably need a timing
simulation before. Eventually, you have to connect a timing analyzer
and check the bus signals after.

If the timing is correct, check the right order of bus commands,
too. The issue with the e500 core is, that it may reorder machine
instructions. Perhaps you need to instert "mbar" instructions.

Sorry, I'm not a HW guy, so I can't tell you more. I didn't do the
simulation and analysis myself.

Kind regards,
Jens

  reply	other threads:[~2009-10-12  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 22:37 [U-Boot] MPC85xx UPM NAND Alemao
2009-10-12  7:24 ` Jens Gehrlein [this message]
2009-10-14 13:15   ` Alemao

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=4AD2D9C2.7030802@tqs.de \
    --to=sew_s@tqs.de \
    --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