[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Victor Librado]

Hello all,
I'm working with u-boot for booting in nandflash with the evaluation 
board atmel at91sam9260ek. Nandflash reads ok, but performing and erase 
doesn`t work.

I get these messages trying to erase a block of the nand and writing the 
environment variables to nandflash.

Any help? I'm missing a configuration parameter in config or what may 
happens?


U-Boot> saveenv
Saving Environment to NAND...
Erasing redundant Nand...Timeout!U-Boot>
U-Boot>


U-Boot> nand erase 0x60000 0x20000

NAND erase: device 0 offset 0x60000, size 0x20000
Timeout!
SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5

OK

 

 

 

Victor Librado Sancho
Departamento I+D
------------------------------------------------------------------------

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Marco Cavallini]

Victor Librado ha scritto:
> 
> Hello all,
> I'm working with u-boot for booting in nandflash with the evaluation 
> board atmel at91sam9260ek. Nandflash reads ok, but performing and erase 
> doesn`t work.
> 
> I get these messages trying to erase a block of the nand and writing the 
> environment variables to nandflash.
> 
> Any help? I'm missing a configuration parameter in config or what may 
> happens?
> 
> 
> U-Boot> saveenv
> Saving Environment to NAND...
> Erasing redundant Nand...Timeout!U-Boot>
> U-Boot>
> 
> 
> U-Boot> nand erase 0x60000 0x20000
> 
> NAND erase: device 0 offset 0x60000, size 0x20000
> Timeout!
> SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5
> 
> OK
> Victor Librado Sancho
> Departamento I+D

Victor,
you should check registers settings and timing into yourboard.h
configuration file

Ciao
-- 
Marco Cavallini
Koan s.a.s. - Bergamo - Italia
Embedded and Real-Time Software Engineering
http://www.KoanSoftware.com - http://www.KaeilOS.com

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Victor Librado]

I am using the same value for the SMC registers as stated in my linux 
kernel board-at91sam9260ek.c. In linux I can perform nandflash 
read/erase/write ok. (flash_eraseall / nandwrite commands).

May I have to define the JFFS2 partitions in u-boot configuration 
my_board.h as I have in Linux?

Commands: *CONFIG_JFFS2_NAND_OFF*, CONFIG_JFFS2_NAND_SIZE ...?

Regards,
V?ctor


Victor,
you should check registers settings and timing into yourboard.h
configuration file

Ciao

 


Victor Librado ha scritto:

> > 
> > Hello all,
> > I'm working with u-boot for booting in nandflash with the evaluation 
> > board atmel at91sam9260ek. Nandflash reads ok, but performing and erase 
> > doesn`t work.
> > 
> > I get these messages trying to erase a block of the nand and writing the 
> > environment variables to nandflash.
> > 
> > Any help? I'm missing a configuration parameter in config or what may 
> > happens?
> > 
> > 
> > U-Boot> saveenv
> > Saving Environment to NAND...
> > Erasing redundant Nand...Timeout!U-Boot>
> > U-Boot>
> > 
> > 
> > U-Boot> nand erase 0x60000 0x20000
> > 
> > NAND erase: device 0 offset 0x60000, size 0x20000
> > Timeout!
> > SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5
> > 
> > OK
>   



 

 

Victor Librado Sancho
Departamento I+D
------------------------------------------------------------------------

------------------------------------------------------------------------

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Stefan Roese]

On Wednesday 06 June 2007, Victor Librado wrote:
> I am using the same value for the SMC registers as stated in my linux
> kernel board-at91sam9260ek.c. In linux I can perform nandflash
> read/erase/write ok. (flash_eraseall / nandwrite commands).
>
> May I have to define the JFFS2 partitions in u-boot configuration
> my_board.h as I have in Linux?

No, this sounds like a driver problem. Do you use the old legancy NAND 
interface (CFG_NAND_LEGACY) with the old access macros (NAND_DISABLE_CE...), 
or do you use the new interface?

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Chris Sharman]

 

> -----Original Message-----
> From: u-boot-users-bounces at lists.sourceforge.net 
> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf 
> Of Victor Librado
> Sent: Thursday, 7 June 2007 2:34 AM
> To: u-boot-users at lists.sourceforge.net
> Subject: [U-Boot-Users] u-boot on nadflash for at91sam9260ek
> 
> 
> 
> Hello all,
> I'm working with u-boot for booting in nandflash with the 
> evaluation board atmel at91sam9260ek. Nandflash reads ok, but 
> performing and erase doesn`t work.
> 
> I get these messages trying to erase a block of the nand and 
> writing the environment variables to nandflash.
> 
> Any help? I'm missing a configuration parameter in config or 
> what may happens?
> 
> 
> U-Boot> saveenv
> Saving Environment to NAND...
> Erasing redundant Nand...Timeout!U-Boot>
> U-Boot>
> 
> 
> U-Boot> nand erase 0x60000 0x20000
> 
> NAND erase: device 0 offset 0x60000, size 0x20000
> Timeout!
> SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5
> 
> OK
> 
>  
> 
>  
> 
>  
> 
> Victor Librado Sancho
> Departamento I+D
> --------------------------------------------------------------
> ----------

