From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help about a simplified bootloader.
Date: Fri, 3 Apr 2009 13:57:55 +0200 [thread overview]
Message-ID: <20090403115755.GC14955@game.jcrosoft.org> (raw)
In-Reply-To: <34f262ce0904022344u6e27ad07g8263785dd36acb58@mail.gmail.com>
On 14:44 Fri 03 Apr , os user wrote:
> Hi all,
>
> I want to boot linux by a simplified bootloader. I use Atmel's ARM
> chip (AT91SAM9RL64EK board). Now, I can boot linux with my small
> program. The small program will parse the image generaed by "mkimage"
> and copy the kernel bianry from NAND flash to SDRAM, construct the tag
> list, disable I/D cache, disable interrupt and then jump to kernel
> entry point. The system can startup, but when accessing rootfile
> system(the rootfile system was also in the NAND chip), a lot of CRC
> errors were found. See below,
> mtd->read(0x1fb2c bytes from 0x1804d4) returned ECC error
> mtd->read(0x1fa38 bytes from 0x3e05c8) returned ECC error
> mtd->read(0x1f7dc bytes from 0x7c0824) returned ECC error
> jffs2_scan_inode_node(): CRC failed on node at 0x007c37a4: Read
> 0xd9b2bc33, calculated 0xda4805c1
>
> and sometimes the sytem even crashed when R/W filesystem.
>
> But with the same linux kernel and rootfile system, if I use U-Boot to
> boot linux, everything seems OK.
>
> Can anyone tell is there any trick that's related with linux NAND
> driver in U-Boot? Or any suggestion to help me moving on?
use U-Boot or Atmel Bootstrap
Best Regards,
J.
next prev parent reply other threads:[~2009-04-03 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 6:44 [U-Boot] Help about a simplified bootloader os user
2009-04-03 11:57 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-04-07 5:30 ` os user
2009-04-03 16:53 ` Scott Wood
2009-04-07 5:32 ` os user
2009-04-08 6:42 ` Shankar Ganesh
2009-04-08 7:12 ` os user
2009-04-03 17:51 ` Wolfgang Denk
2009-04-07 5:31 ` os user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090403115755.GC14955@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox