sunzone

Latest kernal seems to have solved the problem. I checked with 4.13.10. and CLK behavior was similar but Chip Select works properly. But I encountered with another SPI problem. When I use SPI, most of the times SPI is stable. But some times it becomes unstable. Does anyone encounter with unstable SPI? Stable/Unstable SPI status continues to last from from the boot to the next boot. In other words if SPI is unstable, by booting/restarting again SPI can be turned to stable sometimes; vise versa. After boot, if SPI is stable it continues to be stable till next boot ; vise

Ohhhh I see. Thank You very much for the help. I think I am going to write a script to reboot if resolution set to fallback resolution. Thanks again

Any idea where general DRM code might be located?

I am kind of in a hurry. @Igor @jernej is there any way to change the fall-back resolution somehow? If so, I can set fallback resolution to 800 x 480

I am using Orange Pi One with 4.13.10-sunxi image and a 5" 800 x 480 HDMI Display. As you mentioned EDID detection is automatic. But sometimes it fails to detect EDID and default resolution is set to 1024 x768 I need to the resolution to be 800 x 480 no matter what. I followed the advanced settings and fw_setenv video-mode sunxi:800x480-24@60,monitor=hdmi,hpd=1,edid=0 when I follow fw_printenv command it displays, video-mode=sunxi:800x480-24@60,monitor=hdmi,hpd=1,edid=0 But still sometimes(after multiple boots) resolution is set to 1024x768. This is a p

I'm on it. Thanks

I came across a spi clk problem with my Orange Pi One. A similar unanswered question has previously been asked for Orange Pi Zero, but I started a new topic because of the new board. I am using ARMBIAN 5.32.170913 nightly Ubuntu 16.04.3 LTS 4.11.12-sun8i Everything is set up properly and spidev0.0 is created and working. Following is my /boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 fdtfile=sun8i-h3-orangepi-one.dtb overlay_prefix=sun8i-h3 rootdev=UUID=a2df1e68-90c9-46a0-ab26-169cb43e35c8 rootfstype=ext4 overlays=spi-spi

I am using GPIO(CON3) pins 8 and 10 for a project. In BPI M1+, functions for those pins are PH0 and PH1 respectively. https://bananapi.gitbooks.io/bpi-m1-bpi-m1-plus-/content/en/bpi-m1+_gpio_pin_define.html But, when I added overlays=uart3 ,I didn't work properly . When I checked the overlay file sun7i-a20-uart3.dtbo , by changing it to .dts , I figured out that this overlay file uses PG6,PG7 pins, not PH0,PH1 pins. So, to modify the configurations without adding uart3 overlay in the /boot/armbianEnv.txt file, I wanted to edit the /boot/dtb/sun7i-a20-bananapi-m1-plus.dtb

· Hello, So I tried to figure out the original dtb file used but the system by default when I boot the image without any fine configuration. But I couldn't find any information about the default dtb. I checked at /boot/boot.cmd , but nothing is mentioned for "setenv fdtfile" which was available in the old kernel. I figured out that I can add a suitable .dtb in the /boot/armbianEnv.txt in the following post. https://forum.armbian.com/index.php?/topic/4817-banana-pi-m1-extra-configuration/ fdtfile=sun7i-a20-bananapi-m1-plus.dtb But there is no way to