From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bo Shen Date: Mon, 19 Nov 2012 14:10:27 +0800 Subject: [U-Boot] sam9x5 can't find Nand flash In-Reply-To: <75d85c55.6d24.13b172e466a.Coremail.laub923@163.com> References: <33d0ae3.3d99.13b1697bd61.Coremail.laub923@163.com> <50A9A53D.4060000@atmel.com> <31f4d5f2.6c66.13b172ba82e.Coremail.laub923@163.com> <75d85c55.6d24.13b172e466a.Coremail.laub923@163.com> Message-ID: <50A9CD53.7000501@atmel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Alex, On 11/19/2012 13:40, alex wrote: > more information. samba script as below: > > ## Falshing binaries > puts "-I- === Initialize the NAND access ===" > NANDFLASH::Init > > puts "-I- === Enable PMECC OS Parameters ===" > NANDFLASH::NandHeaderValue HEADER 0xc0c00405 > > puts "-I- === Erase all the NAND flash blocs and test the erasing ===" > NANDFLASH::EraseAllNandFlash > > puts "-I- === Load the bootstrap: nandflash_at91sam9-ek in the first > sector ===" > NANDFLASH::SendBootFilePmeccCmd $bootstrapFile > > puts "-I- === Load the u-boot image ===" > send_file {NandFlash} "$ubootFile" $ubootAddr 0 > > puts "-I- === Load the u-boot env image ===" > send_file {NandFlash} "$ubootenvFile" $ubootenvAddr 0 > > puts "-I- === Load the Kernel image ===" > send_file {NandFlash} "$kernelFile" $kernelAddr 0 > > puts "-I- === Enable trimffs ===" > NANDFLASH::NandSetTrimffs 1 > > puts "-I- === Load the linux file system ===" > send_file {NandFlash} "$rootfsFile" $rootfsAddr 0 > > puts "-I- === DONE. ===" > This is no help. Without any useful information. > > > At 2012-11-19 13:37:15,alex wrote: > > I use u-boot v2010.06 with atmel's patch. I give u-boot 512K size. > > U-Boot 2010.06-00002-gb006d3d-dirty (Nov 19 2012 - 09:53:38) > > DRAM: 128 MiB > NAND: No NAND device found!!! > NAND Flash not found ! > No NAND device found!!! > 0 MiB You should also provide bootstrap log info. I think the code is get from www.at91.com/linux4sam. Anyway, I assume that you use the source code and package get for the upper website. If so, the u-boot environment you change is overlap with u-boot. (If you write the u-boot at offset 0x40000, the size is larger than 256K, that means: u-boot offset + u-boot size > 0x80000). So, when save environment, it will overwrite the u-boot, which cause this issue. Please check it again. If all thing as I guess, you can change the u-boot offset to 0x20000, or change environment offset to 0xa0000. you can choose which you prefer. Best Regards, Bo Shen > > > At 2012-11-19 11:19:25,"Bo Shen" > wrote: > >Hi Alex, > > > >On 11/19/2012 10:55, alex wrote: > >> Hi MAINTAINER: > >> Now I develop our product based on sam9x25 EVK, and redefine our NAND > >> partitions. I set u-boot environment in flash address0x80000. > >> if "saveenv" and "reset", u-boot will print "can't find NAND flash". If > >> I set u-boot environment in the address 0xc0000 as EVK board, it's OK. I > >> cant' know the reason. > > > >Which u-boot version do you use? Please also paste the u-boot boot log here. > > > >Please also check the u-boot file size, will the env overlap with it? > > > >Best Regards, > >Bo Shen > > > > > > >