Hi Victor,

I also have this exact same problem on my at91sam9260ek. Nand works fine
in linux but not in U-boot.

However when I use the patched u-boot from Atmel (based on an older
version of u-boot) nand works.

Maybe there are some clues in there somewhere.

Regards
Chris 

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Victor Librado]

Thanks all,

By now I use u-boot-1.1.5 version with atmel 1.3 patch. Definitions of 
timing access for nandflash in my board.h as in linux board initialization.

The configuration nand parameters as follows:

#define NAND_MAX_CHIPS                 1        /* Max number of NAND 
devices   */
#define CFG_MAX_NAND_DEVICE            1        /* Max number of NAND 
devices   */
#define SECTORSIZE                     512
#define CFG_NAND_BASE                  0x40000000
#define CONFIG_NEW_NAND_CODE

#define ADDR_COLUMN                    1
#define ADDR_PAGE                      2
#define ADDR_COLUMN_PAGE               3

#define NAND_ChipID_UNKNOWN            0
#define NAND_MAX_FLOORS                1
#undef  CFG_NAND_WP

#define CFG_NO_FLASH                    1

#undef  CFG_ENV_IS_IN_FLASH
#undef  CFG_ENV_IS_IN_DATAFLASH
#define CFG_ENV_IS_IN_NAND              1

/*#define CONFIG_MTD_DEBUG              1
#define CONFIG_MTD_DEBUG_VERBOSE        MTD_DEBUG_LEVEL3
*/
#ifdef CFG_ENV_IS_IN_NAND
#define CFG_ENV_OFFSET  0x60000         /* environment starts here  */
#define CFG_ENV_SIZE    0x20000         /* 1 sector = 128kB */
#endif

Now when I try to erase nand sector of environment variables or saveenv 
environment variables I get these messages:

U-Boot> nand erase 0x60000 0x20000

NAND erase: device 0 offset 0x60000, size 0x20000
Skipping bad block at  0x00060000

OK
U-Boot> saveenv
Saving Environment to NAND...
Erasing Nand...nand_erase: attempt to erase a bad block at page 0x000000c0
U-Boot>

I looked into source code and when saving environmet variables the erase 
functions exits if it finds a bad block, as in this case. environment 
variables are not saved.

Is it a problem of this sector of my nandflash that is kaputt (change my 
nandflash of my board?)? I read in nandflash datasheet that is normal 
the presence of bad blocks in a flash and that it should be created a 
table with the index of the bad blocks and skip them... U-boot can 
process in this way activiting some variables? (maybe i should use the 
old nand_legacy way ...?)

Or it must be configured u-boot in some way to skip bad block and 
continuing with the erasing and saving variables process ....

Or may be I am totally puzzled....

 

 

 

Victor Librado Sancho
Departamento I+D
------------------------------------------------------------------------


