AT91SAM9XE512 NandFlash Booting Problem

This forum is for users of Microchip MPUs and who are interested in using Linux OS.

Moderator: nferre

dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

AT91SAM9XE512 NandFlash Booting Problem

Tue Feb 05, 2013 5:53 am

I am using a custom board designed like that of EVB AT91SAM9XEEK.

I have successfully ported linux on my custom board, but due to unavailability of NandFlash MT29F2G08AAC, I purchased NandFlash MT29F2G08ABAEA from Digikey with same capacity and data bits. But with my new NandFlash Linux is not booting up(nothing shown on terminal) even though I am able to download files into NandFlash. using SAM-BA. I am using the Angstrom based demo files from Linux4SAM website.

What could be the possible reason? Please help me.
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: AT91SAM9XE512 NandFlash Booting Problem

Tue Feb 05, 2013 4:50 pm

dhanishvijayan wrote:What could be the possible reason? Please help me.
a) It's not supported by the ROM
b) It was not uploaded with "Send Boot File"
c) The NAND ID is not recognized by the AT91BootStrap code

Stick a JTAG probe on it and debug it.
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 06, 2013 7:41 am

Thanks CptTitanic for your comments. What does "Send Boot File" mean?
Sorry for the question if its only a basic thing. I am a newbie.

I was able to read and write data using jtag in IAR platform with the new flash MT29F2G08ABAEA. And it gives the chip ID 2c da 90 95 6 when initialised using SAM-BA, which was different from CHIP ID 2c da 80 15 d0 with EVB Chip MT29F2G08AAC. Is it possible to make changes in the AT91BootStrap Code for enabling the support for the new Nandflash and rebuild the sources?.

Please someone guide me if it is possible to modify the bootstrap and linux kernel accordingly. Thanks in advance.
Warlord
Posts: 7
Joined: Fri Jan 25, 2013 1:52 pm

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 06, 2013 7:58 am

Atmel bootstrap uses only first two bytes of ID. These two flashes have these two bytes the same.
What does "Send Boot File" mean?
This means the operation of writing the bootstrap to a flash by use of SAM-BA software.
1. Initialize NAND flash
2. Erase it all
3. Send Boot File
All this steps must be made to have a successful boot.
If this fails you should download the bootstrap code, turn on the debug level to a maximum to find out a booting details and problem. Then recompile and burn using the steps spoken above.
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 06, 2013 12:03 pm

Image
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Tue Feb 12, 2013 4:12 am

Thanks for the reply. I will be trying these out today and will post the results.
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Tue Feb 12, 2013 7:42 am

Dear Warlord and CptTitanic,
I didnt see Send Boot File in SAMBA. I am using SAMBA version 2.12 and board at91sam9xe512.
Is there any alternate method??.
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 13, 2013 12:12 am

dhanishvijayan wrote:Is there any alternate method??
How do you get boot code on it now, or on the AT91SAM9XE-EK? Do you have an EK board to try and leverage that working knowledge against your own?

Do you use the internal flash? Do you enable the "Boot from Flash (GPNVM3)" in the Flash (On Chip) dialog?

Have you run any code on your board? From the SRAM, SDRAM, Flash?

Have you downloaded and debugged any AT91BootStrap code, or equivalent, or whatever you're using?
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 13, 2013 7:53 am

Thanks CptTitanic for reply, I will describe the testing procedure done on our lab below.

I am setting Boot from Flash (GPNVM3) via SAMBA and booting from internal flash(same procedure from the Demo Script from Linux4SAM).

I have a working AT91SAM9XEEK EVB which is working fine using NandFlash and DataFlash Boot demo files from Linux4Sam.

My custom board does not contain serial Dataflash, so I have only NandFlash Boot option. I have used old Nandflsh IC on the custom board and is booting up fine. But due to unavailability of old type flash I have used a new Nandflash (same series but different ID). But nothing shown on the terminal. I have even experimented by replacing Evaluation board NandFlash with new one and problem persists as on the custom board. I doubt there is something to do with bootstrap or new Nandflash IC, but didnt get any ideas for encountering the problem.

