# Building and Trying...BeagleBone Black and Aufs

**URL:** <https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671>\
**Category:** Linux Discussions\
**Created:** [January 6, 2023, 2:05am UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671 "2023-01-06T02:05:03Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 2:05am UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/1 "2023-01-06T02:05:03Z")

</div>

Hello,

I have, am currently, used aufs to build the kernel. I found their info. on a dainty oops. Anyway, outside of the miracle accident that got me involved in `aufs`, I would like to understand a bit more.

Does the images that are available to build only for eMMC or is there a way to utilize the build instructions from this site to allow for SD Card image creation?

Seth

P.S. Right now, I used these commands to build my image:

```auto
1. install u-boot
2. compile u-boot
3. install the kernel
4. compile the kernel
5. Then, I started to listen to the eewiki Linux guides on this effort
6. install info. to /fstab
7. install debian
8. build debian to the /rootfs/ dir.
9. debian is now at /rootfs/
10. I altered some files for use...
    a. /opt/ and /boot/ and /etc/ only
    b. I put in the files and info. into those directories to build the image w/ debian at /dev/mmcblk0p1
        and at /dev/mmcblk0p2
11. As you might guess, I cannot boot.

```

When did /dev/mmcblk0 start and /dev/mmcblk0p1 and /dev/mmcblk0p2 stop?

I am asking trying to fill in the data of what happened and when…

aufs only allows for so much of [beagleboard.org](http://beagleboard.org) ideas in their kernels, e.g. .dts files, `modules` are mostly hidden so far, and now I cannot boot.

I understand that this build from your ideas and knowledge is done and completed for now. I am not trying to follow along 100% of the time, i.e. as I would like to build differently and w/ other methods.

I will try to post the build. Oh!

`are these builds for use w/ TTL to USB adapters` or can I just plug and play w/ them? I may be mistaken but I think:

1. These builds are for eMMC builds only
2. The builds are for USB to TTL cable adapters also but only?

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 5:00am UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/2 "2023-01-06T05:00:33Z")

</div>

Hello,

Sorry about the above garble. I will update this compilation, the steps taken, soon. I just realized w/out proper explanations, helping me is beyond the scope of what actually I typed in my first set of ideas.

Seth

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 12:20pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/3 "2023-01-06T12:20:00Z")

</div>

Hello,

This is what I did:

```auto
install dependencies...and then compile the main components!

git clone https://github.com/u-boot/u-boot
cd u-boot/

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- distclean
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- am335x_evm_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig 
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-

wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.4.228.tar.xz
xz -d linux-5.4.228.tar.xz
tar -xvfp linux-5.4.228.tar
cd linux-5.4.228/

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- omap2plus_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-

```

This is now me following the references at eewiki for building the image that was made.

```auto
sudo cfdisk /dev/mmcblk0

... Either use two partitions or one partition depending on the year/make/model of the kernel/u-boot?

make it bootable
save yes
Exit

```

Then I basically follow all of the guide on the eewiki for the BeagleBone Black up until building the kernel modules and naming scheme for the kernel. If you see anything I am doing that is out of bounds, please let me know.

Seth

P.S. If there are a particular set of ideas I am missing, please instruct me.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 2:59pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/4 "2023-01-06T14:59:16Z")

</div>

Hi @silver2row a well debugged and fully supported how to is posted here: [Debian: Getting Started with the BeagleBone Black](https://forum.digikey.com/t/debian-getting-started-with-the-beaglebone-black/12967)

BeagleBone Blacks and similar devices have been shipping with this default configuration for probably 8-9 years now… It’s well tested and simpler then your split partition setup.

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 5:38pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/5 "2023-01-06T17:38:32Z")

</div>

Hello @RobertCNelson ,

No issue as usual. I am just recalling when I could build w/ one partition and a boot partition.

I do not think it was six years ago or so…

About the [beagleboard.org](http://beagleboard.org) boards, like the BBB, for a bit there was ideas being allocated into the kernel, `/arch/arm/boot/*/dts/*`, slowly and made things change a bit. So I thought…

I could be way off base. Anyway, no issue.

Seth

P.S. I will keep trying, i.e. as there is a fellow trying to get i2s working on his BBBW (I think). Anyway, I was going to pitch in and keep building images while producing the correct build steps for him/her but came up short.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 5:45pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/6 "2023-01-06T17:45:49Z")

</div>

I2S works fine on the BBB.

