From: Ziyuan <xzy.xu@rock-chips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] accessing eMMC boot partitions from U-Boot
Date: Tue, 14 Mar 2017 18:14:20 +0800 [thread overview]
Message-ID: <58C7C27C.4000100@rock-chips.com> (raw)
In-Reply-To: <0328feca-f840-7eaa-ed10-9173f843914d@wwwdotorg.org>
hi Stephen,
On 03/14/2017 12:41 PM, Stephen Warren wrote:
> On 03/13/2017 06:54 PM, Ziyuan wrote:
>> hi Stephen,
>>
>> On 03/14/2017 05:49 AM, Stephen Warren wrote:
>>> On 03/13/2017 03:34 PM, Tim Harvey wrote:
>>>> Greetings,
>>>>
>>>> I'm working with some boards with eMMC FLASH and understand that I can
>>>> set the fields of the PARTITION_CONFIG with the 'mmc partconf' command
>>>> to specify what partition is used for boot. Once I do that to set the
>>>> boot0 partition for example, how can I access that partition from
>>>> within u-boot via mmc read/write? In Linux the kernel provides access
>>>> to user/boot0/boot1/rpmb via different devices, but I don't see u-boot
>>>> doing that.
>>>
>>> The "mmc dev" command can be used to select which MMC device to
>>> operate on. The "typical" command "mmc dev 0" selects the main
>>> partition on MMC device 0 for later MMC-specific commands such as "mmc
>>> read". You can add an extra parameter to that command to request a
>>> specific HW partition, e.g. "mmc dev 0 1" selects boo0 of MMC device 0
>>> and "mmc dev 0 2" selects boot1.
>>
>> The 4th of "mmc dev 0 1" is the *software* partition index, not the hw
>> partition index. AKA eMMC has four partitions: user
>> data/boot0/boot1/rpmb, I think Tim wanna to boot from other partition,
>> like boot0, right?
>
> The fourth parameter is the HW partition number. See how cmd/mmc.c's
> do_mmc_dev() passes this value to blk_select_hwpart_devnum(), then to
> blk_select_hwpart().
Thanks, it's my fault.
>
>
>
next prev parent reply other threads:[~2017-03-14 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 21:34 [U-Boot] accessing eMMC boot partitions from U-Boot Tim Harvey
2017-03-13 21:40 ` Fabio Estevam
2017-03-13 21:49 ` Stephen Warren
2017-03-14 0:54 ` Ziyuan
2017-03-14 4:41 ` Stephen Warren
2017-03-14 10:14 ` Ziyuan [this message]
2017-03-14 1:08 ` Sergey Kubushyn
2017-03-14 4:44 ` Stephen Warren
2017-03-14 5:11 ` Jaehoon Chung
2017-03-14 6:19 ` Sergey Kubushyn
2017-03-14 13:07 ` Tim Harvey
2017-03-14 15:44 ` Stephen Warren
2017-03-14 12:55 ` Tim Harvey
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=58C7C27C.4000100@rock-chips.com \
--to=xzy.xu@rock-chips.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 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.