Re: [U-Boot] sam9x5 can't find Nand flash
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. ==="
At 2012-11-19 13:37:15,alex laub923@163.com 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
At 2012-11-19 11:19:25,"Bo Shen" voice.shen@atmel.com 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
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 laub923@163.com 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" <voice.shen@atmel.com <mailto:voice.shen@atmel.com>> 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 >
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
At 2012-11-19 14:10:27,"Bo Shen" voice.shen@atmel.com wrote:
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 laub923@163.com 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 MiBYou 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" <voice.shen@atmel.com <mailto:voice.shen@atmel.com>> 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 >
Dear alex,
On 19.11.2012 11:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
if you provide a rebased version on current HEAD we will do so.
Best regards
Andreas Bießmann
Hi Andreas,
On 11/19/2012 19:22, Andreas Bießmann wrote:
Dear alex,
On 19.11.2012 11:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
if you provide a rebased version on current HEAD we will do so.
What's your mean about this? What Alex ask has been merged into mainline. His issue is that he change the offset of the u-boot environment cause the overlap with u-boot.
Best Regards, Bo Shen
Dear Bo Shen,
On 20.11.2012 03:01, Bo Shen wrote:
Hi Andreas,
On 11/19/2012 19:22, Andreas Bießmann wrote:
Dear alex,
On 19.11.2012 11:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
if you provide a rebased version on current HEAD we will do so.
What's your mean about this? What Alex ask has been merged into mainline. His issue is that he change the offset of the u-boot environment cause the overlap with u-boot.
so is that change required globally? Why don't apply it to mainline then?
Best regards
Andreas Bießmann
Dear Bo Shen,
On 26.11.2012 11:48, Andreas Bießmann wrote:
Dear Bo Shen,
On 20.11.2012 03:01, Bo Shen wrote:
Hi Andreas,
On 11/19/2012 19:22, Andreas Bießmann wrote:
Dear alex,
On 19.11.2012 11:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
if you provide a rebased version on current HEAD we will do so.
What's your mean about this? What Alex ask has been merged into mainline. His issue is that he change the offset of the u-boot environment cause the overlap with u-boot.
so is that change required globally? Why don't apply it to mainline then?
damn, it is http://patchwork.ozlabs.org/patch/198524/, correct? I should have read the atmel related stuff more frequently these days. Sorry for that, I was busy with nand related stuff on omap.
Best regards
Andreas Bießmann
Hi Andreas,
On 11/26/2012 19:01, Andreas Bießmann wrote:
Dear Bo Shen,
On 26.11.2012 11:48, Andreas Bießmann wrote:
Dear Bo Shen,
On 20.11.2012 03:01, Bo Shen wrote:
Hi Andreas,
On 11/19/2012 19:22, Andreas Bießmann wrote:
Dear alex,
On 19.11.2012 11:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
if you provide a rebased version on current HEAD we will do so.
What's your mean about this? What Alex ask has been merged into mainline. His issue is that he change the offset of the u-boot environment cause the overlap with u-boot.
so is that change required globally? Why don't apply it to mainline then?
damn, it is http://patchwork.ozlabs.org/patch/198524/, correct? I should have read the atmel related stuff more frequently these days. Sorry for that, I was busy with nand related stuff on omap.
For at91sam9x5ek board, the environment offset in mainline is OK. This patch is for other Atmel boards which I found there are overlap between u-boot and u-boot env.
Best Regards, Bo Shen
Hi Alex,
On 11/19/2012 18:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
The mainline for at91sam9x5ek is supported. You can find it on tag 2012.10 and after.
But, one thing should keep in mind, it only supports mainline Linux kernel for at91sam9x5ek.
Best Regards, Bo Shen
Can you tell me from which tag on mainline kernel can work with mainline u-boot?
At 2012-11-20 09:55:35,"Bo Shen" voice.shen@atmel.com wrote:
Hi Alex,
On 11/19/2012 18:23, alex wrote:
Hi: Thanks, it can work now. BTW, one question whether the atmel' patch on v2010.6 is merged int u-boot mainline?
The mainline for at91sam9x5ek is supported. You can find it on tag 2012.10 and after.
But, one thing should keep in mind, it only supports mainline Linux kernel for at91sam9x5ek.
Best Regards, Bo Shen
Hi Alex,
On 11/20/2012 11:11, alex wrote:
Can you tell me from which tag on mainline kernel can work with mainline u-boot?
When the mainline kernel support at91sam9x5ek, it can work with mainline u-boot. You can choose the kernel version as you prefer.
Btw, this is u-boot ML. If you want to know much more about the Linux kernel for at91sam9x5ek. Please send e-mail to Linux kernel ML.
Best Regards, Bo Shen
participants (3)
-
alex -
Andreas Bießmann -
Bo Shen