From: Andreas Naumann <dev@andin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] fatload from eMMC general purpose partition
Date: Mon, 28 Jul 2014 16:35:25 +0200 [thread overview]
Message-ID: <53D65FAD.9070205@andin.de> (raw)
In-Reply-To: <20140728143840.5e721a39@amdc2363>
Hi,
>
> Could you share exact output from your console?
>
below follows some linux console output from writing some file to a gp-
and a user data partion (foo/bar). After that trying to see that file
from U-Boot...:
[root]# ls /dev/mmcblk3*
/dev/mmcblk3
/dev/mmcblk3boot1
/dev/mmcblk3gp0p1
/dev/mmcblk3p1
/dev/mmcblk3rpmb
/dev/mmcblk3boot0
/dev/mmcblk3gp0
/dev/mmcblk3gp1
Rest of User Data Area
mount /dev/mmcblk3p1 /media/usb0/
touch /media/usb0/foo
umount /media/usb0/
General purpose patition
[root]# mount /dev/mmcblk3gp0p1 /media/usb0/
[root]# touch /media/usb0/bar
[root]# umount /media/usb0/
Start u-boot
Rest of User Data Area
U-Boot =>fatls mmc 2:1 /
0 foo
1 file(s), 0 dir(s)
U-Boot =>fatls mmc 2:2 /
** Invalid partition 2 **
U-Boot =>fatls mmc 2:3 /
** Invalid partition 3 **
U-Boot =>fatls mmc 2:4 /
** Invalid partition 4 **
U-Boot =>fatls mmc 2:5 /
** Invalid partition 5 **
U-Boot =>fatls mmc 2:6 /
** Invalid partition 6 **
U-Boot =>fatls mmc 2:7 /
** Invalid partition 7 **
U-Boot =>fatls mmc 2:8 /
** Invalid partition 8 **
U-Boot =>fatls mmc 2:9 /
** Invalid partition 9 **
U-Boot =>fatls mmc 2:a /
** Invalid partition 10 **
U-Boot =>fatls mmc 2:b /
** Invalid partition 11 **
U-Boot =>fatls mmc 2:c /
** Invalid partition 12 **
U-Boot =>fatls mmc 2:d /
** Invalid partition 13 **
U-Boot =>fatls mmc 2:e /
** Invalid partition 14 **
U-Boot =>fatls mmc 2:f /
** Invalid partition 15 **
Where to find bar ?
regards,
Andreas
next prev parent reply other threads:[~2014-07-28 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 11:38 [U-Boot] fatload from eMMC general purpose partition Andreas Naumann
2014-07-28 12:38 ` Lukasz Majewski
2014-07-28 14:35 ` Andreas Naumann [this message]
2015-04-24 15:58 ` harsha kiran
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=53D65FAD.9070205@andin.de \
--to=dev@andin.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