For users of the Atmel AT91SAM7 and AT91SAM9 ARM CPU chips. Atmel has taken a new direction by combining on chip flash and ram with the ARM CPU on a single die. This provides low cost devices for small systems using the ARM CPU.
This group is to exchange information to help users get started and learn how to use the devices.
I've got a script to load my Linux compilation on to an AT91SAM9261-EK.
It works just fine on several different devices.
We've also had a few where, despite the script running just fine, no
errors from SAM-BA, Linux won't load the JFFS2 root filesystem.
We don't have a sample size large enough to be statistically
significant, but that we've run into this with several devices bothers
us a lot.
Has anyone else had problems with loading a Linux filesystem image into
NAND Flash, is this something where we find a way to test it during
initial device programming and make it Samsung's problem, or is this
maybe an issue with the Linux driver for the NAND Flash that no amount
of hardware fixing will help?
Thanks for any insight!
Dan
------------------------------------

(You need to be a member of AT91SAM -- send a blank email to AT91SAM-subscribe@yahoogroups.com )
Hi,
Go to Atmel site an download AT91SAM9261's latest example code u will get the NAND Flash
test code.Just dump that and it will give u information related to Bad Sectors etc.
With Regards,
MANU
--- On Wed, 4/3/09, Dan Lyke
wrote:
From: Dan Lyke
Subject: [AT91SAM] Lots of AT91SAM9261-EKs with bad NAND flash?
To: A...@yahoogroups.com
Date: Wednesday, 4 March, 2009, 2:16 AM
I've got a script to load my Linux compilation on to an AT91SAM9261- EK.
It works just fine on several different devices.
We've also had a few where, despite the script running just fine, no
errors from SAM-BA, Linux won't load the JFFS2 root filesystem.
We don't have a sample size large enough to be statistically
significant, but that we've run into this with several devices bothers
us a lot.
Has anyone else had problems with loading a Linux filesystem image into
NAND Flash, is this something where we find a way to test it during
initial device programming and make it Samsung's problem, or is this
maybe an issue with the Linux driver for the NAND Flash that no amount
of hardware fixing will help?
Thanks for any insight!
Dan
Add more friends to your messenger and enjoy! Go to
http://messenger.yahoo.com/invite/

(You need to be a member of AT91SAM -- send a blank email to AT91SAM-subscribe@yahoogroups.com )