please choosego to mobile | Continue to access the PC version
View: 15322|Reply: 79

Orange Pi Linux Opi Zero2 DTB issues

[Copy link]

1

threads

3

posts

15

credits

Novice

Rank: 1

credits
15
Published in 2021-1-4 21:44:03 | Show all floors |Read mode
I downloaded the OrangePi Linux image for the Orange Pi Zero2 board from here. This image boots and works fine.

I noticed that the /boot/boot.cmd script is such that it does not actually load the DTB file for the Zero2 board. I need to make some changes to the DTB/DTS file for my project. But if I update the boot.cmd script and generate the new boot.scr such that it loads the DTB file using the FDT command, then the kernel stops booting.

Here are the FDT lines in the original boot.cmd
  1. #load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile}
  2. #fdt addr -c ${fdt_addr_r}
  3. #fdt addr ${fdt_addr_r}
  4. #fdt resize 65536
Copy code

Here is what I have changed them to:
  1. load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb-4.9.170-sun50iw9/sunxi/sun50i-h616-orangepi-zero2.dtb
  2. fdt addr -c ${fdt_addr_r} 0x40000
  3. fdt addr ${fdt_addr_r} 0x40000       
  4. fdt resize 0x10000
Copy code







1

threads

3

posts

15

credits

Novice

Rank: 1

credits
15
 Author| Published in 2021-1-4 21:45:41 | Show all floors
With this changed boot.scr/boot.cmd file, this is the output I see on the UART console. After this boot gets stuck. I have tried with different values of the FDT address, such as 0x10000, ${fdt_addr_r}, etc. Always the same result. Sometimes the display on HDMI becomes shaky but nothing else happens.

  1. Hit any key to stop autoboot:  0
  2. no mmc device at slot 1
  3. card_caps:0x3000000a
  4. host_caps:0x3000003f
  5. switch to partitions #0, OK
  6. mmc0 is current device
  7. Scanning mmc 0:1...
  8. Found U-Boot script /boot/boot.scr
  9. 2318 bytes read in 8 ms (282.2 KiB/s)
  10. ## Executing script at 43100000
  11. U-boot loaded from SD
  12. Boot script loaded from mmc
  13. 188 bytes read in 7 ms (25.4 KiB/s)
  14. 126435 bytes read in 16 ms (7.5 MiB/s)
  15. 8187924 bytes read in 355 ms (22 MiB/s)
  16. 23435336 bytes read in 992 ms (22.5 MiB/s)
  17. ## Booting kernel from Legacy Image at 41000000 ...
  18.    Image Name:
  19.    Image Type:   ARM Linux Kernel Image (uncompressed)
  20.    Data Size:    23435272 Bytes = 22.3 MiB
  21.    Load Address: 41000000
  22.    Entry Point:  41000000
  23.    Verifying Checksum ... OK
  24. ## Loading init Ramdisk from Legacy Image at 43300000 ...
  25.    Image Name:   uInitrd
  26.    Image Type:   ARM Linux RAMDisk Image (gzip compressed)
  27.    Data Size:    8187860 Bytes = 7.8 MiB
  28.    Load Address: 00000000
  29.    Entry Point:  00000000
  30.    Verifying Checksum ... OK
  31.    Loading Ramdisk to 49831000, end 49ffffd4 ... OK
  32.    reserving fdt memory region: addr=43000000 size=2f000
  33. ## Linux machid: 00000000, FDT addr: 43000000

  34. Starting kernel ...
Copy code

1

threads

3

posts

15

credits

Novice

Rank: 1

credits
15
 Author| Published in 2021-1-4 21:46:46 | Show all floors
In the past I have used Armbian on the Orange Pi PC board. The boot.scr of Armbian always uses the DTB file from dtb/, so I have never faced this problem. I am able to include various settings, such as enabling OTG port, in the DTB files and DTBO overlays. But with this Linux image I am facing problems.

10

threads

63

posts

548

credits

Senior member

Orange Pi Việt Nam

Rank: 4

credits
548
Published in 2021-1-29 17:06:16 | Show all floors
Hello,

Do you manage to install docker on the Ubuntu version from Xunlong?

I have tried Ubuntu/Debian but still get this error

  1. Setting up docker-ce (5:19.03.14~3-0~debian-buster) ...
  2. Job for docker.service failed because the control process exited with error code.
  3. See "systemctl status docker.service" and "journalctl -xe" for details.
  4. invoke-rc.d: initscript docker, action "start" failed.
  5. ● docker.service - Docker Application Container Engine
  6.    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  7.    Active: activating (auto-restart) (Result: exit-code) since Fri 2021-01-29 08:58:46 UTC; 71ms ago
  8.      Docs: <a href="https://docs.docker.com" target="_blank">https://docs.docker.com</a>
  9.   Process: 3499 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
  10. Main PID: 3499 (code=exited, status=1/FAILURE)
  11. dpkg: error processing package docker-ce (--configure):
  12. installed docker-ce package post-installation script subprocess returned error exit status 1
  13. Errors were encountered while processing:
  14. docker-ce
Copy code


0

threads

80

posts

216

credits

Intermediate member

Rank: 3Rank: 3

credits
216
Published in 2023-3-13 15:57:37 | Show all floors

0

threads

80

posts

216

credits

Intermediate member

Rank: 3Rank: 3

credits
216
Published in 2023-4-7 12:41:39 | Show all floors

0

threads

80

posts

216

credits

Intermediate member

Rank: 3Rank: 3

credits
216
Published in 2023-4-8 11:28:14 | Show all floors

0

threads

80

posts

216

credits

Intermediate member

Rank: 3Rank: 3

credits
216
Published in 2023-5-3 12:12:00 | Show all floors

0

threads

9

posts

28

credits

Novice

Rank: 1

credits
28
Published in 2023-5-16 17:07:00 | Show all floors
Very useful for me.
basket random

0

threads

3

posts

14

credits

Novice

Rank: 1

credits
14
Published in 2023-6-6 16:15:28 | Show all floors
Ensure that you are using the correct DTB file for your specific Orange Pi Zero2 board revision and the Linux distribution you are running magic tiles 3. DTB files can vary based on hardware revisions, so using an incorrect DTB can cause compatibility issues.
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list