From: Dana Goyette <dgoyette@calpoly.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Weird issues with u-boot on Microblaze
Date: Mon, 24 Aug 2009 11:53:29 -0700 [thread overview]
Message-ID: <4A92E1A9.3050200@calpoly.edu> (raw)
In-Reply-To: <4A8DB8B6.5030206@monstr.eu>
Michal Simek wrote:
>
> this code can't be compiled - you have bad setting. MONITOR_BASE is always on lower address then
> FLASH address. Check that your ram on lower address than your flash - this is check by u-boot.bsp too.
>
>
>
> Regards,
> Michal
>
>
>
>
>
Thanks for that help, and thanks for updating your git repository. I
had previously forgotten about the "flash must be above RAM" limitation.
I had forgotten, and had rebuilt the project without re-running the BSP,
after making the mistake of doing "generate addresses".
I've now rebuild the project and BSP with RAM at 0x10000000 and Flash at
0x20000000, but I'm now getting a linking error:
u-boot-microblaze/net/eth.c:202: relocation truncated to fit:
R_MICROBLAZE_32_PCREL_LO against symbol `board_eth_init' defined in text
section in
board/xilinx/microblaze-generic/libmicroblaze-generic.a(microblaze-generic.o)
I've looked up the error, and about the closest thing I could find was
this -- something about "longcall" attribute:
http://www.mail-archive.com/u-boot at lists.denx.de/msg04518.html
http://fixunix.com/vxworks/48336-how-solve-error-relocation-truncated-fit-r_arm_pc24.html
In Microblaze, do the absolute address values matter, or just the
relative positioning?
I also imagine that perhaps the CompactFlash issues originated from the
incorrect clock rate.
Thanks again for the help.
next prev parent reply other threads:[~2009-08-24 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 23:21 [U-Boot] Weird issues with u-boot on Microblaze Dana Goyette
2009-08-20 8:15 ` Michal Simek
2009-08-20 17:22 ` Dana Goyette
2009-08-20 20:57 ` Michal Simek
2009-08-24 18:53 ` Dana Goyette [this message]
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=4A92E1A9.3050200@calpoly.edu \
--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.