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