07:37 <Stalevar> Hi. So can you give me any hints? I have a device with eMMC, it has partitions mmcblk0boot0 and mmcblk0boot1 2M each, then it has regular DOS partition table and three partitions, first one contains boot.scr, uimage and initrd. boot0 has U-Boot, boot1 has fat filesystem with files named FA, NVS and SMT. The main MMC has U-Boot executable between the MBR and first partition (4M of space). So how do I tell which U-Boot is loaded, from main eMMC or from

07:37 <Stalevar> boot0? I don't have UART access

07:38 <Stalevar> /proc/cpuinfo said Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board

07:38 <Xogium> you can't easily do that, since the boot rom is what loads that

07:39 <Stalevar> I know that this board is supposed to boot from USB too, but USB creation tool is lost on dead manufacturer site beyond recovery it seems (but PDF on how to use it is available)

07:39 <Xogium> however most sane boot roms that do eMMC booting do expect boot0 and boot1 hardware partitions, so it is extremely unlikely otherwise

07:39 <Stalevar> How do boot0 and boot1 work normally?

07:39 <Stalevar> They are like three SD cards in one chip?

07:40 <Stalevar> mmcblk0, mmcblk0boot0 and 1?

07:40 <Xogium> no they are actual hardware partitions

07:40 <Stalevar> So like virtual extra storage?

07:40 <Stalevar> Can boot partitions be created on regular SD card?

07:40 <Stalevar> or they are hardcoded

07:41 <Xogium> specific regions of the eMMC that are meant to store bootloaders, and your boot rom knows where to look to load them. They also have pseudo single cell layer flash emulation rather than the typical mlc flash of the rest of the eMMC storage

07:41 <Xogium> they are specific to eMMC

07:42 <Xogium> eMMC resemble sd, but up to a point, they both differ

07:43 <Xogium> eMMC has various things that sd lacks, such as health status / indications since I think 4.5 of the standard, or was it 5.0 ? And a concept that the sd also lacks is hardware partitions

07:43 <Xogium> the chip itself is aware of those different partitions and how to treat them

07:46 <Xogium> https://www.pengutronix.de/en/blog/2020-10-15-anpassen-einer-emmc.html

07:47 <Xogium> maybe this helps a bit

08:33 <Stalevar> Tricky. I wonder if EUDA use is possible to detect from the system

08:35 <Xogium> somewhat, if you can know the chip's storage size and it doesn't reflect reality, as in if lsblk shows a disk size for mmcblk0 that is different to the actual capacity -- generally half of it

08:39 <Stalevar> Disk /dev/mmcblk0: 7818 MB, 7818182656 bytes

08:39 <Stalevar> 4 heads, 32 sectors/track, 119296 cylinders, total 15269888 sectors

08:39 <Stalevar> Xogium, it is 8G chip

08:39 <Xogium> then it is definitely not using enhanced user area

08:47 <javierm> geertu: ah! I didn't know about D2 (so many 1 channel pixel formats)

08:47 <javierm> err, I meant D1 instead

08:49 <javierm> but yeah, didn't know about D2 either :)

09:52 <Stalevar> Xogium, either way the problem is there is no root password and /etc/shadow is on squashfs

09:52 <Stalevar> however default user has read access to eMMC so I was able to explore it