stalker37 Posted August 13, 2020 Posted August 13, 2020 Hello. I can't enable HDMI output for A64 on Orangepiwin platform - every time screen is blank (monitor not active). Monitor connected over hdmi to vga adapter. After linux kernel is loaded - monitor is alived. I try some options in boot.scr withnout effect for u-boot: video-mode=sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=1 video-mode=sunxi:1024x768-24@60,monitor=dvi,hpd=1,edid=1 video-mode=sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0 and setenv console=tty0 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1024x768p60 Need help. 0 Quote
stalker37 Posted August 14, 2020 Author Posted August 14, 2020 FULL Output of u-boot with "setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0" U-Boot SPL 2020.04-armbian (May 30 2020 - 18:45:19 +0200) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.3(debug):dd1eb34-dirty NOTICE: BL31: Built : 18:45:06, May 30 2020 NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689) NOTICE: BL31: Found U-Boot DTB at 0x4089d60, model: OrangePi Win/Win Plus INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP803 on RSB INFO: PMIC: dcdc1 voltage: 3.300V INFO: PMIC: dcdc5 voltage: 1.500V INFO: PMIC: dcdc6 voltage: 1.100V INFO: PMIC: dldo1 voltage: 3.300V INFO: PMIC: dldo2 voltage: 3.300V INFO: PMIC: dldo4 voltage: 3.300V INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 843419 was applied INFO: BL31: cortex_a53: CPU workaround for 855873 was applied NOTICE: PSCI: System suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2020.04-armbian (May 30 2020 - 18:45:19 +0200) Allwinner Technology CPU: Allwinner A64 (SUN50I) Model: OrangePi Win/Win Plus DRAM: 2 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Card did not respond to voltage select! In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface7 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 2 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 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 3098 bytes read in 4 ms (755.9 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 153 bytes read in 2 ms (74.2 KiB/s) 39702 bytes read in 10 ms (3.8 MiB/s) 3821 bytes read in 7 ms (532.2 KiB/s) Applying kernel provided DT fixup script (sun50i-a64-fixup.scr) ## Executing script at 44000000 11888744 bytes read in 986 ms (11.5 MiB/s) 17162752 bytes read in 1420 ms (11.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11888680 Bytes = 11.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 EHCI failed to shut down host controller. Loading Ramdisk to 494a9000, end 49fff828 ... OK Loading Device Tree to 0000000049436000, end 00000000494a8fff ... OK Starting kernel ... 0 Quote
jernej Posted August 16, 2020 Posted August 16, 2020 To enable HDMI in U-Boot for any A64 board you have to first enable DE2 driver in config file and then somehow enable voltage regulator responsible for HDMI power (this is main reason why it's not currently supported). U-Boot doesn't have AXP803 driver. Probably easiest way would be to modify ATF. 0 Quote
stalker37 Posted August 29, 2020 Author Posted August 29, 2020 DE2 is enabled already: === stalker@lab:~/BLD/u-boot$ fgrep DE2 .config CONFIG_SUNXI_DE2=y CONFIG_VIDEO_DE2=y === Hmm. https://linux-sunxi.org/U-Boot#Setting_u-boot_environment_variables says that HDMI is supported on this platform and https://docs.armbian.com/Hardware_Allwinner/ == U-Boot supports HDMI and LCD output on Allwinner sunxi SoCs === 0 Quote
stalker37 Posted September 1, 2020 Author Posted September 1, 2020 I don't have enough experience to modify ATF. Thanks for the consultation! 0 Quote
valant Posted January 9, 2021 Posted January 9, 2021 On 8/16/2020 at 9:46 AM, jernej said: To enable HDMI in U-Boot for any A64 board you have to first enable DE2 driver in config file and then somehow enable voltage regulator responsible for HDMI power (this is main reason why it's not currently supported). U-Boot doesn't have AXP803 driver. Probably easiest way would be to modify ATF. but it worked with Armbian 5.83. it even did support UEFI GOP. there were issues with storage reads, when using uboot's UEFI so I updated... finding no HDMI at all. could someone point the latest version (minimal, without desktop) of Armbian, where HDMI support in uboot is still there? 0 Quote
stalker37 Posted January 9, 2021 Author Posted January 9, 2021 7 hours ago, valant said: but it worked with Armbian 5.83. it even did support UEFI GOP. there were issues with storage reads, when using uboot's UEFI so I updated... finding no HDMI at all. could someone point the latest version (minimal, without desktop) of Armbian, where HDMI support in uboot is still there? HDMI on my platform (Orange Pi Win/ Win Plus) worked only after linux kernel is loaded... at version 5.83 too 0 Quote
jernej Posted January 9, 2021 Posted January 9, 2021 @valantissue is more complicated than just some config option. Currently U-Boot doesn't support voltage regulators and rely on ATF to enable them (A64 has HDMI voltage supply pin). Logic in ATF will turn on all referenced voltage regulators, which is mostly fine. Issue is in word "mostly" - this logic will prevent ethernet PHY to power on correctly on OrangePi 3. Distros must decide what is lesser evil for time being, having no HDMI and ethernet in U-Boot or having no ethernet in Linux on OrangePi 3 (I didn't check what Armbian does exactly). Situation was discussed with maintainers and consensus is to implement voltage regulator driver in U-Boot, but that will take time. In the mean time, ATF could be updated with a improvement, which would temporary solve both situations, but I didn't find any patch for that yet. 1 Quote
stalker37 Posted January 9, 2021 Author Posted January 9, 2021 Path for AXP803 driver in present in suse linux https://build.opensuse.org/package/show/home:duwe:Teres-I/u-boot 0103-Add-AXP803-PMIC-support.patch 0 Quote
stalker37 Posted February 16, 2021 Author Posted February 16, 2021 Are there any changes on this issue? 0 Quote
stalker37 Posted September 5, 2021 Author Posted September 5, 2021 Patch for support AXP803 driver available from OpenSuse: https://build.opensuse.org/package/view_file/home:duwe:Teres-I/u-boot/0103-Add-AXP803-PMIC-support.patch?expand=1 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.