Jump to content

pro777

Members
  • Posts

    42
  • Joined

  • Last visited

Everything posted by pro777

  1. It looks like the burn failed. Apparently, this is why the firmware from the SD card does not start.
  2. Did you manage to record the Miniloader on EMMC?
  3. Try the firmware with Android Pie for XT-Q8L-V10, which can be loaded from the SD card from the Russian forum 4PDA. True, here you need to write the Miniloader to the EMMC. P.S. You can also try installing Android Pie for XT-Q8L-V10 to EMMC.
  4. @jock Thank you for your utility. I noticed one drawback. I work in Windows 10, which does not mount the FAT partition of your image. I guess this is due to the block size of the FAT partition in 4096 bytes. In Windows 10 a block size of the FAT partition is supported at 8192 bytes and above.
  5. That's right. I have a problem with receiving EDID data through I2C5.
  6. Hi @jock! Thanks for the new image. It loads stably without any errors. True, an error appears during shutdown, dmesg output attached.
  7. @jock, I noticed that the HDMI monitor does not turn on at the start of Uboot and there is no mention of the DRM driver. The Uboot 2020.04 version in this firmware.
  8. Great, @Jock. Can I get a link to your Uboot image with the DRM driver?
  9. jock, it seems DRM Uboot driver appeared: I'm testing tinkerboard android 8.1 firmware, the hdmi screen turns on at the loading stage of Uboot. I use the miniarm device tree. Also, look at the following nodes in the device tree (found from miniarm dtb for android): From dmesg:
  10. Jock, lol, can you give a link to your Ubuntu Focal and kernel 5.5.17?
  11. jock, do you have the opportunity to publish the latest images with Armbian from your repository?
  12. jock, very thanks for Ubuntu 18.04 with LTS 5.1.7 kernel! Great work! How are things going with video and audio playback?
  13. Maybe Sorm means the link above? Then it's no secret
  14. Fine news! You are well done! Thanks! There will be time, I will tested.
  15. No OpenGL/EGL/GLES X11 drivers available at this time for S912 SoC. Hardware rendering via GLES fbdev, as well hardware decoding video and audio is used in the player c2play. Look at this message.
  16. At the moment, unfortunately, I'm not ready to do it yet. But it is possible to assemble the missing packages in the form of archives.
  17. Hello everybody! I assembled a video player c2play, created by crashoverride, with the possibility of hardware decoding and rendering for a boxes on the S912 SOC. To achieve this, was used EGL and GLES libraries from Android, libhybris, libamcodec and ffmpeg with the support of the above library, as well kernel package with Mali driver for T820 GPU. All this was integrated into the firmware of Ubuntu Armbian 16.04 Mate Desktop, building by balbes150. You can download this firmware from here. c2play perfectly playing, both local and network video H.264 and H.265 10-bit, checked up to 4K. Declared support of MP4, MKV and AVI containers. A small help to managing the c2play from the keyboard: ESC - to finish playing, LEFT - 30 sec. back, RIGHT - 30 sec. forward, DOWN - 10 min ahead, UP - 10 min. back. SPACE - pause. To play video, open the terminal window or go to the virtual console (Ctrl-Alt-F1). enter the command: c2play <path to your video>. Or, assign c2play as the default application for the desired file type. More details here or here. In the folder /opt are deb-packages with libhybris and kernel 3.14.29 with the driver Mali. For those who want to build c2play itself, I bring links to resources on the github. Libhybris: https://github.com/libhybris/libhybris. Libamcodec: https://github.com/osmc/libamcodec. FFMPEG: https://github.com/roman-rybalko/FFmpeg-aml. c2play: https://github.com/OtherCrashOverride/c2play.
  18. It seems that kodi and mpv need to be build from the source.. To activate hardware acceleration OpenGL ES in Debian download this firmware and deb package of libhybris for Debian. Follow the instructions listed in my post above.
  19. To obtain the hardware acceleration OpenGLES fbdev on the S912 platform, do the following: - Download the firmware of Armbian 5.44 Ubuntu Mate with the kernel 3.14, created by balbes150. - Burn the loaded image on the SD-card and and run Ubuntu Mate from the SD card. - Download the archive with the kernel 3.14 packages with the Mali driver and the archive with Mali samples and libhybris package. Install all deb packages with the 3.14 kernel from the archive. To do this, go to the unzipped folder aml-s9xx-kernel-3.14.29-with-mali-r16p0-debs, run the command: sudo dpkg -i *.deb. - Unzip the mali-hybris-s912-packages.tgz. Copy the folder etc to the root of ROOTFS partition to set permissions for the mali and ion devices, and also for configuring ld for libhybris. - Unzip the system.tgz and copy the contents to the root of ROOTFS partition (sudo tar xzvf system.tgz -C / ) - Unzip Mali-OpenGL-ES-Samples-Linux-Arm-Bin.tgz in the home directory. - Reboot system. - After reboot the system, add the armhf architecture for the system: sudo dpkg --add-architecture armhf sudo apt update sudo apt install libc6:armhf libstdc++6:armhf - Install libhybris-arm_0.1-1-opt_arm64.deb package and configure ld: sudo ldconfig. - Everything is ready for the test, run: /opt/libhybris/bin/test_glesv2. A picture should appear, as shown in the first screenshot. - To run Mali OpenGLES Samples, go to the Mali-OpenGL-ES-Samples-Linux-Arm-Bin folder and start the executable files. - Freeze the kernel update with the armbian-config.
  20. I managed to get the hardware acceleration GLES fbdev on KM8P S912 using libhybris! How to do this, I will write later.
  21. Hi everyone, I'm working on the task of using the fbdev GLES driver from Android 7.1.1 with the help of Libhybris for my KM8P on S912 for Armbian Ubuntu (Debian). In the framework of this task, I managed to build an legacy kernel 3.14.29 with the Mali driver r16p0. And also the mainline kernel 4.18-rc2 with the Mali driver r19p0. You can download the deb packages for the system update by clicking on the links above. For a start, it's enough to install the corresponding package linux-image-amlogics905x_5.44_arm64.deb for update of the system and also put mali.conf (taken from the LibreElec distributive) in the directory /lib/modprobe.d/ from the archive. sudo dpkg -i linux-image-amlogics905x_5.44_arm64.deb After the system with the 3.14 kernel is upgraded, the device /dev/mali0 appears. Unfortunately, this did not happen for the mainline kernel. It seems that the reason is that there is no description of the GPU in the device tree. I'm use gxm_q201_1g.dtb. Next, I build a package of Libhybris from git. For the 64-bit version, I used the following commands: git clone https://github.com/libhybris/libhybris cd libhybris/hybris git clone https://github.com/Halium/android-headers/ -b halium-7.1 ./autogen.sh \ --prefix=/opt/libhybris \ --build=aarch64-linux-gnu \ --host=aarch64-linux-gnu \ --target=aarch64-linux-gnu \ --with-android-headers=android-headers \ --enable-adreno-quirks \ --enable-mali-quirks \ --enable-debug \ --enable-trace \ --enable-arch=arm64 \ --enable-experimental \ --with-default-egl-platform=fbdev \ --with-default-hybris-ld-library-path=/vendor/lib:/system/lib To build the 32-bit version of Libhybris I installed two packages for cross-compilation: arm-linux-gnueabihf-gcc and arm-linux-gnueabihf-g++. And compiled with the following parameters: CC=arm-linux-gnueabihf-gcc \ CXX=arm-linux-gnueabihf-g++ \ ./autogen.sh \ --prefix=/opt/libhybris \ --with-android-headers=android-headers \ --enable-adreno-quirks \ --enable-arch=arm \ --enable-experimental \ --with-default-hybris-ld-library-path=/system/lib \ --enable-debug \ --enable-trace \ --with-default-egl-platform=fbdev \ --enable-mali-quirks Next: make -j8 sudo make install Then copied the /system/lib directory from the Android firmware to the root of the file system. Running /opt/libhybris/bin/test_glesv2, unfortunately, failed: user@amlogic:/opt/libhybris/bin$ ./test_glesv2 library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it test_glesv2: test_glesv2.c:117: main: Assertion `eglGetError() == EGL_SUCCESS' failed. Aborted For some reason, the system could not create a surface, test_glesv2.c, s.117: surface = eglCreateWindowSurface((EGLDisplay) display, ecfg, (EGLNativeWindowType)NULL, NULL); assert(eglGetError() == EGL_SUCCESS); assert(surface != EGL_NO_SURFACE); I hope that someone will be interested in this task and will achieve a better result.
  22. Thanks, jock. Unfortunately, this did not change the situation. I also tried to increase the frequency on i2c5 to 400 KHz - there were no messages about the timeout, but on the whole, nothing has changed dramatically.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines