----- Reply to message -----
Subject: Re: [Freedombox-discuss] what about a freedombox image for beaglebone black revision c emmc?
Date: 15 March 2018 at 20:42:38
From: ni nhar <nin...@inbox.lv>
To: James Valleroy <jvalle...@mailbox.org>
Subject: Re: [Freedombox-discuss] what about a freedombox image for beaglebone black revision c emmc?
Date: 15 March 2018 at 20:42:38
From: ni nhar <nin...@inbox.lv>
To: James Valleroy <jvalle...@mailbox.org>
Remark. If this reply is not sent to the freedombox email list, it is a mistake.Then please tell how I reply to the freedombox email list.----- Reply to message -----
Subject: Re: [Freedombox-discuss] what about a freedombox image for beaglebone black revision c emmc?
Date: 15 March 2018 at 13:43:40
From: James Valleroy <jvalle...@mailbox.org>
To: <freedombox-discuss@lists.alioth.debian.org>On 03/15/2018 01:35 AM, Sunil Mohan Adapa wrote:
> On Wednesday 14 March 2018 09:00 PM, ni nhar wrote:
>> beaglebone black revision c has an emmc chip. I asked for instruction
>> on how to install the freedombox on the emmc. Got no answer.
>
> Currently, there are no reports of people installing on eMMC for
> BeagleBone Black Revision C. IIRC, quite some time ago, the kernel
> didn't support installing on eMMC.
I am a layperson. I was not aware the kernel has
to be able to support emmc. I thought
configuring a file on the sdcard which the freedombox image has
been written to, would enable the sdcard to write
the freedombox onto the emmc.
I think you have enough tasks about the freedombox and
making a beaglebone black revision c emmc
compatible freedombox image should be skipped.
> If you give it a try and it works, do write about it. We can prepare
> instructions for eMMC installation or prepare a separate image if necessary.
I cannot. I am not skilled. Because I got no answer on this email list,
I planned to ask on the beaglebone black forum.
https://beagleboard.org/discuss
I do not know if you can ask questions if you do not want to
make log in on google? If signing in on google is a
requirement about the forum then I do not want to post
on the forum.
On installing debian 9 on a beaglebone black revision c's
emmc.
After writing the debian 9 image
https://beagleboard.org/latest-images
onto a sdcard, you have to edit a file on the sdcard.
It is file /boot/uEnv.txt
File uenv.txt:
-----
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
uname_r=4.9.45-ti-r57
#uuid=
#dtb=
###U-Boot Overlays###
###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
enable_uboot_overlays=1
###
###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo
#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo
#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo
#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo
###
###Additional custom capes
#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo
#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo
#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo
#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo
###
###Custom Cape
#dtb_overlay=/lib/firmware/<file8>.dtbo
###
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
###PRUSS OPTIONS
###pru_rproc (4.4.x-ti kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
###pru_uio (4.4.x-ti & mainline/bone kernel)
uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
###
###Cape Universal Enable
enable_uboot_cape_universal=1
###
###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1
###
###U-Boot fdt tweaks...
#uboot_fdt_buffer=0x60000
###U-Boot Overlays###
cmdline=coherent_pool=1M net.ifnames=0 quiet
#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e
##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
#cape_enable=bone_capemgr.enable_partno=
##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
-----
You have to remove the # from the last line.
Instead of a separate image, we could add an option that can be selected
during setup (or at a later time):
1. The system boots first from the micro SD card.
2. The user creates their account, and then selects an option like
"Install to other storage device" (supported internal storage or SSD).
3. If needed, the other device is formatted with btrfs filesystem, with
appropriate warnings.
4. The system creates a btrfs snapshot, and uses "btrfs send" and "btrfs
receive" to copy it to the other device.
5. The system performs any device-specific setup required to have it
boot from the other device.
6. The user is instructed that the system will shutdown, and then they
should remove the micro SD card, and reboot.
7. The system boots from the new storage device.
--
James
_______________________________________________
Freedombox-discuss mailing list
Freedombox-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
_______________________________________________ Freedombox-discuss mailing list Freedombox-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
