Open main menu

DAVE Developer's Wiki β

Changes

ORCA-TN-001 — Running Armbian Bullseye (Debian 11)

1,723 bytes added, 15:22, 3 February 2023
Preparing the bootable microSD card
|-
|1.0.0
|January February 2023
|First public release
|-
==Introduction==
This Technical Note (TN) shows how to run Debian 11 (Bullseye) distribution on [[ORCA_SBC|Orca SBC]].
==Testbed== ==Building and deploying To make the root file system onto the target==whole process as straightforward as possible, a prebuilt binary image was used, specifically an [https://www.armbian.com/uefi-arm64/ ''Armbian Generic ARM64''] [https://armbian.site-meganet.com/dl/uefi-arm64/archive/Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img.xz unzx Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimalminimal image].img.xz
==Preparing the bootable microSD card==
The starting point is the default bootable microSD card associated with the release 2.0.0 of the [[DESK-MX8M-L|DESK-MX8M-L kit]]. The card partition scheme has to be modified in order to create a partition that will be used to store the Debian root file system. In the following example, this partition was created using the unused space. This partition is mounted at <code>/media/user/debian/</code> when the card is inserted into the host's reader. After downloading the Armbian image on the host, the contents of the Debian root file system are extracted and copied to this partition. To calculate the offset to mount the partition of the Armbian image, multiply the start address (532480 in the example) by 512.
<pre class="workstation-terminal">
$ unxz Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img.xz
...
$ fdisk -l ./Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img
Disk ./Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img: 3,45 GiB, 3690987520 bytes, 7208960 sectors
./Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img1 8192 532479 524288 256M EFI
./Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img2 532480 7208926 6676447 3,2G Linu
 
 
$ sudo mount -o loop,offset=272629760 Armbian_22.11.1_Uefi-arm64_bullseye_current_5.15.80_minimal.img /mnt/tmp/
$ cd /mnt/tmp/$ sudo cp -aRv * /media/amarsonuser/debian/'armbian.key' -> '/media/amarsonuser/debian/armbian.key''bin' -> '/media/amarsonuser/debian/bin''boot' -> '/media/amarsonuser/debian/boot'
...
</pre>
Then, adjust the <code>/etc/fstab</code> file to make it match the actual [https://linuxhint.com/uuid_storage_devices_linux/ UUID] of the microSD card's partition used for storing the Debian file system. The resulting file used for this test is the following:<pre class="workstation-terminal">
root@uefi-arm64:~# cat /etc/fstab
UUID=41eabd71-ef7f-4a75-94a0-3a55dbacbaea / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1
#UUID=7EEE-611C /boot/efi vfat defaults 0 2
tmpfs /tmp tmpfs defaults,nosuid 0 0
</pre>
 
After unmounting the microSD card's partition, move the card to the target.
 
The last step before booting Orca SBC target is to change the U-Boot environment so that the Linux kernel uses the <code>/dev/mmcblk1p3</code> partition for mounting the root file system.
==Bootstrap process==
If the target is set up properly, the booting process will look like this:
<pre class="board-terminal mw-collapsible mw-collapsed">
U-Boot SPL 2020.04-desk-mx8m-l-2.0.0-rc2+fslc+g32087d457a (Dec 20 2022 - 15:01:10 +0000)
SOM ConfigID not found, using default
root@uefi-arm64:~#
</pre>
4,650
edits