Uboot support for MT29F2G16ABBEAH4 NAND 16 bit
Hi
has Anybody managed to load the Linux Kernel using MT29F2G16ABBEAH4 NAND or other 16 bits NAND memory?
Thanks
Marcio
--
View this message in context: http://u-boot.10912.n7.nabble.com/Uboot-support-for-MT29F2G16ABBEAH4-NAND-16-bit-tp149761.html
Sent from the U-Boot mailing list archive at Nabble.com.
Quoted 5 lines · marcio at netopen.com.br
Hi
has Anybody managed to load the Linux Kernel using MT29F2G16ABBEAH4 NAND or
other 16 bits NAND memory?
I haven't personally, but there's no general reason why 16-bit NAND shouldn't work in U-Boot. Some NAND controllers or drivers don't support it, though -- which controller are you using?
-Scott
Hi Scott
Thanks a lot for your attention.
I am using a custom
board based at the Atmel AT91SAM9M10G45-EK Development Kit. I am quite sure The Linux Kernel is properly loaded in the NAND memory.
Here is
the U-boot log.
U-Boot 2012.10-00075-g0362411-dirty (Mar 15 2013 - 11:33:53)
U-Boot code: 73F00000 -> 73F370C0 BSS: -> 73F79654 CPU:
AT91SAM9G45
Crystal frequency: 12 MHz
CPU clock : 400 MHz
Master clock :
133.333 MHzdram_initdram_init tam_ram=67108864 testa_ram_readonly:
Iniciotesta_ram_readonly: Fim
monitor len: 00079654
ramsize:
04000000
TLB table at: 73ff0000
Top of RAM usable for U-Boot at:73ff0000
Reserving 485k for U-Boot at: 73f76000 Reserving 640k formalloc() at: 73ed6000
Reserving 32 Bytes for Board Info at:73ed5fe0
Reserving 144 Bytes for Global Data at: 73ed5f50 New Stack
Pointer is: 73ed5f40
comeca a configurar a DRAM
Display
DRAMdisplay_dram_config:
DRAM: 64 MiB
reloca e perde o controle
00000000
relocation Offset is: 00076000board_init_r:
gd=73ed5f50
WARNING: Caches not enabled
monitor flash len: 0003C950
Now
running in RAM - U-Boot at: 73f76000
NAND: 256 MiBboard_init_r:
Initialize Environmetenv_relocate: Inicio gd=73ed5f50
gd->env_valid=0
Using default environment
env_relocate:
Fimboard_init_r: jumptableboard_init_r: jumptable sai
In: serial
Out:
serial
Err: serial
board_init_r:interruptsboard_init_r:
initializeboard_init_r: main loop
### main_loop entered: bootdelay=3
### main_loop: bootcmd="nand read 0x70000000 0x200000 0x300000;bootm 0x70000000"
Hit any key to stop autoboot: 0
NAND read: device 0
offset 0x200000, size 0x300000
3145728 bytes read: OK
* kernel: cmdline
image address = 0x70000000
## Booting kernel from Legacy Image at
70000000 ...
Image Name: Linux-2.6.39.4
Image Type: ARM Linux Kernel
Image (uncompressed)
Data Size: 3630052 Bytes = 3.5 MiB
Load Address:
70008000
Entry Point: 70008000
Verifying Checksum ... Bad Data
CRC
ERROR: can't get kernel image!
U-Boot Marcio>
Quoted 1 line
On 03/14/2013
Quoted 2 lines · 05:52:57 PM, marcio at netopen.com.br [1]wrote:
Quoted 2 lines
Hi has Anybody
managed to load the Linux Kernel using MT29F2G16ABBEAH4 NAND or other 16 bits NAND memory?
Quoted 2 lines
I haven't personally, but there's no general
reason why 16-bit NAND
Quoted 1 line
shouldn't work in U-Boot. Some NAND
controllers or drivers don't
Quoted 1 line
support it, though -- which controller
are you using?
Quoted 2 lines
-Scott
Links:
------
[1]
mailto:marcio at netopen.com.br