civic9
-
Posts
7 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by civic9
-
-
I also need to understand if Xorg driver for Mali450 exists an if it is working. Or only framebuffer is usable?
Why I'm not able to run a configuration giving me 1920x1080?
Why regular desktop env can't start the X session with high resolution and hw acceleration?
I have tested image from odroid-c2 with small adaptation under s905 and it is working for me - X on 1920x1080, works quite nice (however it is not like even cheap PC intel desktop).
I am not sure if it will be the same for s905x but they are quite similar (from cnx-software.com: "Amlogic S905X being an upgrade of Amlogic S905 with the same quad core Cortex A53 cores and Mali-450MP GPU but adding VP9 hard ware decoding, HDR support, and integrating 10/100 Ethernet PHY and audio codec").
Driver for Mali450 exists and it is working - but please note that it is for 3d acceleration only, which is used by e.g. kodi and games (and chrome can use 3d acceleration, but i am not sure what it gives to us).
2d operations like e.g. moving windows are not accelerated and probably wont be because mali is pure 3d engine.
You can find more info about these topics on odroid c2 forum.
-
The next update of images. The main change is in the way has a new version of u-boot supports 2 GB of RAM.
I see that you have changed CONFIG_DDR_CHANNEL_SET, CONFIG_DDR_SIZE and CONFIG_NR_DRAM_BANKS.When I had problems with amlogic u-boot on my beelink mxiii (s905, 2gb ram) I have compared ddr configuration structures with original firmware binary - and I found they set CONFIG_DDR_CHANNEL_SET to CONFIG_DDR0_RANK01_DIFF (btw, but they didn't changed neither DDR_SIZE to 2048 nor NR_DRAM_BANKS to 2, linux see 2GB without it, only CONFIG_DDR0_RANK01_DIFF is required), what you did, but it also looks they are using in board/amlogic/gxb_p200_v1/firmware/timing.c ODT (on-die termination) 60OHM for DDR3 (default in amlogic sources is 120OHM):#if (CONFIG_DDR_TYPE == CONFIG_DDR_TYPE_DDR3)#define CFG_DDR_DRV DDR3_DRV_40OHM//#define CFG_DDR_ODT DDR3_ODT_120OHM#define CFG_DDR_ODT DDR3_ODT_60OHMI am not sure if it is required but maybe it can affect stability? boots ok with both values, but I didn't test them for longer period of time - but I have seen at least one kernel crash with 120ohm (then changed to 60). -
@balbes150: do you consider integrating your work (for s9* at least) with armbian official repositories (making pull requests, etc.)?
-
Ok, it was quite simple. Working sample s905_autoscript (static configuration, dhcp should also work):
setenv m "1080p50hz" setenv hpd "false" setenv mbpp "32" setenv bootargs "root=LABEL=rootfs rootwait ro console=ttyS0,115200n8 console=tty0 no_console_suspend hdmimode=${m} m_bpp=${mbpp} net.ifnames= 0 fsck.repair=yes elevator=noop disablehpd=${hpd} consoleblank=0 hdmitx=cecf" setenv boot_start booti 0x11000000 0x13000000 0x1000000 setenv ethaddr C0:12:34:56:78:90 setenv ipaddr 192.168.1.231 setenv serverip 192.168.1.248 tftp 0x13000000 uInitrd tftp 0x11000000 Image tftp 0x1000000 dtb.img run boot_startNow I can change kernel/initrd/dtb images without moving sd card to another device
I will probably change root to NFS too.
It should be faster ans safer than sd cards..
-
Is it possible to load kernel/initrd/dtb from tftp server using s905_autoscript on sdcard? (using factory or custom build uboot)
It would be handy for development and testing. I don't have UART connected so I have small chance to blindly prepare appropriate images for tftp and s905_autoscript.
-
Amlogic-s905x image for odroid C2 works quite good with other s905 devices. I am testing it with beelink mxiii (s905) now.
But there are some minor issues like this one - https://github.com/igorpecovnik/lib/issues/570- manual corrections to the image may me needed.
And like zador-blood-stained commented it will be fixed eventually.
ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)
in General Chat
Posted
So it is no purpose to include uboot builds into (your) images, imho, and you said that your images will be using new uboot. It can be even dangerous - if one will copy such uboot, with wrong ddr settings into internal emmc - tv box can be bricked, because uboot with incompatible ddr settings will be booting from emmc (so such box will not boot from sd card anymore), but wont be able to boot any operating system (this happend to me by using uboot compiled from amlogic sources; it was starting and executing scripts, even tftp was working, but neither android nor linux could be started successfully). Then only amlogic burn tool can help, but it is sometimes hard to do (windows required, problem with connections and drivers, etc).