Deploy On Sd Card - Cherry PUMA SOM-RK3399-Q7 User Manual

cat << EOT > /etc/systemd/network/eth0.network
[Match]
Name=eth0
[Network]
DHCP=yes
EOT
systemctl enable systemd-networkd
systemctl enable systemd-resolved
ln -f -s /lib/systemd/resolv.conf /etc/resolv.conf
When executing systemctl enable you may get the message qemu: Unsupported syscall: 278. The opera-
tion still succeeds and the message can be safely ignored.
Set the hostname and exit from the chroot:
echo rk3399-q7 > /etc/hostname
exit
We now have a root filesystem which can be deployed to the SD card.

4.9 Deploy on SD Card

4.9.1 Partition Setup
Both U-Boot and Linux will be located on the same SD card. The layout of the card after setup is as follows:
Offset Contents
0 Partition table
32kiB U-Boot SPL
240kiB U-Boot environment
256kiB U-Boot + ATF + Cortex-M0 firmware
2MiB Partition 1 (ext4 - Linux root fs)
To setup a SD card for booting you first need to create partitions. Partitions can be created using fdisk (assuming
the SD card is mapped to /dev/sd``X`` , where X should be replaced with your corresponding device-letter) and
has no partitions (this can be checked using the p command):
sudo fdisk /dev/sdX
> p
This should show an empty partition table, for example:
Disk /dev/sdX: 3980 MB,
123 heads, 62 sectors/track,
Units = sectors of 1 *
Sector size (logical/physical):
I/O size (minimum/optimal):
Disk identifier: 0xdbbd45c7
Device Boot Start
If there are partitions on the sdcard, they can be deleted with o.
The required partition can be created with the command n, then accepting the defaults, except for First
sector, where we use 4096:
> n
Partition type:
p primary (0 primary,
e extended
RK3399-Q7 User Manual
© Cherry Embedded Solutions GmbH
Files
spl_sd.img
u-boot.itb
boot.scr, Image, rk3399-puma.dtb, defaultEnv.txt and rootfs
3980394496 bytes
1019 cylinders, total
512 = 512 bytes
512 bytes / 512
512 bytes / 512 bytes
End Blocks
0 extended, 4 free)
7774208 sectors
bytes
Id System
(continues on next page)
v1.6
Page 23