[U-Boot] AT91SAM9M10 Custom Board U-boot reboot after Wrong Image Format
Hi
Our board reboots after send Wrong Image Format message to the console and hangs. The Linux uImage is correctly placed in the NAND 0X200000. The console input is somehow inhibit. I cannot type anything on it until the board reboots . The board is an AT91SAM9M10 custom board based on the AT91SAM9M10G45-ek development kit. It has only USB, Serial(DBGU), DDR2 and NAND. I have tried to remove the LCD code but the linker says that printk is missing.
Any clue? Thanks
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hello,
On 3/13/2013 20:26, marcio@netopen.com.br wrote:
Hi
Our board reboots after send Wrong Image Format message to the console and hangs.
How do you do this? what output from console?
The Linux uImage is correctly placed in the NAND 0X200000. The console input is somehow inhibit. I cannot type anything on it until the board reboots .
You mean, you can not interactive with u-boot, am I right?
The board is an AT91SAM9M10 custom board based on the AT91SAM9M10G45-ek development kit. It has only USB, Serial(DBGU), DDR2 and NAND. I have tried to remove the LCD code but the linker says that printk is missing.
Please remove LCD related #defined in board configuration header, while not remove the code.
What the detail message for "printk is missing."
BTW, Which version u-boot do you use?
Best Regards, Bo Shen
Hi Bo Shen
Thanks for you help.
I have removed the LCD define and I found out that ṕrintk was introduced in a piece of code that I imported from a code of mine.
the version is:
U-Boot 2012.10-00075-g0362411-dirty
Now I managed to load the linux kernel but I still get Wrong Image Format message and the console input does not work.
It seems something related to the 16 bits NAND I am using. I have modified the code to accpet 16 bits NAND but the probem remains.
Thanks again
Marcio
On Wed, 13 Mar 2013 18:32:30 -0700 (PDT), Bo Shen-3 [via U-Boot] wrote:
Hello,
On 3/13/2013 20:26, [hidden
email] wrote:
Hi
Our board reboots after send Wrong Image
Format message to the console and
hangs.
How do you do this?
what output from console?
The Linux uImage is correctly placed in
the NAND 0X200000. The
console input is somehow inhibit. I cannot
type anything on it until the
board reboots .
You mean, you
can not interactive with u-boot, am I right?
The board is an
AT91SAM9M10 custom board based on the AT91SAM9M10G45-ek
development
kit.
It has only USB, Serial(DBGU), DDR2 and NAND. I have tried
to remove the LCD code but the linker says that printk is
missing.
Please remove LCD related #defined in board configuration header,
while
not remove the code.
What the detail message for "printk
is missing."
BTW, Which version u-boot do you use?
Best
Regards,
Bo Shen _______________________________________________
U-Boot mailing list [hidden email]
http://lists.denx.de/mailman/listinfo/u-boot [1]
-------------------------
If you reply to this email, your message
will be added to the discussion below: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [2]
To unsubscribe from AT91SAM9M10 Custom Board U-boot reboot after
Wrong Image Format, click here [3].
NAML [4]
Links: ------ [1] http://lists.denx.de/mailman/listinfo/u-boot [2] http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [3] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe... [4] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewe...
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi Bo Shen
I have used a SAMBA old version and I managed to write the Linux Kernel that can be recognized by U-boot but now it sends a message "Veritying Checksum ....: Bad Data CRC. It seems that U-Boot is only reading the first sector OK and the rest of the Kernel is being worngly read.
Thanks for your attention
Marcio
On Wed, 13 Mar 2013 18:32:30 -0700 (PDT), Bo Shen-3 [via U-Boot] wrote:
Hello,
On
3/13/2013 20:26, [hidden email] wrote:
Hi
Our board reboots
after send Wrong Image Format message to the console and
hangs.
How do you do this? what output from console?
The Linux uImage
is correctly placed in the NAND 0X200000. The
console input is
somehow inhibit. I cannot type anything on it until the
board
reboots .
You mean, you can not interactive with u-boot, am I
right?
The board is an AT91SAM9M10 custom board based on the
AT91SAM9M10G45-ek
development kit. It has only USB,
Serial(DBGU), DDR2 and NAND.
I have tried to remove the LCD code but
the linker says that printk is
missing.
Please remove LCD
related #defined in board configuration header, while
not remove the
code.
What the detail message for "printk is missing."
BTW,
Which version u-boot do you use?
Best Regards, Bo Shen
_______________________________________________
U-Boot mailing list
[hidden email] http://lists.denx.de/mailman/listinfo/u-boot [1]
If you reply to this email, your
message will be added to the discussion below: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [2]
To unsubscribe from AT91SAM9M10 Custom Board U-boot reboot after
Wrong Image Format, click here [3].
NAML [4]
Links: ------ [1] http://lists.denx.de/mailman/listinfo/u-boot [2] http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [3] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe... [4] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewe...
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi Marcio,
On 3/14/2013 20:23, marcio@netopen.com.br wrote:
Hi Bo Shen
I have used a SAMBA old version and I managed to write the Linux Kernel that can be recognized by U-boot but now it sends a message "Veritying Checksum ....: Bad Data CRC. It seems that U-Boot is only reading the first sector OK and the rest of the Kernel is being worngly read.
Bad Data CRC don't help. Because, many possible issue will cause this issue.
Consider you use 16bit NAND flash. Have you define CONFIG_SYS_NAND_DBW_16 in board configuration header?
BTW, which bootstrap version do you use? (As I suspect the bootstrap has enabled for supporting 16bit NAND, so it read u-boot OK)
Please provide the log information output from dbgu.
Thanks for your attention
Marcio
Best Regards, Bo Shen
Hi B.
Thanks for your attention!
Bad Data CRC don't help.
Because, many possible issue will cause this issue.
I will provide the log.
Consider you use 16bit NAND flash. Have you define
CONFIG_SYS_NAND_DBW_16 in board configuration header?
Yes I did that. Before I include this definition the board did not even try to boot the kernel.
BTW, which bootstrap version do you use? (As I
suspect the bootstrap has
enabled for supporting 16bit NAND, so it
read u-boot OK)
The At91bootstrap indeed loads U-boot OK. The problem is afterward.
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 MHz dram_init dram_init tam_ram=67108864 testa_ram_readonly: Inicio testa_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 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 00000000
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 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!
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi Marcio,
于 2013/3/16 2:46, marcio@netopen.com.br 写道:
Hi B.
Thanks for your attention!
Bad Data CRC don't help.
Because, many possible issue will cause this issue.
I will provide the log.
Consider you use 16bit NAND flash. Have you define
CONFIG_SYS_NAND_DBW_16 in board configuration header?
Yes I did that. Before I include this definition the board did not even try to boot the kernel.
BTW, which bootstrap version do you use? (As I
suspect the bootstrap has
enabled for supporting 16bit NAND, so it
read u-boot OK)
The At91bootstrap indeed loads U-boot OK. The problem is afterward.
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 MHz dram_init dram_init tam_ram=67108864 testa_ram_readonly: Inicio testa_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 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 00000000
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 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!
I see you read only 3MiB, however, the kernel size is 3.5 MiB (Data Size: 3630052 Bytes = 3.5 MiB). So, you only read partial kernel, this cause CRC error.
Best Regards, Bo Shen
Hi Bo
That is indeed the problem. I shrink the kernel to less than 3Mb and it works!
Thanks a lot Best regards Marico
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi Bo
Now I am getting a problem mounting the NAND file system. Do you have any idea?
Below is the log.
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: 3084960 Bytes = 2.9 MiB Load Address: 70008000 Entry Point: 70008000 Verifying Checksum ... OK kernel data at 0x70000040, len = 0x002f12a0 (3084960) Loading Kernel Image ... OK OK kernel loaded at 0x70008000, end = 0x702f92a0 images.os.start = 0x70000000, images.os.end = 0x702f12e0 images.os.load = 0x70008000, load_end = 0x702f92a0
Starting kernel ...
Uncompressing Linux... done, booting the kernel. Linux version 2.6.39.4 (root@marcio-VPCF135FB [1]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #425 PREEMPT Sat Mar 16 11:43:59 BRT 2013 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine: Atmel AT91SAM9M10G45-EK Ignoring tag cmdline (using the default kernel command line) Memory policy: ECC disabled, Data cache writeback Clocks: CPU 400 MHz, master 133 MHz, main 12.000 MHz Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: mem=64M@0x70000000 [2] console=ttyS0,115200 mtdparts=mtdparts=n and0:5M(Bootstrap),95M(system),-(userdata) mtdids=nand0=nand0 ubi.mtd=1 ubi.mtd= 2 rw root=ubi0:system rootfstype=ubifs init=/init gdb waitkgdb kgdboc=ttyS0,115 200 PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 58620k/58620k available, 6916k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xff200000 - 0xffe00000 ( 12 MB) vmalloc : 0xd0800000 - 0xfee00000 ( 742 MB) lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc024b000 (2316 kB) .text : 0xc024b000 - 0xc05e0a14 (3671 kB) .data : 0xc05e2000 - 0xc0601d60 ( 128 kB) Preemptable hierarchical RCU implementation. NR_IRQS:192 AT91: 160 gpio irqs in 5 banks Console: colour dummy device 80x30 console [ttyS0] enabled Calibrating delay loop... 197.12 BogoMIPS (lpj=98560) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 MARCIO: at91_add_device_isi end=C02453CC AT91: Power Management AT91: Starting after general reset bio: create slab at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c-gpio i2c-gpio.0: using pins 52 (SDA) and 53 (SCL) at_hdmac at_hdmac: Atmel AHB DMA Controller ( cpy slave ), 8 channels Switching to clocksource tcb_clksrc Switched to NOHz mode on CPU #0 NetWinder Floating Point Emulator V0.97 (double precision) hx170dec: dec/pp kernel module. $Revision: 1.9 $ hx170dec: supports 8170 and 8190 hardware hx170dec: base_port=0x00900000 irq=30 hx170dec: HW ID=0x81701250 hx170dec: Compatible HW found at 0x00900000 hx170dec: module inserted. Major = 253 memalloc: 8190 Linear Memory Allocator, $Revision: 1.1 $ memalloc: linear memory base = 0x24000000 memalloc: allocation method: 64M memalloc: 67108864 bytes (64MB) configured. Check RAM size! ashmem: initialized JFFS2 version 2.2. (NAND) (SUMMARY) Â(c) 2001-2006 Red Hat, Inc. msgmni has been set to 114 io scheduler noop registered (default) atmel_usart.0: ttyS0 at MMIO 0xfeffee00 (irq = 1) is a ATMEL_SERIAL atmel_usart.2: ttyS2 at MMIO 0xfff90000 (irq = 8) is a ATMEL_SERIAL kgdb: Registered I/O driver kgdboc. brd: module loaded loop: module loaded atmel_nand atmel_nand: No DMA support for NAND access. NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi t) Scanning device for bad blocks Bad eraseblock 40 at 0x000000500000 Bad eraseblock 41 at 0x000000520000 Bad eraseblock 800 at 0x000006400000 Bad eraseblock 801 at 0x000006420000 Creating 3 MTD partitions on "atmel_nand": 0x000000000000-0x000000500000 : "Bootstrap" 0x000000500000-0x000006400000 : "system" 0x000006400000-0x000010000000 : "userdata" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048 uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 2: 0, read 64 bytes uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 3: 0, read 64 bytes uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 4: 0, read 64 bytes uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 5: 0, read 64 bytes uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 6: 0, read 64 bytes uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error :
Links: ------ [1] mailto:root@marcio-VPCF135FB [2] mailto:mem=64M@0x70000000
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi Marcio, This is not u-boot related, I think you should post this issue to Linux kernel mailing list.
On 03/16/2013 10:58 PM, marcio@netopen.com.br wrote:
[Snip]
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi t) Scanning device for bad blocks Bad eraseblock 40 at 0x000000500000 Bad eraseblock 41 at 0x000000520000 Bad eraseblock 800 at 0x000006400000 Bad eraseblock 801 at 0x000006420000 Creating 3 MTD partitions on "atmel_nand": 0x000000000000-0x000000500000 : "Bootstrap" 0x000000500000-0x000006400000 : "system" 0x000006400000-0x000010000000 : "userdata" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 131072 bytes (128 KiB) UBI: logical eraseblock size: 129024 bytes UBI: smallest flash I/O unit: 2048 UBI: sub-page size: 512 UBI: VID header offset: 512 (aligned 512) UBI: data offset: 2048
I check the NAND flash spec and find you may use wrong parameters for generating UBIFS image.
--->8--- Page size x16: 1056 words (1024 + 32 words) ---<8---
and no sub-page.
So, I think mini I/O unit should be 1024 x 4 = 4096 Bytes
uncorrectable error : uncorrectable error : uncorrectable error : uncorrectable error : UBI error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 2: 0, read 64 bytes
This is ECC error, I think you should also update the driver for atmel_nand.c (mainly ECC layout)
Best Regards, Bo Shen
Hi Bo
Thanks a lot for your help.
Best regards
MArcio
On Sat, 16 Mar 2013 19:46:06 -0700 (PDT), Bo Shen [via U-Boot] wrote:
Hi Marcio,
This is not u-boot related, I think you should post this
issue to
Linux kernel mailing list.
On 03/16/2013 10:58 PM,
[hidden email] wrote:
[Snip]
NAND device: Manufacturer ID:
0x2c, Chip
ID: 0xba (Micron NAND 256MiB 1,8V 16-bi t)
Scanning device for bad
blocks Bad eraseblock 40 at
0x000000500000
Bad eraseblock 41 at 0x000000520000 Bad
eraseblock 800 at 0x000006400000
Bad eraseblock 801 at
0x000006420000
Creating 3 MTD partitions on "atmel_nand":
0x000000000000-0x000000500000 :
"Bootstrap"
0x000000500000-0x000006400000 :
"system"
0x000006400000-0x000010000000 : "userdata"
UBI: attaching mtd1
to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI:
logical eraseblock size: 129024 bytes UBI: smallest flash
I/O unit:
2048 UBI: sub-page size: 512 UBI: VID header
offset: 512 (aligned
UBI: data offset: 2048
I check the
NAND flash spec and find you may use wrong
parameters for generating
UBIFS image.
--->8--- Page size x16: 1056 words (1024 + 32
words)
and no sub-page.
So, I think mini I/O unit should
be 1024 x 4 = 4096 Bytes
uncorrectable error : uncorrectable
error
: uncorrectable error : uncorrectable error : UBI
error: ubi_io_read:
error -74 (ECC error) while reading 64 bytes
from PEB 2:
0, read 64 bytes
This is ECC error, I think
you should also update
the driver for atmel_nand.c (mainly ECC
layout)
Best Regards, Bo Shen
_______________________________________________
U-Boot mailing list
[hidden email] http://lists.denx.de/mailman/listinfo/u-boot [1]
If you reply to this email, your
message will be added to the discussion below: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [2]
To unsubscribe from AT91SAM9M10 Custom Board U-boot reboot after
Wrong Image Format, click here [3].
NAML [4]
Links: ------ [1] http://lists.denx.de/mailman/listinfo/u-boot [2] http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [3] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe... [4] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewe...
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
Hi B
I would like to mention that I run U-boot either via the code located in flash(using at91bootstrap) or directly in the DDRAM via Eclipse/GDB/JTAG(Jflash).
Thanks
Marcio
On Thu, 14 Mar 2013 19:31:39 -0700 (PDT), Bo Shen-3 [via U-Boot] wrote:
Hi Marcio,
On 3/14/2013 20:23, [hidden email] wrote:
Hi Bo Shen
I
have used a SAMBA old version and I managed to write
the Linux
Kernel that can be recognized by U-boot but now it sends a
message
"Veritying Checksum ....: Bad Data CRC. It seems that U-Boot is
only
reading the first sector OK and the rest of the Kernel is being
worngly read.
Bad Data CRC don't help. Because, many possible
issue will cause this issue.
Consider you use 16bit NAND flash.
Have you define
CONFIG_SYS_NAND_DBW_16 in board configuration header?
BTW, which bootstrap version do you use? (As I suspect the
bootstrap has
enabled for supporting 16bit NAND, so it read u-boot
OK)
Please provide the log information output from dbgu.
Thanks for your attention
Marcio
Best Regards, Bo
Shen
U-Boot
mailing list
[hidden email]
http://lists.denx.de/mailman/listinfo/u-boot [1]
-------------------------
If you reply to this email, your message
will be added to the discussion below: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [2]
To unsubscribe from AT91SAM9M10 Custom Board U-boot reboot after
Wrong Image Format, click here [3].
NAML [4]
Links: ------ [1] http://lists.denx.de/mailman/listinfo/u-boot [2] http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... [3] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe... [4] http://u-boot.10912.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewe...
-- View this message in context: http://u-boot.10912.n7.nabble.com/AT91SAM9M10-Custom-Board-U-boot-reboot-aft... Sent from the U-Boot mailing list archive at Nabble.com.
participants (3)
-
Bo Shen -
Bo Shen -
marcio＠netopen.com.br