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: 73F0 -> 73F370C0 BSS: -> 73F79654
CPU:
AT91SAM9G45
Crystal frequency: 12 MHz
CPU clock : 400 MHz
Master clock :
133.333 MHz
dram_init
dram_init tam_ram=67108864
testa_ram_readonly:
Inicio
testa_ram_readonly: Fim
monitor len: 00079654
ramsize:
0400
TLB table at: 73ff
Top of RAM usable for U-Boot at:
73ff
Reserving 485k for U-Boot at: 73f76000
Reserving 640k for
malloc() 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
DRAM
display_dram_config:
DRAM: 64 MiB
reloca e perde o controle
relocation Offset is: 00076000
board_init_r:
gd=73ed5f50
WARNING: Caches not enabled
monitor flash len: 0003C950
Now
running in RAM - U-Boot at: 73f76000
NAND: 256 MiB
board_init_r:
Initialize Environmet
env_relocate: Inicio gd=73ed5f50
gd->env_valid=0
Using default environment
env_relocate:
Fim
board_init_r: jumptable
board_init_r: jumptable sai
In: serial
Out:
serial
Err: serial
board_init_r:interrupts
board_init_r:
initialize
board_init_r: main loop
### main_loop entered: bootdelay=3
### main_loop: bootcmd="nand read 0x7000 0x20 0x30;bootm
0x7000"
Hit any key to stop autoboot: 0
NAND read: device 0
offset 0x20, size 0x30
3145728 bytes read: OK
* kernel: cmdline
image address = 0x7000
## Booting kernel from Legacy Image at
7000 ...
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>
> On 03/14/2013
05:52:57 PM, mar...@netopen.com.br [1]wrote:
>
>> 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
Links:
--
[1]
mailto:mar...@netopen.com.br
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot