From: Dana Goyette <dgoyette@calpoly.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Weird issues with u-boot on Microblaze
Date: Wed, 19 Aug 2009 16:21:25 -0700 [thread overview]
Message-ID: <h6i1dm$ipa$1@ger.gmane.org> (raw)
I've been trying to bring up a vanilla kernel on an XUPV5-LX110T board,
and have been having all sorts of odd issues with U-Boot. For example,
if I try to enable FIT image support (as noted on
http://www.monstr.eu/wiki/doku.php?id=uboot:uboot ), I get
CONFIG_BOOTMAPSZ undefined. I've also had to edit image.h to get the
thing to compile.
image.c: In function ?boot_get_fdt?:
image.c:1510: error: ?bootm_headers_t? has no member named ?fit_hdr_fdt?
image.c:1511: error: ?bootm_headers_t? has no member named ?fit_uname_fdt?
image.c:1512: error: ?bootm_headers_t? has no member named ?fit_noffset_fdt?
the fix: edit image.h (line 221):
#if defined(CONFIG_OF_LIBFDT) /* WAS: CONFIG_PPC */
If I fix that and try to load a FIT image with a kernel and device-tree,
the bootm command completely ignores the device tree; unfortunately, I
don't have a log of this on hand, because now even image loading has
broken somehow. For example, fatls ace 0 gives " 131074 \x02.\x02 ", and
attempting DHCP boot results in a spew of "ARP Retry count exceeded;
starting again" -- retry count exceeded, despite it never having tried
even once?
I've attached a log of the console output under both conditions, as well
as the config.mk and xparameters.h under microblaze_generic; for some
reason, the given U-Boot BSP assumes 100MHz, despite the board using
125MHz. Does anyone have advice for getting u-boot to work on this board?
Thanks in advance for any help.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot.log
Type: text/x-log
Size: 3326 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090819/20625d47/attachment.bin
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config.mk
Url: http://lists.denx.de/pipermail/u-boot/attachments/20090819/20625d47/attachment.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xparameters.h
Type: text/x-chdr
Size: 2333 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090819/20625d47/attachment.h
-------------- next part --------------
A non-text attachment was scrubbed...
Name: microblaze-generic.h
Type: text/x-chdr
Size: 9385 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090819/20625d47/attachment-0001.h
next reply other threads:[~2009-08-19 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 23:21 Dana Goyette [this message]
2009-08-20 8:15 ` [U-Boot] Weird issues with u-boot on Microblaze Michal Simek
2009-08-20 17:22 ` Dana Goyette
2009-08-20 20:57 ` Michal Simek
2009-08-24 18:53 ` Dana Goyette
2009-08-24 22:04 ` Michal Simek
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='h6i1dm$ipa$1@ger.gmane.org' \
--to=dgoyette@calpoly.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.