Rockpi4/dev/Debian - Revision history

Stephen at 03:40, 30 January 2023

2023-01-30T03:40:37Z

Nascs at 07:50, 29 January 2023

2023-01-29T07:50:02Z

Nascs at 07:48, 29 January 2023

2023-01-29T07:48:24Z

Nascs at 07:43, 29 January 2023

2023-01-29T07:43:50Z

Nascs at 07:43, 29 January 2023

2023-01-29T07:43:01Z

Nascs at 07:38, 29 January 2023

2023-01-29T07:38:04Z

Nascs at 07:37, 29 January 2023

2023-01-29T07:37:20Z

Nascs at 07:34, 29 January 2023

2023-01-29T07:34:51Z

Nascs at 07:21, 29 January 2023

2023-01-29T07:21:05Z

Stephen at 09:55, 7 November 2022

2022-11-07T09:55:16Z

← Older revision		Revision as of 03:40, 30 January 2023
Line 149:		Line 149:

	For developers, flash from USB OTG port, follow instructions [[Rockpi4/dev/usb-install \|here]]. You will need the flash helper '''rk3399_loader_xxx.bin''' and generated '''out/system.img''' files.		For developers, flash from USB OTG port, follow instructions [[Rockpi4/dev/usb-install \|here]]. You will need the flash helper '''rk3399_loader_xxx.bin''' and generated '''out/system.img''' files.
