public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Daniel Morris'" <danielm@eCosCentric.com>,
	"'Frank Pagliughi'" <fpagliughi@mindspring.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: AW: [ECOS] General NAND Flash support?
Date: Tue, 16 Dec 2014 14:53:00 -0000	[thread overview]
Message-ID: <006701d01940$087c2760$19747620$@itrgmbh.de> (raw)
In-Reply-To: <20141215221924.GA16860@chunk.ammanford.ecoscentric.com>

Hello All,

many thanks for all the answers!

So, as I understand, full NAND functionality is implemented inside YAFFS
only?
As I understand, beside user data YAFFS is writing additionally control
information to the Flash (like FAT)?

But, when we have only NAND on board, how we can boot from NAND?
ROM bootstrap loader from uController is expecting simple Binary image.

Thanks
Richard


Richard Rauch
email: rrauch@itrgmbh.de
 
_______________________________________________

ITR GmbH Informationstechnologie Rauch 

web:   	http://www.itrgmbh.de
email: 	info@itrgmbh.de
  
Büroaddresse:
Business Terminal West, 3. Stock
Muggenhofer Strasse 136
90429 Nürnberg
phone:	+49 (0) 911 / 32 609 86- 8

Sitz:
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
Geschaeftsfuehrer: Richard Rauch
Handelsregister: Nuernberg HR B 21676
USt-Id Nr. : DE228051873
_______________________________________________
 

> -----Ursprüngliche Nachricht-----
> Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] Im Auftrag von Daniel Morris
> Gesendet: Montag, 15. Dezember 2014 23:20
> An: Frank Pagliughi
> Cc: ecos-discuss@ecos.sourceware.org
> Betreff: Re: [ECOS] General NAND Flash support?
> 
> On Mon, Dec 15, 2014 at 01:38:14PM -0500, Frank Pagliughi wrote:
> > Last time I tried it, the code was too buggy to try to use in an
> > actual product. That was about 2 years ago.
> 
> Take a look here for instructions and source to the tested, documented and
> product grade NAND library and optional log-structured, wear-levelling,
bad
> block managing, error correcting and fast mounting NAND filesystem:
> 
> http://www.ecoscentric.com/devzone/yaffs.shtml
> 
> Both the NAND library epk and upstream YAFFS port have recently been
> updated and re-validated. There are also drivers contributed by Spansion
> available on ecos-patches.
> 
>  Daniel
> 
> 
> %<----------------------------------------------------------------------
>   Daniel Morris - Sales & Marketing Director
>   eCosCentric - The eCos and RedBoot experts
>   Tel: +44 1223 245 571 - info@eCosCentric.com
>   DDI: +44 1269 591 171 - danielm@eCosCentric.com
> 
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2014-12-16 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 14:52 Richard Rauch
2014-12-15 18:38 ` Frank Pagliughi
2014-12-15 22:19   ` Daniel Morris
2014-12-16 14:53     ` Richard Rauch [this message]
2014-12-16 20:11       ` AW: " Ross Younger

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='006701d01940$087c2760$19747620$@itrgmbh.de' \
    --to=rrauch@itrgmbh.de \
    --cc=danielm@eCosCentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=fpagliughi@mindspring.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).