No one made a reference I2S cape, so there is no reference overlay in our git repo.

So as long as you:

1. Wire it up correctly
2. Load the proper Overlay

It’ll work. There are a few threads in the ti e2e forums on custom wiring/device-tree/etc…

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 5:48pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/7 "2023-01-06T17:48:06Z")

</div>

Thank you…

Seth

P.S. I saw on the [beagleboard.org](http://beagleboard.org) site in the docs. sections, there is a short on playing sound w/ ALSA. I sort of directed the person to that specified section of the docs.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 5:52pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/8 "2023-01-06T17:52:22Z")

</div>

The BBB has always had i2s audio, thru the HDMI port…

[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-boneblack-hdmi.dtsi?h=v6.2-rc2#n70](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-boneblack-hdmi.dtsi?h=v6.2-rc2#n70)

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 5:54pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/9 "2023-01-06T17:54:39Z")

</div>

The framer provides this support?

Seth

P.S. Right…the NXP onboard. That is the framer. So, it will be a hack from the am335x → NXP framer → HDMI → extra circuitry…

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 6:04pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/10 "2023-01-06T18:04:52Z")

</div>

> [@silver2row](#):
>
> So, it will be a hack from the am335x → NXP framer → HDMI → extra circuitry…

Why? SPI1\_SCLK, SPI1\_CS0, and SPI1\_D0 used for i2s audio are between the am335x and the NXP framer, are routed on the P8/P9 header so users can use them directly…

Just disable TDA19988…

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 6:11pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/11 "2023-01-06T18:11:53Z")

</div>

Oh…nice. I was unaware of this idea. I did not know how the i2s worked on the BBB.

Seth

P.S. Okay…I will keep reading about this idea.

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 6:13pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/12 "2023-01-06T18:13:29Z")

</div>

Hello @RobertCNelson ,

I thought i2c0 was internal only…

Seth

P.S. So, the overlay gets allocated to /boot/uEnv.txt, then before the actual build of the source of the overlays, one would remove said TDA19988, and then finally build the overlays…

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 6:15pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/13 "2023-01-06T18:15:44Z")

</div>

> [@silver2row](#):
>
> I thought i2c0 was internal only…

i2c and i2s are nothing alike, unlike a similar acronym… i2s is a serial point to point link…

Regards

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 6:16pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/14 "2023-01-06T18:16:49Z")

</div>

> [@silver2row](#):
>
> P.S. So, the overlay gets allocated to /boot/uEnv.txt, then before the actual build of the source of the overlays, one would remove said TDA19988, and then finally build the overlays…

[https://elinux.org/Beagleboard:BeagleBoneBlack\_Debian#U-Boot\_Disable\_on-board\_devices](https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices)

To Disable HDMI AUDIO:

```auto
disable_uboot_overlay_audio=1

```

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 6:21pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/15 "2023-01-06T18:21:14Z")

</div>

Okay and Right,

So, it is just disabling the HDMI audio in the u-boot via the `already-made-available` /boot/uEnv.txt file.

Then, one can use the sound and audio w/ SPI and not i2c.

I got confused I guess. Line 70 from the link above shows the &i2c0 `phandle` or directive (whatever it is called in DTS format) which showed the item in question.

Seth

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [January 6, 2023, 6:25pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/16 "2023-01-06T18:25:40Z")

</div>

> [@silver2row](#):
>
> So, it is just disabling the HDMI audio in the u-boot via the `already-made-available` /boot/uEnv.txt file.

Correct…

> [@silver2row](#):
>
> Then, one can use the sound and audio w/ SPI and not i2c.

 ![audio](https://global.discourse-cdn.com/digikey/original/3X/6/9/69f8b03e83b8c7308488bed6e030795bd430f2ce.png)

> [@silver2row](#):
>
> I got confused I guess. Line 70 from the link above shows the &i2c0 `phandle` or directive (whatever it is called in DTS format) which showed the item in question.

That’s the node with tda19988, which shows the i2s configuration…

Regards,

---

<div class="post-metadata">

**Author:** ![silver2row](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/silver2row/32/1016_2.png) [@silver2row](https://forum.digikey.com/u/silver2row)\
**Post date:** [January 6, 2023, 6:43pm UTC](https://forum.digikey.com/t/building-and-trying-beaglebone-black-and-aufs/27671/17 "2023-01-06T18:43:21Z")

</div>

Okay and Yes Sir,

Node. It is called a node. I saw that a little too late.

Seth
