Hi
Is it possible to boot the R4SE with the R4S image. I was hoping to eventually migrate ipfire to the eMMC for a more stable system. I have had a couple of instances where the sd card has failed on my orangePi. Usually after a system upgrade and reboot.
Many thanks
Paul
Technically yes, it should boot just fine.
E is industrial use with fixed mac address for international market.
First try it on an sdcard before flashing it on emmc cause in case they changed the ddr module then it might not boot.
Good Luck.
It boots well from sd card. But not able yet to flash it to the eMMC. It seems that ipfire do not recognize the eMMC
[root@secbox ~]# ls /dev/mm*
/dev/mmcblk1 /dev/mmcblk1p1 /dev/mmcblk1p2 /dev/mmcblk1p3
No mmcblk2 (eMMC)
booting from sd with friendlyWrt
I flashed the eMMC from a working (booting) sd card with IPFire arm core 180.
root@FriendlyWrt:~# dd if=/dev/sda of=/dev/mmcblk2 bs=1M status=progress
8021606400 bytes (8.0 GB, 7.5 GiB) copied, 509 s, 15.8 MB/s
7655+0 records in
7655+0 records out
8026849280 bytes (8.0 GB, 7.5 GiB) copied, 512.079 s, 15.7 MB/s
root@FriendlyWrt:~#
After sync, power off, eject sd’s and power on…
No boot from eMMC, but I observe this in the eMMC booting again from sd with friendlyWrt:
root@FriendlyWrt:~# ls -l /dev/mmcblk2*
brw------- 1 root root 179, 0 Jan 18 2013 /dev/mmcblk2
brw------- 1 root root 179, 32 Jan 18 2013 /dev/mmcblk2boot0
brw------- 1 root root 179, 64 Jan 18 2013 /dev/mmcblk2boot1
brw------- 1 root root 179, 1 Jan 18 2013 /dev/mmcblk2p1
brw------- 1 root root 179, 2 Jan 18 2013 /dev/mmcblk2p2
brw------- 1 root root 179, 3 Jan 18 2013 /dev/mmcblk2p3
crw------- 1 root root 243, 0 Jan 18 2013 /dev/mmcblk2rpmb
root@FriendlyWrt:~#
The sd car with ipfire has only 3 partitions and eMMC new partitions should be …p1,…p2, …p3 but any idea of what …boot0, …boot1 and …rpmb?
Any idea how to boot iPfire form eMMC on R4SE?
Thanks in advance