One more thing i have noticed is that after replacing with the new NandFlash ic on EVB, I am able to load linux OS using Dataflash demo file, but takes more time to find NandFlash after uboot loaded from Serial Dataflash.

I have tested the new Nandflash using IAR (both Custom board and EVB) and is working fine.
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: AT91SAM9XE512 NandFlash Booting Problem

Wed Feb 13, 2013 9:38 am

Ok, so next on the check list would be the supported NAND ID's which in the current release should reside in at91bootstrap-master\driver\nandflash.c

Code: Select all

static struct nand_chip nand_ids[] = {
	/* Samsung K9F2G08U0M 256MB */
	{0xecda, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Samsung K9F2G08U0A 256MB */
	{0xecaa, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Micron MT29F2G16AAB 256MB */
	{0x2cca, 0x800, 0x20000, 0x800, 0x40, 0x1},
	/* Micron MT29F2G08AAC 256MB  */
	{0x2cda, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Micron MT29F2G08ABD 256MB */
	{0x2caa, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Mircon MT29H8G08ACAH1 1GB */
	{0x2c38, 0x800, 0x80000, 0x1000, 0xe0, 0x0},
	{0,}
};
You'll have to add your new flash, and perhaps build with CONFIG_DEBUG to provide some diagnostic output.

The ID code looks the same, so I would anticipate you'll need to dig in and debug the NAND support and timing to better understand the issue, and if it is resolvable.
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Fri Feb 15, 2013 6:59 am

Thanks for the comments CptTitanic.

I have just seen the source code of bootstrap loader that you have posted. I think the device ids are same(First two bytes in source code).

So I will check and compare the timings of new and old nandflash, and update my findings if any.
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Thu Feb 21, 2013 6:36 am

Now the new problem arise. I have been using the Demofiles from Linux4SAM website, for booting from NandFlash in my AT91SAM9XEEK development board. I have downloaded the source file for at91bootstrap ver 3.5.1, but the configuration file for at91sam9xeek was missing. So I used at91sam9260 board nandboot configration and edited it and compiled without error using CodeSourcery compiler 2012.09 for arm.

I have replaced the demo file, but my board is not booting up. Nothing is shown on my terminal. I have experimented by toggling some options, but didnt work. I am also attaching the configuration details below that i have used.

#
# Automatically generated make config: don't edit
# Wed Feb 20 14:09:46 2013
#
HAVE_DOT_CONFIG=y
CONFIG_BOARDNAME="at91sam9xeek"
# CONFIG_AT91SAM9260EK is not set
# CONFIG_AT91SAM9261EK is not set
# CONFIG_AT91SAM9263EK is not set
# CONFIG_AT91SAM9RLEK is not set
CONFIG_AT91SAM9XEEK=y
# CONFIG_AT91SAM9G10EK is not set
# CONFIG_AT91SAM9G20EK is not set
# CONFIG_AT91SAM9M10G45EK is not set
# CONFIG_AT91SAM9X5EK is not set
# CONFIG_AT91SAM9N12EK is not set
# CONFIG_AT91SAMA5D3XEK is not set
CONFIG_CHIP="AT91SAM9XE"
CONFIG_BOARD="at91sam9xeek"
CONFIG_MACH_TYPE="0x44B"
CONFIG_LINK_ADDR="0x000000"
CONFIG_DATA_SECTION_ADDR="0x304000"
CONFIG_TOP_OF_MEMORY="0x306000"
# CONFIG_CRYSTAL_12_000MHZ is not set
# CONFIG_CRYSTAL_16_000MHZ is not set
# CONFIG_CRYSTAL_16_36766MHZ is not set
CONFIG_CRYSTAL_18_432MHZ=y
ALLOW_CRYSTAL_18_432MHZ=y
CONFIG_CRYSTAL="CRYSTAL_18_432MHZ"
# CONFIG_CPU_CLK_166MHZ is not set
# CONFIG_CPU_CLK_180MHZ is not set
CONFIG_CPU_CLK_200MHZ=y
# CONFIG_CPU_CLK_240MHZ is not set
# CONFIG_CPU_CLK_266MHZ is not set
# CONFIG_CPU_CLK_400MHZ is not set
# CONFIG_CPU_CLK_533MHZ is not set
ALLOW_CPU_CLK_200MHZ=y
# DISABLE_CPU_CLK_240MHZ is not set
# CONFIG_BUS_SPEED_83MHZ is not set
# CONFIG_BUS_SPEED_90MHZ is not set
CONFIG_BUS_SPEED_100MHZ=y
# CONFIG_BUS_SPEED_133MHZ is not set
# ALLOW_PIO3 is not set
# CPU_HAS_PMECC is not set
# CONFIG_LOAD_ONE_WIRE is not set
# CONFIG_MMC_SUPPORT is not set

#
# Memory selection
#
CONFIG_SDRAM=y
# CONFIG_SDDRC is not set
# CONFIG_DDR2 is not set
ALLOW_DATAFLASH=y
# ALLOW_FLASH is not set
ALLOW_NANDFLASH=y
# ALLOW_SDCARD is not set
# ALLOW_HSMCI is not set
# ALLOW_PSRAM is not set
# ALLOW_SDRAM_16BIT is not set
# CONFIG_RAM_32MB is not set
CONFIG_RAM_64MB=y
# CONFIG_RAM_128MB is not set
# CONFIG_RAM_256MB is not set
# CONFIG_RAM_512MB is not set
# CONFIG_DATAFLASH is not set
# CONFIG_FLASH is not set
CONFIG_NANDFLASH=y
# CONFIG_SDCARD is not set
CONFIG_MEMORY="nandflash"
# CONFIG_SDCARD_HS is not set
ALLOW_BOOT_FROM_DATAFLASH_CS0=y
ALLOW_BOOT_FROM_DATAFLASH_CS1=y
DATAFLASHCARD_ON_CS0=y

#
# NAND Flash configuration
#
CONFIG_ENABLE_SW_ECC=y
# CONFIG_NANDFLASH_SMALL_BLOCKS is not set
# ALLOW_NANDFLASH_RECOVERY is not set
CONFIG_BOOTSTRAP_MAXSIZE="23000"
CONFIG_PROJECT="nandflash"
CONFIG_LOAD_UBOOT=y
# CONFIG_LOAD_LINUX is not set
# CONFIG_LOAD_1MB is not set
# CONFIG_LOAD_4MB is not set
# CONFIG_LOAD_64KB is not set
CONFIG_IMG_ADDRESS="0x00020000"
CONFIG_IMG_SIZE="0x00080000"
CONFIG_JUMP_ADDR="0x20003E30"

#
# U-Boot Image Storage Setup
#
CONFIG_IMAGE_NAME="uboot"
CONFIG_LONG_TEST=y
CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_LOUD is not set
# CONFIG_DEBUG_VERY_LOUD is not set
CONFIG_HW_INIT=y
# CONFIG_USER_HW_INIT is not set
CONFIG_THUMB=y
CONFIG_DISABLE_WATCHDOG=y


Can anyone share the configuration file that is used to compile the demofile for AT91SAM9XEEK, so that I can troubleshoot the NandFlash Booting problem
dhanishvijayan
Posts: 15
Joined: Wed Jun 13, 2012 3:46 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Mon Mar 04, 2013 7:15 am

Finally got the NandFlash MT29F2G08ABAEA working fine in my custom board.

I will share the Configuration used, may be helpful to others using the same processor.

Processor: AT91SAM9XE512
Board: AT91SAM9XE-EK
Boot: NandBoot
Bootstrap version: AT91BOOTSTRAP Ver 3.5.1
Compiler used: CodeSourcery 2009 Q3


#
# Automatically generated make config: don't edit
# Thu Feb 28 17:28:11 2013
#
HAVE_DOT_CONFIG=y
CONFIG_BOARDNAME="at91sam9xeek"
# CONFIG_AT91SAM9260EK is not set
# CONFIG_AT91SAM9261EK is not set
# CONFIG_AT91SAM9263EK is not set
# CONFIG_AT91SAM9RLEK is not set
CONFIG_AT91SAM9XEEK=y
# CONFIG_AT91SAM9G10EK is not set
# CONFIG_AT91SAM9G20EK is not set
# CONFIG_AT91SAM9M10G45EK is not set
# CONFIG_AT91SAM9X5EK is not set
# CONFIG_AT91SAM9N12EK is not set
# CONFIG_AT91SAMA5D3XEK is not set
CONFIG_CHIP="AT91SAM9XE"
CONFIG_BOARD="at91sam9xeek"
CONFIG_MACH_TYPE="0x44B"
CONFIG_LINK_ADDR="0x000000"
CONFIG_DATA_SECTION_ADDR="0x304000"
CONFIG_TOP_OF_MEMORY="0x306000"
# CONFIG_CRYSTAL_12_000MHZ is not set
# CONFIG_CRYSTAL_16_000MHZ is not set
# CONFIG_CRYSTAL_16_36766MHZ is not set
CONFIG_CRYSTAL_18_432MHZ=y
ALLOW_CRYSTAL_18_432MHZ=y
CONFIG_CRYSTAL="CRYSTAL_18_432MHZ"
# CONFIG_CPU_CLK_166MHZ is not set
# CONFIG_CPU_CLK_180MHZ is not set
CONFIG_CPU_CLK_200MHZ=y
# CONFIG_CPU_CLK_240MHZ is not set
# CONFIG_CPU_CLK_266MHZ is not set
# CONFIG_CPU_CLK_400MHZ is not set
# CONFIG_CPU_CLK_533MHZ is not set
ALLOW_CPU_CLK_200MHZ=y
# DISABLE_CPU_CLK_240MHZ is not set
# CONFIG_BUS_SPEED_83MHZ is not set
# CONFIG_BUS_SPEED_90MHZ is not set
CONFIG_BUS_SPEED_100MHZ=y
# CONFIG_BUS_SPEED_133MHZ is not set
# ALLOW_PIO3 is not set
# CPU_HAS_PMECC is not set
# CONFIG_LOAD_ONE_WIRE is not set
# CONFIG_MMC_SUPPORT is not set

#
# Memory selection
#
CONFIG_SDRAM=y
# CONFIG_SDDRC is not set
# CONFIG_DDR2 is not set
ALLOW_DATAFLASH=y
# ALLOW_FLASH is not set
ALLOW_NANDFLASH=y
# ALLOW_SDCARD is not set
# ALLOW_HSMCI is not set
# ALLOW_PSRAM is not set
# ALLOW_SDRAM_16BIT is not set
# CONFIG_RAM_32MB is not set
CONFIG_RAM_64MB=y
# CONFIG_RAM_128MB is not set
# CONFIG_RAM_256MB is not set
# CONFIG_RAM_512MB is not set
# CONFIG_DATAFLASH is not set
# CONFIG_FLASH is not set
CONFIG_NANDFLASH=y
# CONFIG_SDCARD is not set
CONFIG_MEMORY="nandflash"
# CONFIG_SDCARD_HS is not set
ALLOW_BOOT_FROM_DATAFLASH_CS0=y
ALLOW_BOOT_FROM_DATAFLASH_CS1=y
DATAFLASHCARD_ON_CS0=y

#
# NAND Flash configuration
#
CONFIG_ENABLE_SW_ECC=y
# CONFIG_NANDFLASH_SMALL_BLOCKS is not set
# ALLOW_NANDFLASH_RECOVERY is not set
CONFIG_BOOTSTRAP_MAXSIZE="23000"
CONFIG_PROJECT="nandflash"
CONFIG_LOAD_UBOOT=y
# CONFIG_LOAD_LINUX is not set
# CONFIG_LOAD_1MB is not set
# CONFIG_LOAD_4MB is not set
# CONFIG_LOAD_64KB is not set
CONFIG_IMG_ADDRESS="0x00020000"
CONFIG_IMG_SIZE="0x00040000"
CONFIG_JUMP_ADDR="0x23F00000"

#
# U-Boot Image Storage Setup
#
CONFIG_IMAGE_NAME="uboot"
# CONFIG_LONG_TEST is not set
CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_LOUD is not set
# CONFIG_DEBUG_VERY_LOUD is not set
CONFIG_HW_INIT=y
# CONFIG_USER_HW_INIT is not set
CONFIG_THUMB=y
CONFIG_DISABLE_WATCHDOG=y
smart
Posts: 16
Joined: Sat Dec 31, 2016 10:42 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Tue Jan 03, 2017 5:16 am

dhanishvijayan wrote:Finally got the NandFlash MT29F2G08ABAEA working fine in my custom board.

I will share the Configuration used, may be helpful to others using the same processor.

Processor: AT91SAM9XE512
Board: AT91SAM9XE-EK
Boot: NandBoot
Bootstrap version: AT91BOOTSTRAP Ver 3.5.1
Compiler used: CodeSourcery 2009 Q3


#
# Automatically generated make config: don't edit
# Thu Feb 28 17:28:11 2013
#
HAVE_DOT_CONFIG=y
CONFIG_BOARDNAME="at91sam9xeek"
# CONFIG_AT91SAM9260EK is not set
# CONFIG_AT91SAM9261EK is not set
# CONFIG_AT91SAM9263EK is not set
# CONFIG_AT91SAM9RLEK is not set
CONFIG_AT91SAM9XEEK=y
# CONFIG_AT91SAM9G10EK is not set
# CONFIG_AT91SAM9G20EK is not set
# CONFIG_AT91SAM9M10G45EK is not set
# CONFIG_AT91SAM9X5EK is not set
# CONFIG_AT91SAM9N12EK is not set
# CONFIG_AT91SAMA5D3XEK is not set
CONFIG_CHIP="AT91SAM9XE"
CONFIG_BOARD="at91sam9xeek"
CONFIG_MACH_TYPE="0x44B"
CONFIG_LINK_ADDR="0x000000"
CONFIG_DATA_SECTION_ADDR="0x304000"
CONFIG_TOP_OF_MEMORY="0x306000"
# CONFIG_CRYSTAL_12_000MHZ is not set
# CONFIG_CRYSTAL_16_000MHZ is not set
# CONFIG_CRYSTAL_16_36766MHZ is not set
CONFIG_CRYSTAL_18_432MHZ=y
ALLOW_CRYSTAL_18_432MHZ=y
CONFIG_CRYSTAL="CRYSTAL_18_432MHZ"
# CONFIG_CPU_CLK_166MHZ is not set
# CONFIG_CPU_CLK_180MHZ is not set
CONFIG_CPU_CLK_200MHZ=y
# CONFIG_CPU_CLK_240MHZ is not set
# CONFIG_CPU_CLK_266MHZ is not set
# CONFIG_CPU_CLK_400MHZ is not set
# CONFIG_CPU_CLK_533MHZ is not set
ALLOW_CPU_CLK_200MHZ=y
# DISABLE_CPU_CLK_240MHZ is not set
# CONFIG_BUS_SPEED_83MHZ is not set
# CONFIG_BUS_SPEED_90MHZ is not set
CONFIG_BUS_SPEED_100MHZ=y
# CONFIG_BUS_SPEED_133MHZ is not set
# ALLOW_PIO3 is not set
# CPU_HAS_PMECC is not set
# CONFIG_LOAD_ONE_WIRE is not set
# CONFIG_MMC_SUPPORT is not set

#
# Memory selection
#
CONFIG_SDRAM=y
# CONFIG_SDDRC is not set
# CONFIG_DDR2 is not set
ALLOW_DATAFLASH=y
# ALLOW_FLASH is not set
ALLOW_NANDFLASH=y
# ALLOW_SDCARD is not set
# ALLOW_HSMCI is not set
# ALLOW_PSRAM is not set
# ALLOW_SDRAM_16BIT is not set
# CONFIG_RAM_32MB is not set
CONFIG_RAM_64MB=y
# CONFIG_RAM_128MB is not set
# CONFIG_RAM_256MB is not set
# CONFIG_RAM_512MB is not set
# CONFIG_DATAFLASH is not set
# CONFIG_FLASH is not set
CONFIG_NANDFLASH=y
# CONFIG_SDCARD is not set
CONFIG_MEMORY="nandflash"
# CONFIG_SDCARD_HS is not set
ALLOW_BOOT_FROM_DATAFLASH_CS0=y
ALLOW_BOOT_FROM_DATAFLASH_CS1=y
DATAFLASHCARD_ON_CS0=y

#
# NAND Flash configuration
#
CONFIG_ENABLE_SW_ECC=y
# CONFIG_NANDFLASH_SMALL_BLOCKS is not set
# ALLOW_NANDFLASH_RECOVERY is not set
CONFIG_BOOTSTRAP_MAXSIZE="23000"
CONFIG_PROJECT="nandflash"
CONFIG_LOAD_UBOOT=y
# CONFIG_LOAD_LINUX is not set
# CONFIG_LOAD_1MB is not set
# CONFIG_LOAD_4MB is not set
# CONFIG_LOAD_64KB is not set
CONFIG_IMG_ADDRESS="0x00020000"
CONFIG_IMG_SIZE="0x00040000"
CONFIG_JUMP_ADDR="0x23F00000"

#
# U-Boot Image Storage Setup
#
CONFIG_IMAGE_NAME="uboot"
# CONFIG_LONG_TEST is not set
CONFIG_DEBUG=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_LOUD is not set
# CONFIG_DEBUG_VERY_LOUD is not set
CONFIG_HW_INIT=y
# CONFIG_USER_HW_INIT is not set
CONFIG_THUMB=y
CONFIG_DISABLE_WATCHDOG=y


nice :lol: !
i have the question like same your trouble.
my custom board is AT91SAM9X25 ref the AT91SAM99X35-EK SCH board.
but my custom board use nandflash is MT29F2G08ABAEAWP .so the EK board is MT29F2G08AAD
and them ID is not same too .
i run the ATsoftpacket for IAR by in DDR2 demo is fine that can be read/write or read the correct nandflash ID
but i use SAM-BA2.16 can not execute " enable nandflash " the DEBUG uart show some information that it is end of the applte the pmbox->commend has changed ..it led to return the PC SAM-BA2.16 is timout .
so far ,i can not find any way to solve them ..
i am a newbie than you ...
if you have any way please tell me :D .
many thanks

M-phone :+86 13346239466
QQ:925295580
e-mail:925295580@qq.com
smart
Posts: 16
Joined: Sat Dec 31, 2016 10:42 am

Re: AT91SAM9XE512 NandFlash Booting Problem

Tue Jan 03, 2017 5:26 am

CptTitanic wrote:Ok, so next on the check list would be the supported NAND ID's which in the current release should reside in at91bootstrap-master\driver\nandflash.c

Code: Select all

static struct nand_chip nand_ids[] = {
	/* Samsung K9F2G08U0M 256MB */
	{0xecda, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Samsung K9F2G08U0A 256MB */
	{0xecaa, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Micron MT29F2G16AAB 256MB */
	{0x2cca, 0x800, 0x20000, 0x800, 0x40, 0x1},
	/* Micron MT29F2G08AAC 256MB  */
	{0x2cda, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Micron MT29F2G08ABD 256MB */
	{0x2caa, 0x800, 0x20000, 0x800, 0x40, 0x0},
	/* Mircon MT29H8G08ACAH1 1GB */
	{0x2c38, 0x800, 0x80000, 0x1000, 0xe0, 0x0},
	{0,}
};
You'll have to add your new flash, and perhaps build with CONFIG_DEBUG to provide some diagnostic output.

The ID code looks the same, so I would anticipate you'll need to dig in and debug the NAND support and timing to better understand the issue, and if it is resolvable.
please help me and the link is :
discussions/viewtopic.php/t,25666.html

many tks !! :D

Return to “Linux”

Who is online

Users browsing this forum: No registered users and 2 guests