I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?
Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way?
Or am I just dumb and these are actually still the eMMC?
(10-25-2019, 07:59 AM)tsago Wrote: I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?
Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way?
Or am I just dumb and these are actually still the eMMC?
Partitions on the eMMC?
I know when I used the "Disks" program in Debian (that I added to OEM OS on the PBP), I saw the partitioning on what "Disks" refered to as an SD, which the eMMC....
That help? :-)
10-25-2019, 01:41 PM (This post was last modified: 10-25-2019, 02:34 PM by tsago.
Edit Reason: added one more ref
)
(10-25-2019, 08:16 AM)rick1959 Wrote:
(10-25-2019, 07:59 AM)tsago Wrote: I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?
Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way?
Or am I just dumb and these are actually still the eMMC?
Partitions on the eMMC?
I know when I used the "Disks" program in Debian (that I added to OEM OS on the PBP), I saw the partitioning on what "Disks" refered to as an SD, which the eMMC....
That help? :-)
Well I thought so too, but if those are partitions on the eMMC, shouldn't they visually show as a part of the "mmcblk1" device? (pic attached)
fdisk -l /dev/mmcblk1 also doesn't list them as partitions belonging to it.
Alright, mystery solved!
Basically those are some special-cookie "partitions", intended by the eMMC spec for boot firmwares (boot0, boot1), and secure data (rpmb).
Then there's the normal "USER" partition(~block-device), which is used for normal partitioning (= mmcblk0/1[p1/2/3..]).
(10-25-2019, 07:59 AM)tsago Wrote: I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?
Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way?
Or am I just dumb and these are actually still the eMMC?
Partitions on the eMMC?
I know when I used the "Disks" program in Debian (that I added to OEM OS on the PBP), I saw the partitioning on what "Disks" refered to as an SD, which the eMMC....
That help? :-)
Well I thought so too, but if those are partitions on the eMMC, shouldn't they visually show as a part of the "mmcblk1" device? (pic attached)
fdisk -l /dev/mmcblk1 also doesn't list them as partitions belonging to it.
Alright, mystery solved!
Basically those are some special-cookie "partitions", intended by the eMMC spec for boot firmwares (boot0, boot1), and secure data (rpmb).
Then there's the normal "USER" partition(~block-device), which is used for normal partitioning (= mmcblk0/1[p1/2/3..]).
(10-25-2019, 07:59 AM)tsago Wrote: I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?
Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way?
Or am I just dumb and these are actually still the eMMC?
Partitions on the eMMC?
I know when I used the "Disks" program in Debian (that I added to OEM OS on the PBP), I saw the partitioning on what "Disks" refered to as an SD, which the eMMC....
That help? :-)
Well I thought so too, but if those are partitions on the eMMC, shouldn't they visually show as a part of the "mmcblk1" device? (pic attached)
fdisk -l /dev/mmcblk1 also doesn't list them as partitions belonging to it.
Alright, mystery solved!
Basically those are some special-cookie "partitions", intended by the eMMC spec for boot firmwares (boot0, boot1), and secure data (rpmb).
Then there's the normal "USER" partition(~block-device), which is used for normal partitioning (= mmcblk0/1[p1/2/3..]).
I've added a little detail to the Pinebook Pro Wiki on the subject on eMMC partitions. Feel free to either send me corrections / updates, or make them yourself. Here is the link;
10-27-2019, 05:37 AM (This post was last modified: 10-27-2019, 05:38 AM by z4v4l.)
eMMC boot partitions, it's better to call them "areas" to avoid confusion, are good candidates for uboot or other FW storage. would be if Rockchip ROM code did understand them. but it probably doesn't. at least rk3399 manual doesn't mention them. would be interesting to experiment. with Rockpro. they were intended for such usage, they free general purpose area for user and they provide redundancy (since they always come in two identical instances).
I changed the "0" / zero to "1" / one so it matches the other lines.
Then added a line that the device number may vary depending on the kernel.
My home media server has similar naming for the SD card. Though in my case, leaves out the extra 3 eMMC specific non-user areas.
It also never changes device number, but that's probably due to the lack of other card device interfaces.
Do we know the device naming of the SD card in the Pinebook Pro?
lsblk devices