Chris Sharman escribi?:
>  
>
>   
>> -----Original Message-----
>> From: u-boot-users-bounces at lists.sourceforge.net 
>> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf 
>> Of Victor Librado
>> Sent: Thursday, 7 June 2007 2:34 AM
>> To: u-boot-users at lists.sourceforge.net
>> Subject: [U-Boot-Users] u-boot on nadflash for at91sam9260ek
>>
>>
>>
>> Hello all,
>> I'm working with u-boot for booting in nandflash with the 
>> evaluation board atmel at91sam9260ek. Nandflash reads ok, but 
>> performing and erase doesn`t work.
>>
>> I get these messages trying to erase a block of the nand and 
>> writing the environment variables to nandflash.
>>
>> Any help? I'm missing a configuration parameter in config or 
>> what may happens?
>>
>>
>> U-Boot> saveenv
>> Saving Environment to NAND...
>> Erasing redundant Nand...Timeout!U-Boot>
>> U-Boot>
>>
>>
>> U-Boot> nand erase 0x60000 0x20000
>>
>> NAND erase: device 0 offset 0x60000, size 0x20000
>> Timeout!
>> SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5
>>
>> OK
>>
>>  
>>
>>  
>>
>>  
>>
>> Victor Librado Sancho
>> Departamento I+D
>> --------------------------------------------------------------
>> ----------
>>     
>
> Hi Victor,
>
> I also have this exact same problem on my at91sam9260ek. Nand works fine
> in linux but not in U-boot.
>
> However when I use the patched u-boot from Atmel (based on an older
> version of u-boot) nand works.
>
> Maybe there are some clues in there somewhere.
>
> Regards
> Chris 
>
>
>
>   

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Michel Benoit]

Hi Victor

We have the same problem.  The u-boot 1.1.5 code from Atmel does not
correctly support the ECC correction coding in the OOB (out of bounds)
area of the nandflash when writing.  I have tried playing around with
the available settings to no avail.  When you do saveenv the data is
correctly written to nand flash but the oob area is filled with a 12
byte ECC code which makes the 5th byte in the OOB something other than
FF and thus marks the sector as bad.  The hw ECC controller of the
AT91SAM9260 is hard coded to generate a  4 byte ECC in the first 4
bytes of the OOB.  This is the ECC used by SAMBA (external pc
programming tool) and the linux at91-nand driver.  I have not found
any support for this in the Atmel u-boot code (yet).

If anyone has fixed AT91SAM9260 hw ECC support in u-boot please send
us a copy of your changes.  Even a sw ECC that generates a correct 4
byte code would be useful.

U-boot on at91sam9260 can however read from nand (i think it ignores
ECC by default) so its possible to boot an image that you have written
to nand, its just not possible to write to nand from within u-boot.  I
use either samba or linux (flash_eraseall and nandwrite) to write data
to the nandflash and fw_setenv and fw_printenv (compiled from u-boot
tools dir) to modify u-boot environment variables during development

Atmel has a port of u-boot 1.2 available on www.at91.com.  I have not
been successful it getting that version to run yet. Does anyone know
if it includes support for nandflash writes from u-boot?

Michel

> Thanks all,
>
> By now I use u-boot-1.1.5 version with atmel 1.3 patch. Definitions of
> timing access for nandflash in my board.h as in linux board initialization.
>
> The configuration nand parameters as follows:
>
> #define NAND_MAX_CHIPS                 1        /* Max number of NAND
> devices   */
> #define CFG_MAX_NAND_DEVICE            1        /* Max number of NAND
> devices   */
> #define SECTORSIZE                     512
> #define CFG_NAND_BASE                  0x40000000
> #define CONFIG_NEW_NAND_CODE
>
> #define ADDR_COLUMN                    1
> #define ADDR_PAGE                      2
> #define ADDR_COLUMN_PAGE               3
>
> #define NAND_ChipID_UNKNOWN            0
> #define NAND_MAX_FLOORS                1
> #undef  CFG_NAND_WP
>
> #define CFG_NO_FLASH                    1
>
> #undef  CFG_ENV_IS_IN_FLASH
> #undef  CFG_ENV_IS_IN_DATAFLASH
> #define CFG_ENV_IS_IN_NAND              1
>
> /*#define CONFIG_MTD_DEBUG              1
> #define CONFIG_MTD_DEBUG_VERBOSE        MTD_DEBUG_LEVEL3
> */
> #ifdef CFG_ENV_IS_IN_NAND
> #define CFG_ENV_OFFSET  0x60000         /* environment starts here  */
> #define CFG_ENV_SIZE    0x20000         /* 1 sector = 128kB */
> #endif
>
> Now when I try to erase nand sector of environment variables or saveenv
> environment variables I get these messages:
>
> U-Boot> nand erase 0x60000 0x20000
>
> NAND erase: device 0 offset 0x60000, size 0x20000
> Skipping bad block at  0x00060000
>
> OK
> U-Boot> saveenv
> Saving Environment to NAND...
> Erasing Nand...nand_erase: attempt to erase a bad block at page 0x000000c0
> U-Boot>
>
> I looked into source code and when saving environmet variables the erase
> functions exits if it finds a bad block, as in this case. environment
> variables are not saved.
>
> Is it a problem of this sector of my nandflash that is kaputt (change my
> nandflash of my board?)? I read in nandflash datasheet that is normal
> the presence of bad blocks in a flash and that it should be created a
> table with the index of the bad blocks and skip them... U-boot can
> process in this way activiting some variables? (maybe i should use the
> old nand_legacy way ...?)
>
> Or it must be configured u-boot in some way to skip bad block and
> continuing with the erasing and saving variables process ....
>
> Or may be I am totally puzzled....
>
>
>
>
>
>
>
> Victor Librado Sancho
> Departamento I+D
> ------------------------------------------------------------------------
>
>
> Chris Sharman escribi?:
> >
> >
> >
> >> -----Original Message-----
> >> From: u-boot-users-bounces at lists.sourceforge.net
> >> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf
> >> Of Victor Librado
> >> Sent: Thursday, 7 June 2007 2:34 AM
> >> To: u-boot-users at lists.sourceforge.net
> >> Subject: [U-Boot-Users] u-boot on nadflash for at91sam9260ek
> >>
> >>
> >>
> >> Hello all,
> >> I'm working with u-boot for booting in nandflash with the
> >> evaluation board atmel at91sam9260ek. Nandflash reads ok, but
> >> performing and erase doesn`t work.
> >>
> >> I get these messages trying to erase a block of the nand and
> >> writing the environment variables to nandflash.
> >>
> >> Any help? I'm missing a configuration parameter in config or
> >> what may happens?
> >>
> >>
> >> U-Boot> saveenv
> >> Saving Environment to NAND...
> >> Erasing redundant Nand...Timeout!U-Boot>
> >> U-Boot>
> >>
> >>
> >> U-Boot> nand erase 0x60000 0x20000
> >>
> >> NAND erase: device 0 offset 0x60000, size 0x20000
> >> Timeout!
> >> SAM NAND 256MiB 3,3V 8-bit: MTD Erase failure: -5
> >>
> >> OK
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Victor Librado Sancho
> >> Departamento I+D
> >> --------------------------------------------------------------
> >> ----------
> >>
> >
> > Hi Victor,
> >
> > I also have this exact same problem on my at91sam9260ek. Nand works fine
> > in linux but not in U-boot.
> >
> > However when I use the patched u-boot from Atmel (based on an older
> > version of u-boot) nand works.
> >
> > Maybe there are some clues in there somewhere.
> >
> > Regards
> > Chris
> >
> >
> >
> >
>
>
>
> ------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
>
> ------------------------------
>
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
>
> End of U-Boot-Users Digest, Vol 13, Issue 21
> ********************************************
>

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Victor Librado]

