public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dharmosoth Seetharam <seetharam_21@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem in writing downloaded image to NAND device
Date: Wed, 28 Nov 2007 10:45:12 +0000 (GMT)	[thread overview]
Message-ID: <794354.44331.qm@web94811.mail.in2.yahoo.com> (raw)
In-Reply-To: <20071127220850.2174A24075@gemini.denx.de>

Hi,

Thank you for quick suggestion.

I have one doubt in NAND write/read PATH. 

> >  nand_write() --> nand_write_ecc() -->
> >  nand_write_page() --> nand_write_buf() -->
> >  
> >
> >  in nand_write_buf() :
> >
> >  for (i=0; i<len; i++) {
> >       writeb(buf[i], this->IO_ADDR_W);
> >
> > << writeb is defined as
> >    (*(volatile unsigned char *)(a) = (v)) >>


How can be "n" (where n=len) characters are 
going to written this->IO_ADDR_W.


As per the above fro loop, I am getting confuse
that is - for each character from buf ( ie. buf[i])
the dest. address will be the same. So, there will be
a overwriting to the same dest. address in NAND.

Is there any logic behind this stmt ?? 


Please suggest me the right way to understand the 
NAND write PATH from U-Boot code.


Thanks,
Seetharam

--- Wolfgang Denk <wd@denx.de> wrote:

> In message
> <914704.38072.qm@web94807.mail.in2.yahoo.com> you
> wrote:
> > 
> > I have downloaded the file
> u-boot-1.3.0-rc1.tar.bz2
> > from the following link.
> > ftp://ftp.denx.de/pub/u-boot/
> 
> Why didn't you use one of the more recent versions
> like 
> 
> > But, U_BOOT_VERSION is having 1.2.0 only.
> 
> Oops? Make sure to unpack, configure and build the
> downloaded tarball,
> please.
> 
> > Is it wrong ?? OR any other U-boot 1.3 is there ?
> > Please point me if i am wrong.
> 
> A short look at the FTP server shows:
> 
> -rw-rw-r--      6866983   Sep  8 01:09  
> u-boot-1.3.0-rc1.tar.bz2
> -rw-r--r--      6876009   Sep 20 00:07  
> u-boot-1.3.0-rc2.tar.bz2
> -rw-rw-r--      8783437   Oct 14 00:13  
> u-boot-1.3.0-rc3.tar.gz
> -rw-rw-r--      6896029   Nov 19 22:25  
> u-boot-1.3.0-rc4.tar.bz2
> -rw-rw-r--      6898443   Nov 19 22:26  
> u-boot-1.3.0.tar.bz2
> 
> So indeed it seems there are never versions
> available.
> 
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 
> -- 
> DENX Software Engineering GmbH,     MD: Wolfgang
> Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194
> Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80
> Email: wd at denx.de
> "There are things that are so serious that you can 
> only  joke  about
> them"                                               
>     - Heisenberg
> 



      Why delete messages? Unlimited storage is just a click away. Go to http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html

  reply	other threads:[~2007-11-28 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27  9:04 [U-Boot-Users] Problem in writing downloaded image to NAND device Dharmosoth Seetharam
2007-11-27  9:23 ` Stefan Roese
2007-11-27 15:40   ` Dharmosoth Seetharam
2007-11-27 18:31     ` Stefan Roese
2007-11-27 22:08     ` Wolfgang Denk
2007-11-28 10:45       ` Dharmosoth Seetharam [this message]
2007-11-28 11:00         ` Stefan Roese
2007-11-29 11:04           ` Dharmosoth Seetharam
2007-11-29 11:21             ` Stefan Roese

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=794354.44331.qm@web94811.mail.in2.yahoo.com \
    --to=seetharam_21@yahoo.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