Digitalman1983
-
Posts
10 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Digitalman1983
-
-
Good catch....
"git checkout v2015.04 -b tmp" should be "git checkout v2020.10 -b tmp"
-
Thanks for that, Gediz,
In looking at the Olimex forum post https://www.olimex.com/forum/index.php?topic=4463.0 regarding the A13, as well as http://linux-sunxi.org/LCD it would appear that the CONFIG_VIDEO_LCD_MODE is indeed part of the configuration for U-Boot, which requires U-boot to be custom built:
git clone git://git.denx.de/u-boot.git
cd u-boot/
git checkout v2015.04 -b tmphttps://developer.arm.com/-/media/Files/downloads/gnu-a/9.2-2019.12/binrel/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz
tar -xvf gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- a64-olinuxino_defconfig
make menuconfig
This allows the configuration of U-boot where the LCD can be properly enabled.
I'm working on the next step, which is properly linking the compiler to build the U-boot image, as well as adding a user patch to armbian build tools to allow use of the custom U-boot binary. Stay tuned.
-
Has anyone had any luck getting the LCD working on newer kernels?
-
Has anyone had any luck getting the LCD working on newer kernels?
-
One additional comment,
I noticed according to the hardware notes in armbian docs that CONFIG_VIDEO_LCD_MODE must be enabled in kernel configuration.
I just checked my kernel configuration and that option does not exist.
-
LCD support does not appear to be working in the latest builds (stable kernel 5.8.6, development kernel 5.9.7)
My understanding is that this has been an issue for a while with A64 boards, specifically the Pine64, but that it was working at one time.
Here's what I've tried so far:
-Followed instructions at https://docs.armbian.com/Hardware_Allwinner/ and added "setenv video-mode sunxi:480x272-24@60,monitor=lcd,hpd=1,edid=1" to boot.cmd and put "saveenv" at the end, re-compiled boot.scr
-Did a modprobe of panel-olimex-lcd-olinuxino
-Rebooted several times
-Ensured that LCD jumper was closed and verified LCD was working with Olimex builds.
Screen flickers at startup then stays white.
Any thoughts?
-
Levent Erenler thanks so much for sharing your discovery!
I was able to get audio working on my Lime-A64 using the provided overlay.
-
On the 20.08.2 Buster release (Kernel 5.8.6) the headphone jack is not currently working.
HDMI audio seems to be supported.
aplay -L returns only the HDMI audio interface. (sun50i-a64-hdmi) but is not showing the headphone interface (should additionally show sun50i-a64-audio as in other working builds)
This is also the case with the current development build (Armbian_20.11.0-trunk.32_Lime-a64_buster_current_5.9.7)
A look at the device tree shows “<stdout>: Warning (unit_address_vs_reg): Node /sound/simple-audio-card,dai-link@0 has a unit name, but no reg property” on the first line of the DTS of sun50i-a64-olinuxino, sun50i-a64-olinuxino-emmc, and sun50i-a64-olinuxino-2Ge8G device tree blobs. Not sure if this is a contributing factor.
The snippet it seems to be complaining about:
simple-audio-card,dai-link@0 {
format = "i2s";
frame-master = <0x11>;
bitclock-master = <0x11>;
mclk-fs = <0x80>;I did some digging and found this patch from a few years ago: https://www.alsa-project.org/pipermail/alsa-devel/2018-October/141047.html
The only major difference I see between the configuration added by the patch and my current device tree is that hex addresses are specified in place of pointer variables. (i.e. <0x12> vs <&dai>Going on the advice of several forum posts, I tried adding "overlays=analog-codec" to /boot/armbianEnv.txt to no avail.
I suspect that analog audio needs to be enabled in kernel configuration.
-
I am having this issue as well, and as far as I can tell, it has not been resolved yet.
Can anyone confirm whether there is a newer release than the Olimex/Armbian release with kernel 5.2.5 where USB/eMMC are functional?
Armbian Donations
in Off-topic
Posted
Wow that was quick! I didn't even have a chance to kick in....so what's next ?