Hello Michel and all,

Thank you very much for your comments. By now I have the following on my 
at91sam9260ek work with nandflash:

1) In linux. Linux version 2.6.19 with maxim patches. Kernel 
configuration: at91-nand support but not CONFIG_MTD_NAND_ECC_SMC 
defined. So my Linux system is not performing ECC. In at91-nand.c is stated:

                    nand_chip->ecc.mode = NAND_ECC_SOFT;    /* enable ECC */

So the Linux version (when configured) I assume is not using the HW ECC 
at91sam9260 processor provides. It has a c file nand_ecc.c with an 
algorithm to do it by soft. This is provide in linux 2.6.21 at91 patches?
All in all, nandwrite and flash_eraseall commands work properly.

2)In u-boot. I redefined the block of the nandflash for environment 
variables :

#ifdef CFG_ENV_IS_IN_NAND
#define CFG_ENV_OFFSET  0x80000         /* environment starts here  */
#define CFG_ENV_SIZE    0x20000         /* 1 sector = 128kB */
 #endif


Now saveenv works properly! I think it was previously a bad block in my 
nandflash?

I have a doubt, if I define the soft ECC (both linux, u-boot), the OOB 
section of each page of the SAMSUNG nandflash the board has (64 bytes), 
how will it be filled? Because the nandflash datasheet states that in a 
block the first byte of the OOB section in the 1st o 2nd pages must be 
FFh or it is a bad block. So it could be that ECC data (the 4 byte hw or 
software ECC) were written in this first byte of the OOB and mark the 
block as invalid for this nandflash....... (so every write will generate 
a bad bloack?)

In u-boot the eccmode:

nand->eccmode = NAND_ECC_HW12_2048; /* NAND_ECC_SOFT;*/

What part of the OOB writes?

I'm getting really confused... any help will be welcomed.

Can ECC disabled in nandflash u-boot with some compilation option?

Best regards,

V?ctor.

/////////////////////////

Hi Victor

We have the same problem.  The u-boot 1.1.5 code from Atmel does not
correctly support the ECC correction coding in the OOB (out of bounds)
area of the nandflash when writing.  I have tried playing around with
the available settings to no avail.  When you do saveenv the data is
correctly written to nand flash but the oob area is filled with a 12
byte ECC code which makes the 5th byte in the OOB something other than
FF and thus marks the sector as bad.  The hw ECC controller of the
AT91SAM9260 is hard coded to generate a  4 byte ECC in the first 4
bytes of the OOB.  This is the ECC used by SAMBA (external pc
programming tool) and the linux at91-nand driver.  I have not found
any support for this in the Atmel u-boot code (yet).

If anyone has fixed AT91SAM9260 hw ECC support in u-boot please send
us a copy of your changes.  Even a sw ECC that generates a correct 4
byte code would be useful.

U-boot on at91sam9260 can however read from nand (i think it ignores
ECC by default) so its possible to boot an image that you have written
to nand, its just not possible to write to nand from within u-boot.  I
use either samba or linux (flash_eraseall and nandwrite) to write data
to the nandflash and fw_setenv and fw_printenv (compiled from u-boot
tools dir) to modify u-boot environment variables during development

Atmel has a port of u-boot 1.2 available on www.at91.com.  I have not
been successful it getting that version to run yet. Does anyone know
if it includes support for nandflash writes from u-boot?

Michel

 

 

 

Victor Librado Sancho
Departamento I+D
------------------------------------------------------------------------

[U-Boot-Users] u-boot on nadflash for at91sam9260ek

[Stefan Roese]

Hi Victor,

On Thursday 07 June 2007, Victor Librado wrote:
> 2)In u-boot. I redefined the block of the nandflash for environment
> variables :
>
> #ifdef CFG_ENV_IS_IN_NAND
> #define CFG_ENV_OFFSET  0x80000         /* environment starts here  */
> #define CFG_ENV_SIZE    0x20000         /* 1 sector = 128kB */
>  #endif
>
>
> Now saveenv works properly! I think it was previously a bad block in my
> nandflash?

That can always happen. And the code *should* be able to handle this. If it is 
not able to handle this situation right now (sorry, I don't know for sure), 
then we (you? ;-)) should fix this. Patches always welcome.

> I have a doubt, if I define the soft ECC (both linux, u-boot), the OOB
> section of each page of the SAMSUNG nandflash the board has (64 bytes),
> how will it be filled? Because the nandflash datasheet states that in a
> block the first byte of the OOB section in the 1st o 2nd pages must be
> FFh or it is a bad block. So it could be that ECC data (the 4 byte hw or
> software ECC) were written in this first byte of the OOB and mark the
> block as invalid for this nandflash....... (so every write will generate
> a bad bloack?)
>
> In u-boot the eccmode:
>
> nand->eccmode = NAND_ECC_HW12_2048; /* NAND_ECC_SOFT;*/
>
> What part of the OOB writes?

See drivers/nand/nand_base.c

static struct nand_oobinfo nand_oob_64 = {
	.useecc = MTD_NANDECC_AUTOPLACE,
	.eccbytes = 24,
	.eccpos = {
		40, 41, 42, 43, 44, 45, 46, 47,
		48, 49, 50, 51, 52, 53, 54, 55,
		56, 57, 58, 59, 60, 61, 62, 63},
	.oobfree = { {2, 38} }
};

So the ECC positions are: 40, 41, 42 etc, as defined above.

> I'm getting really confused... any help will be welcomed.
>
> Can ECC disabled in nandflash u-boot with some compilation option?

Not an compilation option, but a NAND driver option:

	this->eccmode = NAND_ECC_NONE;

instead of 

	this->eccmode = NAND_ECC_SOFT;

But I wouldn't recommend this. Using NAND without ECC is definitely not a good 
idea. Even for reading. So we should try to investigate further and fix the 
source of the problem. Please stick with NAND_ECC_SOFT for now, since it is 
known to work on other platform, and we have less possible error sources 
(like CPU specific HW-ECC code).

Hope this helps a little.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================