Flash mbox Android on emmc using the steps from bpi wiki.
Then try to boot manjaro latest image.
Can I install it on eMMC and use it without SD card?
Yes
This image is to be used with bsp uboot on emmc as the Manjaro Image does not have any uboot.
Please try this steps.
- Flash Android on eMMC.
- Boot into Android. (just to make sure it works)
- Flash
Manjaro-ARMwith etcher on sdcard. - Insert SD Card and it should boot into Manjaro over sdcard.
- Test if everything that you want works on sdcard and make sure the time is synced to your current time.
- Run the Install emmc script as root.
sudo /boot/install-aml-emmc.sh(This will install the same OS from SD Card to emmc). - Reboot. (with sdcard to boot into sdcard once again)
- Reboot. (without sdcard to boot into emmc)
It seems the android image download links are down (500 Internal server error). I have the armbian image flashed to the eMMC already, but that bootloader won’t load the the Manjaro image from the SD card. I guess I need to wait until they fix the Android images.
I will upload it on my server. Will send you the link once it is uplaoded.
Update: Find it 2021-05-20-bpi-m5-m2pro-mbox-android9-emmc.zip
Filesize: 879.08mb
I have uploaded the md5sum to verify if the file is the same.
Good Luck.
After the installation to eMMC it says restart and reactivate multi-boot. I am not sure how to do that, but without the SD card it won’t boot. Do I need to do something between step 7 and 8?
Edit: I try KDE version and the GUI seems to crash/flicker/go black a lot. From SD card it boots every time, and the basic functionalities work, and I can confirm that panfrost works.
Edit2: Also do you know why free -h reports 980M (~1G) total memory instead of 4G? I can see your neofetch reports 984M only as well.
I thought My device is 1gb model but M5 is only 4gb so I need to check.
You need to restart with sdcard inserted and both into the sdcard again.
There is a small manual change you have to do.
Mount the emmc rootfs and in /etc/fstab comment out the rootfs as it is old PARTUUID.
I hope you get what I am trying to say, I will update that in the next released.
I did play around in /etc/fstab, I needed to restart from scratch due to a mistake. Still trying to make this work.
I ran
sudo blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT_MNJRO" LABEL="BOOT_MNJRO" UUID="4E25-E654" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="d9ecb2aa-9f05-4066-a980-89d6c8b22ee1"
/dev/mmcblk0p2: LABEL="ROOT_MNJRO" UUID="ac0fe79c-a1bf-483c-9352-75deb0452255" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="8a268f2f-4747-4a37-aa09-490201df48ea"
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT_MNJRO" LABEL="BOOT_MNJRO" UUID="0544-4078" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1d550000-01"
/dev/mmcblk1p2: LABEL="ROOT_MNJRO" UUID="2223eb3d-914f-4b24-b200-e08454309917" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1d550000-02"
/dev/zram0: LABEL="zram0" UUID="43483ee0-aa94-4fa6-b174-7e47fabd6941" TYPE="swap"
mmcblk1 device is the eMMC. Then I ran
sudo mount /dev/mmcblk1p2 /mnt
sudo nano /mnt/etc/fstab
and added the content
PARTUUID=1d550000-01 /boot vfat defaults 0 0
PARTUUID=1d550000-02 / ext4 defaults 0 1
Then reboot, and it still won’t boot. After putting the SD card back everything is ok, but is booted from SD card. Do you have any idea how to proceed?
What is in emmc boot partition?
Can you share
Mount /dev/mmcblk1p1 to mnt
ls -la /mnt/
Also
cat /mnt/uEnv.ini
drwxr-xr-x 4 root root 16384 1970 jan 1 .
drwxr-xr-x 18 root root 4096 febr 10 23.23 ..
drwxr-xr-x 4 root root 8192 febr 10 23.23 dtbs
-rwxr-xr-x 1 root root 735 febr 10 23.23 emmc_autoscript
-rwxr-xr-x 1 root root 663 febr 10 23.23 emmc_autoscript.cmd
-rwxr-xr-x 1 root root 28946944 febr 10 23.23 Image
-rwxr-xr-x 1 root root 7199548 febr 10 23.23 initramfs-linux.img
-rwxr-xr-x 1 root root 4642 febr 10 23.23 install-aml-emmc.sh
drwxr-xr-x 2 root root 8192 febr 10 23.23 LOST.DIR
-rwxr-xr-x 1 root root 4194304 febr 10 23.23 u-boot-default-aml.img
-rwxr-xr-x 1 root root 268 febr 10 23.23 uEnv.ini
-rwxr-xr-x 1 root root 28947008 febr 10 23.23 uImage
-rwxr-xr-x 1 root root 7199612 febr 10 23.23 uInitrd
dtb_name=/dtbs/amlogic/meson-sm1-bananapi-m5.dtb
bootargs=root=LABEL=ROOT_MNJRO rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 quiet splash plymouth.ignore-serial-consoles
Is there boot.ini or some file in sd card /boot/ ? Copy it over to emmc /boot/ and try to reboot
Where did you get this from?
It should be
bootargs=root=PARTUUID=1d550000-02
Copied boot.ini with conent
'V)�v�a�_�b����S905 autoscriptZif fatload mmc 0 0x1000000 u-boot.ext; then go 0x1000000; fi;
if fatload usb 0 0x1000000 u-boot.ext; then go 0x1000000; fi;
setenv env_addr 0x1040000
setenv initrd_addr 0x13000000
setenv boot_start 'bootm ${loadaddr} ${initrd_addr} ${dtb_mem_addr}'
setenv addmac 'if printenv mac; then setenv bootargs ${bootargs} mac=${mac}; elif printenv eth_mac; then setenv bootargs ${bootargs} mac=${eth_mac}; fi'
setenv try_boot_start 'if fatload ${devtype} ${devnum} ${loadaddr} uImage; then if fatload ${devtype} ${devnum} ${initrd_addr} uInitrd; then fatload ${devtype} ${devnum} ${env_addr} uEnv.ini && env import -t ${env_addr} ${filesize} && run addmac; fatload ${devtype} ${devnum} ${dtb_mem_addr} ${dtb_name} && run boot_start; fi;fi'
setenv devtype mmc
setenv devnum 0
run try_boot_start
setenv devtype usb
for devnum in 0 1 2 3 ; do run try_boot_start ; done
I just ran the install-aml-emmc.sh and it created the files on the eMMC boot partition. I did not change any file other than we talked about in this thread.
Now I changed uEnv.ini on the mmcblk1p1 to
dtb_name=/dtbs/amlogic/meson-sm1-bananapi-m5.dtb
bootargs=root=PARTUUID=1d550000-02 rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 quiet splash plymouth.ignore-serial-consoles
Shutdown, remove SD card still no boot.
I will test it myself. You’re confusing the bootloader by running the script again.
You used the same mbox android image like I did right ?
Same mbox Android image. I ran the script twice, but something went wrong so I reflashed Android and then run the script only once IIRC.
I am flashing mbx image on emmc now and then will test the KDE Latest image from the link.
In my test the mmc flash is not working as it not able to find any data in emmc when booting. I am testing this further to see whether this garbage bootloader needs more space to fit in.
Do you have any luck booting from eMMC?
No didn’t try it after that.
Do you plan to fix the memory and the eMMC issue or should we move to another image?
1 Like