[U-Boot] U-Boot NAND-Access

[U-Boot] U-Boot NAND-Access

[Peter Niklas]

Hello,

We are using a Zynq SoC on a custom Board. We are trying to use a 
NAND-Flash (MT29F8G08ABABAWP-IT) to store the Xilinx First Stage Boot 
Loader, U-Boot, Kernel ....
We are having trouble to use the NAND-Flash in U-Boot.
Currently we are using U-Boot 2012.04.01-00304-g7639205-dirty.
and I get the Messag:
NAND:  No NAND device found!!!
nand_scan_ident for NAND failed

I enabled CMD_NAND in the specific config file:
#define CONFIG_NAND_ZYNQ
#define CONFIG_CMD_NAND
#define CONFIG_CMD_NAND_LOCK_UNLOCK
#define CONFIG_SYS_MAX_NAND_DEVICE 1
#define CONFIG_SYS_NAND_BASE XPSS_NAND_BASEADDR
#define CONFIG_MTD_DEVICE

I also tried an older version of U-Boot  (U-Boot 2011.03-dirty) before 
where I got the Output:

NAND:  No oob scheme defined for oobsize 224
No oob scheme defined for oobsize 224

I also enabled the CMD_NAND as before.
When I look into the sources I only see oob_schemes defined for 128.

Has anyone tried to use a NAND-flash with the oobsize of 224?
Is there some configuration missing?
Besides the CMD config, I did not change anything else for 
NAND-Configuration. Am I missing something?
The NAND-Flash has been tested with the Xilinx Drivers and it works.

Thanks, Regards,
Peter Niklas


CONFIDENTIALITY: The contents of this e-mail are confidential and 
intended only for the above addressee(s). If you are not the intended
recipient, or the person responsible for delivering it to the intended 
recipient, copying or delivering it to anyone else or using it in any 
unauthorized manner is prohibited and may be unlawful. If you 
receive this e-mail by mistake, please notify the sender and the 
systems administrator at straymail at tttech.com immediately. 

[U-Boot] U-Boot NAND-Access

[Wolfgang Denk]

Dear Peter Niklas,

In message <OFCB5B87EF.D3CAAEFE-ONC1257AB0.005101E8-C1257AB0.005512D0@tttech.com> you wrote:
>
> We are using a Zynq SoC on a custom Board. We are trying to use a 
> NAND-Flash (MT29F8G08ABABAWP-IT) to store the Xilinx First Stage Boot 
...
> Currently we are using U-Boot 2012.04.01-00304-g7639205-dirty.

Commmit 7639205 is not known in mainline.  We cannot help you with
code unknown to us.


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
"The pathology is to want control, not that you ever get it,  because
of course you never do."                            - Gregory Bateson

[U-Boot] U-Boot NAND-Access

[Scott Wood]

On 11/08/2012 09:31:10 AM, Peter Niklas wrote:
> Hello,
> 
> We are using a Zynq SoC on a custom Board. We are trying to use a
> NAND-Flash (MT29F8G08ABABAWP-IT) to store the Xilinx First Stage Boot
> Loader, U-Boot, Kernel ....
> We are having trouble to use the NAND-Flash in U-Boot.
> Currently we are using U-Boot 2012.04.01-00304-g7639205-dirty.
> and I get the Messag:
> NAND:  No NAND device found!!!
> nand_scan_ident for NAND failed
> 
> I enabled CMD_NAND in the specific config file:
> #define CONFIG_NAND_ZYNQ

It's not just an unrecognized (and dirty) SHA1 as Wolfgang pointed out  
(which is not necessarily that surprising for a custom board, but it's  
still code we can't see) -- there's not even any CONFIG_NAND_ZYNQ in  
mainline U-Boot.

-Scott

[U-Boot] U-Boot NAND-Access

[Peter Niklas]

Yes, I understand. Unfortunate for me.
But besides the custom uboot version:
Would I need to configure additional commands to use NAND-Flash in the 
mainline?

Regards,
Peter




From:
Scott Wood <scottwood@freescale.com>
To:
Peter Niklas <peter.niklas@tttech-automotive.com>, 
Cc:
<u-boot@lists.denx.de>
Date:
13.11.2012 04:13
Subject:
Re: [U-Boot] U-Boot NAND-Access



On 11/08/2012 09:31:10 AM, Peter Niklas wrote:
> Hello,
> 
> We are using a Zynq SoC on a custom Board. We are trying to use a
> NAND-Flash (MT29F8G08ABABAWP-IT) to store the Xilinx First Stage Boot
> Loader, U-Boot, Kernel ....
> We are having trouble to use the NAND-Flash in U-Boot.
> Currently we are using U-Boot 2012.04.01-00304-g7639205-dirty.
> and I get the Messag:
> NAND:  No NAND device found!!!
> nand_scan_ident for NAND failed
> 
> I enabled CMD_NAND in the specific config file:
> #define CONFIG_NAND_ZYNQ

It's not just an unrecognized (and dirty) SHA1 as Wolfgang pointed out 
(which is not necessarily that surprising for a custom board, but it's 
still code we can't see) -- there's not even any CONFIG_NAND_ZYNQ in 
mainline U-Boot.

-Scott



CONFIDENTIALITY: The contents of this e-mail are confidential and 
intended only for the above addressee(s). If you are not the intended
recipient, or the person responsible for delivering it to the intended 
recipient, copying or delivering it to anyone else or using it in any 
unauthorized manner is prohibited and may be unlawful. If you 
receive this e-mail by mistake, please notify the sender and the 
systems administrator at straymail at tttech.com immediately. 

[U-Boot] U-Boot NAND-Access

[Scott Wood]

On 11/13/2012 03:57:50 AM, Peter Niklas wrote:
> Yes, I understand. Unfortunate for me.
> But besides the custom uboot version:
> Would I need to configure additional commands to use NAND-Flash in the
> mainline?

You would need to add support for your hardware.

-Scott