public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chuck Wical <chuck.wical@amanomcgann.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB fatload fails to load rootfs
Date: Thu, 29 Aug 2013 13:32:10 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130829T152512-710@post.gmane.org> (raw)
In-Reply-To: kvmuf4$l6v$1@ger.gmane.org

Romain Izard <romain.izard.pro <at> gmail.com> writes:

> 
> On 2013-08-28, Chuck Wical <chuck.wical <at> amanomcgann.com> wrote:
> > I am trying to load rootfs.ext2.gz.uboot from usb using fatload but
> > when it reaches a point in writing the file to memory a reset occurs
> > of the CPU.  If I load this file using tftp it works fine.  Here are
> > the commands I am using:
> >
> > loadaddr=0x21000000
> >
> > tftp $(loadaddr) rootfs.ext2.gz.uboot
> >
> > usb start fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot
> >
> > The version of U-Boot used is 2009.11.1 and upgrading at this point
> > may be an issue.  Before a bunch of questions are asked I inherited
> > this project, it is mature and works, I have no documentation, and I
> > am simply trying to copy a file from usb to memory.  Nothing more,
> > nothing fancy.
> >
> > My searches on the web have not yielded any possible solutions or good
> > explanations of the usb subsystem in U-Boot so I am hoping someone can
> > provide some possible solutions or information I can read.
> >
> The FAT reading code in old versions of U-Boot is quite sensitive to
> external conditions. In my experience, changing the compiler for a
> source tree based on the 2007 U-Boot code from GCC 4.3.3 to GCC 4.7.3
> produced the same issue as the one you described. Surprisingly, the
> issue only occurred for the rootfs, and not the kernel, which was a
> smaller file.
> 
> Unfortunately for you, our answer to this issue was the finalization of
> the porting of our platform to the U-Boot mainline, which does not has
> those problems.
> 
> Best regards,


Thank you Roman for the response.  You stated exactly what I am seeing, it
is only the rootfs file that fails while the uImage and etc.jffs2 files copy
and write to nand with no problem.

You will have to forgive my lack of knowledge on U-Boot since I have only
been working on this specific task that involves U-Boot for about a week now
so I have been on a steep learning curve.  You mentioned U-Boot mainline not
having this issue.  Could you direct me to where I can find this so I can
take a look?

My concern is the cross-compiler that was created by a third party may not
be compatible with newer versions of U-Boot and I would need to go through
the patches to see if there was anything custom created.  As you probably
understand this is time consuming work, especially with the learning curve I
am on.  

Again many thanks for the response!

Chuck

  reply	other threads:[~2013-08-29 13:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 18:58 [U-Boot] USB fatload fails to load rootfs Chuck Wical
2013-08-29  7:49 ` Romain Izard
2013-08-29 13:32   ` Chuck Wical [this message]
2013-08-29 13:50     ` Stefano Babic

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=loom.20130829T152512-710@post.gmane.org \
    --to=chuck.wical@amanomcgann.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