From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07
Date: Wed, 04 Sep 2013 00:45:27 +0200 [thread overview]
Message-ID: <20130903224528.02CB1380DDB@gemini.denx.de> (raw)
In-Reply-To: <002b01cea8e7$b14fc5b0$13ef5110$@amanomcgann.com>
Dear Chuck,
In message <002b01cea8e7$b14fc5b0$13ef5110$@amanomcgann.com> you wrote:
>
> I found if I used tftp these files transferred correctly and the board would
> boot with the new files. I thought the solution was found and I could
> simply setup the same files using USB through environment variables. The
> script worked but the problem was when it tried to load rootfs into RAM it
> would cause a CPU reset and RomBOOT to start. At first I thought there was
> something wrong with the script so I tried to load the file by typing it the
> command but got the same result.
Are you using the same load address in RAM with both the tftp and the
fatload commands? Can you provide a complete console log of both the
working and the crashing cases?
> Command:
>
> usb start
>
> fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same
> address used by tftp.
Please show the complete commands, and all output.
> My first question is, is there a solution for this issue using U-Boot
> 2009.11.1? This version builds currently within our project.
We need to understand the problem beforeanybody could answer that...
> Second question is I downloaded U-Boot 2013.07 but noticed huge change in
> the build process. I figured out the patches I need along with the AT91
> configuration for our board. We are using the arm926ej6 processor with a
> board similar to at91sam9260ek. When I try to build I get the
> hardware.h:49:3 error: #error "Unsupported AT91 processor" message. When I
> look at the header file I see where it fails but I don't understand why
> since I do have a matching define. For some reason hardware.h is not seeing
> this define and I am stumped as to why. So any suggestions on how to solve
> or figure this out would be appreciated.
Well, 2009.11 is indeed extremely old. With such an out-of-tree port
you are essentially lost. Adapting the old patches to current
mainline is more or less the same effort as starting from scratch (and
probably even more so).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Crash programs fail because they are based on the theory that, with
nine women pregnant, you can get a baby a month. - Wernher von Braun
next prev parent reply other threads:[~2013-09-03 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 20:53 [U-Boot] U-Boot 2009.11.1 USB Issue and Building U-Boot 2013.07 Chuck Wical
2013-09-03 22:45 ` Wolfgang Denk [this message]
[not found] ` <005001cea968$9eaa58e0$dbff0aa0$@amanomcgann.com>
2013-09-04 15:36 ` Wolfgang Denk
2013-09-04 16:23 ` Chuck Wical
2013-09-04 9:37 ` Jens Scharsig
2013-09-05 10:09 ` Andreas Bießmann
2013-09-05 19:39 ` Chuck Wical
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=20130903224528.02CB1380DDB@gemini.denx.de \
--to=wd@denx.de \
--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