−
−	~~=== build deban11 armhf image with a existed image ===~~
−
−	~~1. Flash a debian11 arm64 image to a sd card or a emmc module~~
−
−	~~2. Insert the SD card or emmc that has been burned into the image to the local computer and mount it~~
−
−	~~radxa@radxa:~$ sudo blkid /dev/sdb2~~
−	~~/dev/sdb2: LABEL="rootfs" UUID="8bf96d05-7c97-42fc-863c-95e3e7603ef4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="474d4c1f-53da-447c-bab4-334abe0d5753"~~
−	~~radxa@radxa:~$ sudo blkid /dev/sdb1~~
−	~~/dev/sdb1: LABEL_FATBOOT="config" LABEL="config" UUID="4AD5-9369" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="config" PARTUUID="8d24a074-ea49-4d24-a17c-82dd88776fa2"~~
−	~~radxa@radxa:~$ lsblk~~
−	~~... ...~~
−	~~sdb 8:16 1 29.3G 0 disk~~
−	~~├─sdb1 8:17 1 16M 0 part~~
−	~~└─sdb2 8:18 1 5.1G 0 part~~
−
−	~~radxa@radxa:~$ sudo mount /dev/sdb2 /data2~~
−	~~radxa@radxa:~$ cd /data2~~
−
−	~~3. Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system~~
−
−	~~radxa@radxa:/data2$ sudo cp -r ./boot ~/~~
−	radxa@radxa:/data2$ sudo rm -rf *
−	~~radxa@radxa:/data2$ sudo cp -av ~/pro/rootfs/* ./~~
−	~~radxa@radxa:/data2$ sudo cp -av ~/boot/* ./boot/~~
−
−	~~radxa@radxa:/data2$ sudo cat ./etc/fstab~~
−	~~# UNCONFIGURED FSTAB FOR BASE SYSTEM~~
−
−	~~//Replace the uuid in the preceding section~~
−	~~radxa@radxa:/data2$ sudo cat ./etc/fstab~~
−	~~# UNCONFIGURED FSTAB FOR BASE SYSTEM~~
−	~~UUID=8bf96d05-7c97-42fc-863c-95e3e7603ef4 / ext4 defaults 0 1~~
−	~~UUID=4AD5-9369 /config vfat defaults,x-systemd.automount 0 2~~
−
−	~~4. Umount the sd card or the emmc, then boot up~~
−
−	~~radxa@radxa:/data2$ cd~~
−	~~radxa@radxa:~$ sudo umount /data2~~
−
−	~~5. After the system start, Check whether rootfs is armhf (32-bit)~~
−
−	~~radxa@rock-4c-plus:~$ sudo apt-get install file -y~~
−	~~radxa@rock-4c-plus:~$ file /bin/ls~~
−	~~/bin/ls: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, Buildd~~
−	~~radxa@rock-4c-plus:~$~~
−
−	~~6. Check whether the tools are 32-bit. If not, uninstall the tool and reinstall it~~

	=== FAQs ===		=== FAQs ===

@@ Line 156: / Line 156: @@
 . Insert the SD card or emmc that has been burned into the image to the local computer and mount it
-  radxa@rock-4c-plus:~$ sudo blkid /dev/sdb2
+  radxa@radxa:~$ sudo blkid /dev/sdb2
   /dev/sdb2: LABEL="rootfs" UUID="8bf96d05-7c97-42fc-863c-95e3e7603ef4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="474d4c1f-53da-447c-bab4-334abe0d5753"
   radxa@radxa:~$ sudo blkid /dev/sdb1
   /dev/sdb1: LABEL_FATBOOT="config" LABEL="config" UUID="4AD5-9369" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="config" PARTUUID="8d24a074-ea49-4d24-a17c-82dd88776fa2"
-  radxa@rock-4c-plus:~$ lsblk
+ radxa@radxa:~$ lsblk
   ... ...
   sdb      8:16   1  29.3G  0 disk
@@ Line 166: / Line 166: @@
   └─sdb2   8:18   1   5.1G  0 part
-   radxa@rock-4c-plus:~$ sudo mount /dev/sdb2 /data2
+   radxa@radxa:~$ sudo mount /dev/sdb2 /data2
-   radxa@rock-4c-plus:~$ cd /data2
+   radxa@radxa:~$ cd /data2
 . Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system

@@ Line 156: / Line 156: @@
 . Insert the SD card or emmc that has been burned into the image to the local computer and mount it
-  sudo blkid /dev/sdb2
+  radxa@rock-4c-plus:~$ sudo blkid /dev/sdb2
   /dev/sdb2: LABEL="rootfs" UUID="8bf96d05-7c97-42fc-863c-95e3e7603ef4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="474d4c1f-53da-447c-bab4-334abe0d5753"
   radxa@radxa:~$ sudo blkid /dev/sdb1
   /dev/sdb1: LABEL_FATBOOT="config" LABEL="config" UUID="4AD5-9369" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="config" PARTUUID="8d24a074-ea49-4d24-a17c-82dd88776fa2"
- lsblk
+  radxa@rock-4c-plus:~$ lsblk
   ... ...
   sdb      8:16   1  29.3G  0 disk
@@ Line 166: / Line 166: @@
   └─sdb2   8:18   1   5.1G  0 part
- sudo mount /dev/sdb2 /data2
+  radxa@rock-4c-plus:~$ sudo mount /dev/sdb2 /data2
- cd /data2
+  radxa@rock-4c-plus:~$ cd /data2
 . Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system

@@ Line 197: / Line 197: @@
   radxa@rock-4c-plus:~$
-. Check whether the tool is 32-bit. If not, uninstall the tool and reinstall it
+. Check whether the tools are 32-bit. If not, uninstall the tool and reinstall it
 === FAQs ===

@@ Line 156: / Line 156: @@
 . Insert the SD card or emmc that has been burned into the image to the local computer and mount it
-```
+ sudo blkid /dev/sdb2
-sudo blkid /dev/sdb2
+ /dev/sdb2: LABEL="rootfs" UUID="8bf96d05-7c97-42fc-863c-95e3e7603ef4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="474d4c1f-53da-447c-bab4-334abe0d5753"
-/dev/sdb2: LABEL="rootfs" UUID="8bf96d05-7c97-42fc-863c-95e3e7603ef4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="474d4c1f-53da-447c-bab4-334abe0d5753"
+ radxa@radxa:~$ sudo blkid /dev/sdb1
-nasca@nasca-H4:~$ sudo blkid /dev/sdb1
+ /dev/sdb1: LABEL_FATBOOT="config" LABEL="config" UUID="4AD5-9369" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="config" PARTUUID="8d24a074-ea49-4d24-a17c-82dd88776fa2"
 /dev/sdb1: LABEL_FATBOOT="config" LABEL="config" UUID="4AD5-9369" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="config" PARTUUID="8d24a074-ea49-4d24-a17c-82dd88776fa2"
-−
-−
-−
   lsblk
-... ...
+ ... ...
-sdb      8:16   1  29.3G  0 disk
+ sdb      8:16   1  29.3G  0 disk
-├─sdb1   8:17   1    16M  0 part
+ ├─sdb1   8:17   1    16M  0 part
-└─sdb2   8:18   1   5.1G  0 part
+ └─sdb2   8:18   1   5.1G  0 part
-−
   sudo mount /dev/sdb2 /data2
   cd /data2
 . Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system
-```
+ radxa@radxa:/data2$ sudo cp -r ./boot ~/
-radxa@radxa:/data2$ sudo cp -r ./boot ~/
+ radxa@radxa:/data2$ sudo rm -rf *
-radxa@radxa:/data2$ sudo rm -rf *
+ radxa@radxa:/data2$ sudo cp -av ~/pro/rootfs/* ./
-radxa@radxa:/data2$ sudo cp -av ~/pro/rootfs/* ./
+ radxa@radxa:/data2$ sudo cp -av ~/boot/* ./boot/
 radxa@radxa:/data2$ sudo cp -av ~/boot/* ./boot/
-radxa@radxa:/data2$ sudo cat ./etc/fstab
+ radxa@radxa:/data2$ sudo cat ./etc/fstab
-# UNCONFIGURED FSTAB FOR BASE SYSTEM
+ # UNCONFIGURED FSTAB FOR BASE SYSTEM
-//Replace the uuid in the preceding section
+ //Replace the uuid in the preceding section
-radxa@radxa:/data2$ sudo cat ./etc/fstab
+ radxa@radxa:/data2$ sudo cat ./etc/fstab
-# UNCONFIGURED FSTAB FOR BASE SYSTEM
+ # UNCONFIGURED FSTAB FOR BASE SYSTEM
-UUID=8bf96d05-7c97-42fc-863c-95e3e7603ef4       /       ext4    defaults        0       1
+ UUID=8bf96d05-7c97-42fc-863c-95e3e7603ef4       /       ext4    defaults        0       1
-UUID=4AD5-9369  /config vfat    defaults,x-systemd.automount    0       2
+ UUID=4AD5-9369  /config vfat    defaults,x-systemd.automount    0       2
-```
+. Umount the sd card or the emmc, then boot up
 .  After the system start, Check whether rootfs is armhf (32-bit)
-```
+ radxa@rock-4c-plus:~$ sudo apt-get install file -y
 . Check whether the tool is 32-bit. If not, uninstall the tool and reinstall it

@@ Line 202: / Line 202: @@
 ```
 radxa@rock-4c-plus:~$ sudo apt-get install file -y
 radxa@rock-4c-plus:~$ file /bin/ls
 /bin/ls: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, Buildd

@@ Line 152: / Line 152: @@
 === build deban11 armhf image with a existed image ===
-==== Flash a debian11 arm64 image to a sd card or a emmc module ====
+. Flash a debian11 arm64 image to a sd card or a emmc module
-==== Insert the SD card or emmc that has been burned into the image to the local computer and mount it ====
+. Insert the SD card or emmc that has been burned into the image to the local computer and mount it
 ```
@@ Line 175: / Line 175: @@
 ```
-====  Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system ====
+. Go to the root file system, back up the boot directory, delete and replace the root file system, and restore the boot directory to the root file system
 ```
@@ Line 194: / Line 194: @@
 ```
-==== Umount the sd card or the emmc, then boot up ====
+. Umount the sd card or the emmc, then boot up
-−
 ```
 radxa@radxa:/data2$ cd
 radxa@radxa:~$ sudo umount /data2
 ```
-==== After the system start, Check whether rootfs is armhf (32-bit)  ====
+.  After the system start, Check whether rootfs is armhf (32-bit)
 ```
 radxa@rock-4c-plus:~$ sudo apt-get install file -y
@@ Line 235: / Line 234: @@
 /bin/ls: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, Buildd
 radxa@rock-4c-plus:~$
-==== Check whether the tool is 32-bit. If not, uninstall the tool and reinstall it ====
+```
 === FAQs ===

@@ Line 152: / Line 152: @@
 === build deban11 armhf image with a existed image ===
-==== FAQs ====
+ sudo mount /dev/sdb2 /data2
 .For system image built from rockchip-bsp, what is the user name and password?
@@ Line 175: / Line 255: @@
   ./build/mk-kernel.sh rk3399-fuhai
-==== Troubleshooting ====
+=== Troubleshooting ===
 Check [[Rockpi4/FAQs |ROCK Pi 4 FAQs]] first, if it doesn't help, start a new post on the forum https://forum.radxa.com/c/dev

← Older revision		Revision as of 07:21, 29 January 2023
Line 149:		Line 149:

	For developers, flash from USB OTG port, follow instructions [[Rockpi4/dev/usb-install \|here]]. You will need the flash helper '''rk3399_loader_xxx.bin''' and generated '''out/system.img''' files.		For developers, flash from USB OTG port, follow instructions [[Rockpi4/dev/usb-install \|here]]. You will need the flash helper '''rk3399_loader_xxx.bin''' and generated '''out/system.img''' files.
		+
		+	=== build deban11 armhf image with a existed image ===
		+
		+
		+
		+
		+
		+
		+

	==== FAQs ====		==== FAQs ====

@@ Line 75: / Line 75: @@
 ==== Build u-boot ====
-  ./build/mk-uboot.sh rockpi4b     #For ROCK Pi 4 Mode B
+  ./build/mk-uboot.sh rk3399-rock-pi-4b     #For ROCK Pi 4 Mode B
 The generated images will be copied to out/u-boot folder
@@ Line 85: / Line 85: @@
 Build kernel with default '''rockchip_linux_defconfig'''
-  ./build/mk-kernel.sh rockpi4b    #For ROCK Pi 4 Mode B
+  ./build/mk-kernel.sh rk3399-rock-pi-4b    #For ROCK Pi 4 Mode B
 ===== Change kernel config(optional)=====
@@ Line 96: / Line 96: @@
   make rockchip_linux_defconfig
   make menuconfig
   cd ..
-  ./build/mk-kernel.sh rockpi4b    #For ROCK Pi 4 Mode B
+  ./build/mk-kernel.sh rk3399-rock-pi-4b    #For ROCK Pi 4 Mode B
 You will get the kernel image and dtb file
   ls out/kernel/
-  Image  rockpi-4b-linux.dtb
+  Image  rk3399-rock-pi-4b.dtb
 ==== Make rootfs image ====
@@ Line 136: / Line 138: @@
 ==== Combine everything into one image ====
-  build/mk-image.sh -c rk3399 -b rockpi4 -t system -r rootfs/linaro-rootfs.img
+  build/mk-image.sh -c rk3399 -b rk3399-rock-pi-4b -t system -r rootfs/linaro-rootfs.img
 This will combine u-boot, kernel and rootfs into one image and generate GPT partition table. Output is
@@ Line 153: / Line 155: @@
 The user name is '''linaro''' and the password is '''linaro'''.
 ==== Troubleshooting ====
 Check [[Rockpi4/FAQs |ROCK Pi 4 FAQs]] first, if it doesn't help, start a new post on the forum https://forum.radxa.com/c/dev