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] wrot
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, mar...@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 erasebl
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
0x20, size 0x30
3145728 bytes read: OK
* kernel: cmdline image
address = 0x7000
## Booting kernel from Legacy Image at 7000
...
Image Name:
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-after-Wrong-Image-Format-tp149567p149875.html
Sent from the U-Boot ma
Hi Marcio,
于 2013/3/16 2:46, mar...@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 configuratio
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,
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 defin
Hi Marcio,
On 3/14/2013 20:23, mar...@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 sect
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.
T
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 Forma
Hello,
On 3/13/2013 20:26, mar...@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 0X20. The
console input is somehow inhibit. I canno
Hi
Our board reboots after send Wrong Image Format message to the console and
hangs. The Linux uImage is correctly placed in the NAND 0X20. 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 AT91SA
12 matches
Mail list logo
