From: Derald D. Woods <woods.technical@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: am3517_evm: SD/MMC boot with uEnv.txt, zImage, and FDT
Date: Mon, 15 Feb 2016 16:54:53 -0600 [thread overview]
Message-ID: <56C2573D.4040703@gmail.com> (raw)
In-Reply-To: <20160208204533.GO25786@bill-the-cat>
On 02/08/2016 02:45 PM, Tom Rini wrote:
> On Sun, Feb 07, 2016 at 08:54:47PM -0600, Derald D. Woods wrote:
>
>> Boot with the Linux zImage and am3517-evm.dtb pair, when SD/MMC media
>> is present. This behavior can be overridden by creating a 'uEnv.txt'
>> file with 'uenvcmd' defined.
>>
>> To boot an existing 'uImage', create the following 'uEnv.txt':
>>
>> [start]-----------------------------------------------------------------
>>
>> loaduimage=fatload mmc 0:1 ${loadaddr} ${bootfile}
>> uenvcmd=run loaduimage; run mmcargs; bootm ${loadaddr}
>>
>> [end]-------------------------------------------------------------------
>>
>> Inspired by similar patches, for other OMAP3 boards, from EEWiki
>> - https://github.com/eewiki/u-boot-patches/tree/master/v2016.01
>>
>> Signed-off-by: Derald D. Woods <woods.technical@gmail.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
>
Gentle nudge.
I know that there is not much support for this board and its variants.
That being said, one can still buy the SOM's at Digi-Key and other
outlets. The Zoom AM3517 eXperimenter, which I have, is still a decent
platform for development. So for those who may still care, it would be
good to keep this updated.
Derald
next prev parent reply other threads:[~2016-02-15 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 2:54 [U-Boot] [PATCH] OMAP3: am3517_evm: SD/MMC boot with uEnv.txt, zImage, and FDT Derald D. Woods
2016-02-08 20:45 ` Tom Rini
2016-02-15 22:54 ` Derald D. Woods [this message]
2016-02-15 23:03 ` Derald D. Woods
2016-02-15 22:34 ` [U-Boot] " Tom Rini
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=56C2573D.4040703@gmail.com \
--to=woods.technical@gmail.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