From: ansaris <ansaris@iwavesystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX6 - u-boot binary size getting changed
Date: Wed, 14 Jan 2015 17:01:59 +0530 [thread overview]
Message-ID: <54B653AF.7000501@iwavesystems.com> (raw)
Hi,
We are using imx6Q sabresd platform for our development with Linux
3.10.17_1.0.0-GA BSP.
We have installed the meta-tool chain in our 64bit Host PC and 32 bit
Host PC using below steps.
$bitbake meta-toolchain
$sudo sh tmp/deploy/sdk/poky-eglibc-x86_64-arm-toolchain-<version>.sh
The u-boot source code is compiled in 32bit host PC and with this
u-boot.imx binary, the target board is booted.
At u-boot level, the command "bdinfo" displays below information.
arch_number = 0x0000112D
boot_params = 0x10000100
DRAM bank = 0x00000000
-> start = 0x10000000
-> size = 0x40000000
eth0name = FEC
ethaddr = 00:01:02:03:04:05
current eth = FEC
ip_addr = <NULL>
baudrate = 115200 bps
TLB addr = 0x4FFF0000
relocaddr = 0x4FF68000
reloc off = 0x38768000
irq_sp = 0x4F565F38
sp start = 0x4F565F28
Then the u-boot source code is compiled in 64bit host PC and with this
u-boot.imx binary, the target board is booted.
At u-boot level, the command "bdinfo" displays below information.
arch_number = 0x0000112D
boot_params = 0x10000100
DRAM bank = 0x00000000
-> start = 0x10000000
-> size = 0x40000000
eth0name = FEC
ethaddr = 00:01:02:03:04:05
current eth = FEC
ip_addr = <NULL>
baudrate = 115200 bps
TLB addr = 0x4FFF0000
relocaddr = 0x4FF66000
reloc off = 0x38766000
irq_sp = 0x4F563F38
sp start = 0x4F563F28
We would like to know, why the "relocaddr & reloc off "(as highlighted
above) are different? since the source codes are same and compiled in
different host PC (64bit & 32bit).
In addition, we checked the u-boot.imx binary file size. We could see
the difference in the file size as below
u-boot.imx(compiled in 32bit host PC) - 313644 bytes
u-boot.imx(compiled in 64bit host PC) - 318780 bytes
Thank You,
Regards,
Ansari
reply other threads:[~2015-01-14 11:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54B653AF.7000501@iwavesystems.com \
--to=ansaris@iwavesystems.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