Jump to content
  • 0

Incorrect boot behavior on OrangePI Plus 2E


Petr
 Share

Question

I encountered a very strange boot behavior on OrangePI Plus 2E. When I boot from SD card with the desktop Armbian image, I'm having just an input of some color on HDMI (photo attached). No U-boot output on screen, but considering UART output both U-boot and system boot with no errors (log file is attached). Boot with the server Armbian image goes just fine, except no U-boot output on screen (only on UART) and screen resolution is 1280x720, while native resolution for the display is 1920x1080.

Until recently everything worked just fine with both desktop and mainline images, and U-boot giving proper output on screen in 10920x1080 resolution.

What I tried so far:

1) Rewrote desktop image on same SD card after full formatting. Didn't help, nothing changed.

2) Moved to NEXT kernel on mainline image, reinstalled U-boot. Didn't help, still no display output in U-boot and resolution stuck on 1280x720.

What I'm going to try now:

- Write both images on new SD cards.

I have a default preinstalled Android image on eMMC and it boots just fine, but I'm not sure what that means to my problem. Guess it's not a failure of HDMI interface at least.

 

Would appreciate any help on this problem.

2uzxZiEK0dU.jpg

Log from UART on boot of desktop image:

U-Boot SPL 2018.05-armbian (May 04 2019 - 10:26:53 +0200)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2018.05-armbian (May 04 2019 - 10:26:53 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus 2E
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
230454 bytes read in 23 ms (9.6 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
USB4:   USB EHCI 1.00
USB5:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 4 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 2 USB Device(s) found
scanning bus 5 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 12 ms (308.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 9 ms (21.5 KiB/s)
5222295 bytes read in 302 ms (16.5 MiB/s)
4654976 bytes read in 278 ms (16 MiB/s)
Found legacy kernel configuration
36984 bytes read in 8 ms (4.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5222231 Bytes = 5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   2048MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2c00081!
ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]!

Ubuntu 16.04.6 LTS orangepiplus2e ttyS0

orangepiplus2e login: petr
Password:
  ___                               ____  _         ____  _____
 / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_)  _    |___ \| ____|
| | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |_| |_    __) |  _|
| |_| | | | (_| | | | | (_| |  __/ |  __/| |_   _|  / __/| |___
 \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| |_|   |_____|_____|
                       |___/

Welcome to ARMBIAN 5.83 stable Ubuntu 16.04.6 LTS 3.4.113-sun8i
System load:   1.51 1.54 0.66   Up time:       3 min
Memory usage:  8 % of 2014MB    IP:            172.18.148.144
CPU temp:      34°C
Usage of /:    6% of 29G

[ 0 security updates available, 3 updates total: apt upgrade ]
Last check: 2019-07-04 17:43

[ General system configuration (beta): armbian-config ]


petr@orangepiplus2e:~$

Edited by Petr
Link to comment
Share on other sites

7 answers to this question

Recommended Posts

Check forum guidelines to use maximum potential!

  • 0
1 hour ago, Petr said:

No U-boot output on screen, but considering UART output both U-boot and system boot with no errors


If your screen is not attached, there will be no error. HDMI is optional component ;) Since we have no logs, we can only guess. If modern kernel/u-boot doesn't show up nothing it could be just a bad cable. Have you tried with other?

Android boot loader is totally different.

Link to comment
Share on other sites

  • 0

Thanks for your answers.

To NicoD:

I just tried Armbian 5.59 Ubuntu Xenial on a fresh new SD card. No difference.

To Igor:

I guess I wasn't clear in my description of current and previous behavior.

Previous behavior:

Armbian Xenial Desktop: 1920x1080 display U-boot log output on HDMI, then 1920x1080 OS boot log, then desktop environment.

Armbian Bionic Mainline: 1920x1080 display U-boot log output on HDMI, then 1920x1080 OS boot log and login promt.

Current behavior:

Armbian Xenial Desktop: No HDMI output during U-boot (can track it through UART), then this same-color on HDMI.

Armbian Bionic Mainline: No HDMI output during U-boot, then 1280x720 OS boot log output on HDMI, then login promt.

I understand that Android bootloader is different from U-boot and Armbian, but I guess the fact that the SBC boots at all may mean that this behavior not a complete hardware failure. Maybe I guess wrong.

I already tried three different HDMI cables (proved to work with Raspberry PI and Win10 PC) and two monitors, though both of the same model. Going to try monitor of another model.

Edit: tried another monitor. Same one-color image. Monitor detected that the image is 1280x720@60Hz

Link to comment
Share on other sites

  • 0
2 hours ago, Petr said:

Armbian Bionic Mainline: No HDMI output during U-boot, then 1280x720 OS boot log output on HDMI, then login promt.


I have this board in front of me, connected to my HD dev monitor and I have FHD picture. This is the exact image I have used:
https://dl.armbian.com/orangepiplus2e/archive/Armbian_5.90_Orangepiplus2e_Debian_buster_next_4.19.57.7z

 

root@orangepiplus2e:/home/igorp# armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/1NMP
Please post the URL in the forum where you've been asked for.

Logs:
http://ix.io/1NMP

Link to comment
Share on other sites

  • 0

 

Just now, Igor said:

This is the exact image I have used

I tried this image and not really anything changed except now screen resolution is 1024x768@60p. I read through the logs and it seems that the board fails to auto-detect parameters of a monitor attached.

Logs: http://ix.io/1NN5

I guess at this point it's not a software problem, but I'm curious what could be the reason after all, considering that the board used to boot just fine.

I have a bold assumption that it could be related that few days ago there was a power failure with short period of over-voltage at the building I work in so it may be the reason (or may not, I don't really know).

Anyway thanks a lot for your help!

Link to comment
Share on other sites

  • 0

A little of update: I installed desktop environment (using armbian-config) on both image provided by @Igor and the one downloaded from the board page (Armbian Xenial 5.85 stable, but with kernel updated to 5.10 using armbian-config). In both cases I'm having Armbian desktop environment working fine, though the resolution is still 1024x768. I've read this instruction and added line setenv video-mode sunxi:1920x1080-24@60,monitor=dvi,hpd=0,edid=0 to my  boot.cmd file, recompiled it to boot.scr and rebooted twice, but it gave no difference. Is it possible to change resolution manually any other way?

 

I assume this behavior could be accounted as a proof that my board experiences some hardware fault, while it's being handled differently by legacy and mainline kernel. Guess not really much can be done at this point.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...