From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] question regarding the odroidc2 board support
Date: Tue, 27 Jun 2017 09:57:21 +0200 [thread overview]
Message-ID: <20170627095721.344addfd@jawa> (raw)
In-Reply-To: <trinity-1fd6791b-6aef-4849-b5fc-01df289e5359-1498154121662@3capp-mailcom-bs15>
On Thu, 22 Jun 2017 19:55:21 +0200
daggs <daggs@gmx.com> wrote:
> Greetings,
>
> I'm using buildroot to generate images for the odroid c2 boards and
> from what I see, it uses u-boot.bin to burn into the image. I'm not
> seeing any other uboot product that is used for booting (unless I'm
> mistaken). I'm reading the odroid c2 readme file and I see it
> instructs the use to burn a alternative u-boot.bin from the one that
> was created by the env. I wonder how it is possible to actually use
> newer uboot when in the end uboot recommends to replace u-boot.bin
> with pre existing one?
From the spec I do see that C2 has SD card and eMMC.
I can only share my experience with Odroid XU3/U3.
The boot process would (probably) require some signed blobs from
hardkernel (those binaries are corresponding to u-boot-spl.bin).
I can recommend looking to Hardkernel forum (they should have some
topics dedicated for this SoM), or look for tizen.org wiki:
https://wiki.tizen.org/Quick_guide_for_odroidxu3
I hope, that the boot flow is similar for XU3 and C2.
>
> Thanks,
>
> Dagg.
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
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
next prev parent reply other threads:[~2017-06-27 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 17:55 [U-Boot] question regarding the odroidc2 board support daggs
2017-06-27 7:57 ` Lukasz Majewski [this message]
2017-06-27 11:58 ` daggs
2017-06-27 13:12 ` Lukasz Majewski
2017-06-28 8:44 ` daggs
2017-06-28 9:12 ` Lukasz Majewski
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=20170627095721.344addfd@jawa \
--to=lukma@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