From: Shawn Guo <shawnguo@kernel.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Mainline u-boot installation on Odroid-UX4
Date: Thu, 7 Apr 2016 17:35:34 +0800 [thread overview]
Message-ID: <20160407093534.GC4022@tiger> (raw)
Hi Przemyslaw, Anand,
I just got a Odroid-UX4 board to play. I installed firmware (bl1, bl2,
tzsw, u-boot) from hardkernel using sd_fusing.sh, and the board boots
fine. But when I install mainline u-boot v2016.03 by following
doc/README.odroid, the board refuses to boot with nothing appearing on
serial console.
Here is what I did:
- make odroid-xu3_defconfig
- make (using arm-linux-gnueabi-gcc 4.7.3)
- copy u-boot.bin (which is same as u-boot-dtb.bin in v2016.03 release)
to sd_fuse/hardkernel folder, and modify sd_fusing.sh to get it point
to this new U-Boot
- ./sd_fusing.sh /dev/sdX to flash the SD card
One thing I'm not sure is the offset that firmware should be installed
to SD card. The doc/README.odroid and hardkernel sd_fusing.sh tells
different ones.
doc/README.odroid:
-------------------------------------
| Binary | Block offset| part type |
| name | SD | eMMC |(eMMC only)|
-------------------------------------
| Bl1 | 1 | 0 | 1 (boot) |
| Bl2 | 31 | 30 | 1 (boot) |
| U-Boot | 63 | 62 | 1 (boot) |
| Tzsw | 2111 | 2110 | 1 (boot) |
| Uboot Env | 2560 | 2560 | 0 (user) |
-------------------------------------
sd_fusing.sh:
signed_bl1_position=1
bl2_position=31
uboot_position=63
tzsw_position=719
env_position=1231
I tried both sets, and neither works for me.
I know Odroid-UX4 is supported by mainline U-Boot today, so there must
be something missing from my setup. Could you please help me here?
Thanks.
Shawn
next reply other threads:[~2016-04-07 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 9:35 Shawn Guo [this message]
2016-04-07 10:20 ` [U-Boot] Mainline u-boot installation on Odroid-UX4 Przemyslaw Marczak
2016-04-07 13:57 ` Anand Moon
2016-04-07 13:59 ` Shawn Guo
2016-04-07 14:23 ` Przemyslaw Marczak
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=20160407093534.GC4022@tiger \
--to=shawnguo@kernel.org \
--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