Jump to content


  • Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by MOHAMMAD HADI

  1. What other projects ? do you mean panfrost for Midgard and Bifrost GPUs ? or other projects for the Utgard GPUs ?
  2. AFAIK 3d acceleration works in X through the libmali provided by amlogic, Neil Armstrong has some instruction of how to get it working https://github.com/superna9999/meson_gx_mali_450 I didn't try it though. keep in mind that libmali.so is a mess, you have to use a certain libmali.so for X and another one for wayland or gbm, you can't have acceleration for the three of them at the same time. The best thing to do now is to wait for lima driver, which is a reversed engineered driver that will wok with mesa, so we will get rid of the libmali mess
  3. @balbes150 the images are missing some of the video decoder firmwares, the latest firmwares with the correct directory structure can be found here https://github.com/LibreELEC/meson-firmware/tree/master/meson
  4. Well. the Debian distro included is built by 150balbes and tested by hundreds of users, so I would say the problem is in the boot menu, of course you can add your distros and the included details above explain how to do that. Unfortunately I don't understand what's going on on your device without details, if you have a Uart cable you can attach it to the box and post the log to see what's going on. Regards
  5. sorry, no idea regarding this problem, did you try the debian distro ? Regards
  6. looking at https://discourse.coreelec.org/t/which-dtb-do-i-use/389 I see that there are two types of GT1 ultimate gxm_q200_2g and gxm_q200_3g, which one do you use ? anyway I modified and compiled both dtbs for you https://drive.google.com/open?id=1OZmXRInsRMlF0vCUtcuQlIMNjl-sSwMm https://drive.google.com/open?id=1HRKjoRZUgYoWvuKH97kmtxivIjXHBfrM use the correct one (that you normally use for Coreelec) also please note that these dtbs (with the modified remote driver) are only to be used in the recovery partition, don't copy it to your distributions (use the dtbs of your distributions instead) Regards
  7. what do you mean cannot complete installation? did you replace the dtbs? you need to replace the dtb file for each system with the appropriate one for your device, for example - for coreelec go into the directory multiboot/COREELEC and then copy the correct dtb for your device from the device_trees folder to the main COREELEC folder and name it dtb.img - for Debian go into the directory multiboot/Debian_Server-3/ and copy your dtb from the dtb folder into the Debian_Server-3 rename it to dtb.img You replaced the main dtb.img file in the fat32 partition ? where did you get your dtb file from ? if you got the file from Coreelec then you need to disable the meson-remote node in the dts file and enable the meson-ir node and then compile the dtb file, this is because amlogic devices have two drivers for the remote, Coreelec uses the meson-remote while I used the meson-ir for simplicity. If you don't know how to edit your edit and compile device trees just give me the name of the device tree that you used and I will compile it for you Regards
  8. Nice!! I never knew about the "go" command. but still, I can't boot for some reason, I just used "fatload" and then "go" gxb_p20x#fatload mmc 0 ${loadaddr} bootloader.bin reading bootloader.bin 4194304 bytes read in 334 ms (12 MiB/s) gxb_p20x#go ${loadaddr} ## Starting application at 0x01080000 ... "Synchronous Abort" handler, esr 0x02000000 ELR: 1080000 LR: 77edddf0 x0 : 0000000000000001 x1 : 0000000073eca148 x2 : 0000000073eca148 x3 : 0000000001080000 x4 : 0000000000000030 x5 : 0000000000000000 x6 : 00000000ffffffd0 x7 : 0000000000000004 x8 : 0000000000000031 x9 : 0000000000000000 x10: 000000000000000f x11: 0000000077f46798 x12: 0000000000000000 x13: 0000000000000000 x14: 0000000000000000 x15: 0000000000000000 x16: 0000000000000000 x17: 0000000000000000 x18: 0000000073ec3e28 x19: 0000000073eca148 x20: 0000000000000002 x21: 0000000001080000 x22: 0000000000000002 x23: 0000000077f73818 x24: 0000000000000000 x25: 0000000000000000 x26: 0000000000000000 x27: 0000000073eca1a0 x28: 0000000000000000 x29: 0000000073ec3930 Resetting CPU ... should I load the binary to a specific address other than the ${loadaddr} ?if so whats the correct address? Thanks
  9. Yes I know that part but you said it's possible to load the custom bootloader from the eMMC bootloader How ?
  10. Can you elaborate on this ? do you mean I have to modify the vendor bootloader on the eMMC to be able to chainload the sd card bootloader ? what modification do I have to make?
  11. Hi, I've compiled u-boot from source( I have the binary u-boot.bin.sd.bin file) now how can I boot this binary? I don't want to erase the vendor u-boot on the emmc and replace it with this, I want a way to boot into this binary for testing without writing it to emmc. Is this possible? My device is k2pro tv pro ( amlogic S905 SoC) Regards
  12. It's actually not that hard, there is already a tool to simplify things called reprepro, I can do this myself but you're the one providing the images, so you know when to update the packages. An easy tutorial to follow: https://www.tecmint.com/create-deb-pacakge-repository-in-ubuntu/ Besides, there are only four custom packages in your images linux-bionic-root-aml-s9xxx linux-dtb-aml-s9xxx linux-image-aml-s9xxx linux-u-boot-aml-s9xxx-default all other packages are from Armbian and ubuntu repositories so the repository will be very small and easy to maintain. The commands used to sign and upload packages can probably be scripted in Armbian build system so once you build the image the four custom packages will automatically be uploaded to the SourceForge repo. Regards
  13. @balbes150 We should make a repository for our custom packages and add them to apt lists, it doesn't make sense to reflash the image or manually downloading and installing deb packages every time the kernel gets updated, I think we can use SourceForge to host the packages for free.
  14. I've compiled the kernel successfully from Torvalds tree by using the next config instead of the default, I've applied Maxime v4l2-m2m patches and I get video decoder but it doesn't really work when playing files, as far as I can see it only works with FFmpeg when dumping raw frames.
  15. Hi, I'm trying to build a custom kernel and boot it using the rootfs provided by the Ubuntu_bionic_default_4.18.0 image. I compiled the kernel from torvalds tree (after applying the text_offset patch of course) and used your config (https://github.com/150balbes/Build-Armbian/blob/master/config/kernel/linux-aml-s9xxx-default.config) but the kernel get's stuck when it reaches userspace and after a couple of minutes I get these errors Do you have any Idea what's causing this ?
  16. @balbes150 Do you plan on adding libmali to the build? some nice instructions provided by Neil here : https://lists.infradead.org/pipermail/linux-amlogic/2017-June/004092.html
  17. Thanks, that fixed the issue to an extent. After some reading it seems like Xfce doesn't have the best support for HIDPI, big screens (mine is 55") and a better choice would be cinnamon or Enlightenment 18 Regards
  18. Hi, How can I scale up the whole DE ? I have a 4k screen and everything looks so small, increasing font DPI doesn't give very good results
  19. @balbes150 please use meaningful messages for your commits, putting the date in the commit message is not very useful, I noticed this in all of your repos
  20. I updated the image to support Ir remote so you don't need to use your keyboard
  21. I updated the topic with the new boot manager
  22. I'm talking about the meson-ir module, doesn't seem to be using a standard ir protocol.
  23. Yes, I've already built and loaded the remote modules, I also had to edit the meson-remote and meson-ir sections of the dtb(now I have an rc device under /sys/class/rc/rc0 ) the problem is with lirc, I can't set it up with the amlogic drivers, maybe amlogic is using a special protocol, every time I train lirc for the remote and then when I test the config It fails to recognize the buttons. Thanks
  24. @balbes150 regarding the wifi drivers of the ampak am6335 and the dvb drivers I've asked you about before, it turns out that for the wifi you don't need an out-of-tree driver, the wifi is already supported by the dhd module provided with amlogic's kernel, the problem is that for some reason the module is failing to detect the right path of the firmware to load so I'm getting this after modprobe dhd: [ 82.045326] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/brcm/.bin [ 82.045330] _dhdsdio_download_firmware: dongle image file download failed [ 82.045348] dhd_bus_devreset Failed to download binary to the dongle Anyways I solved it by passing the path manually to the module like so: modprobe dhd firmware_path=/lib/firmware/brcm/fw_bcm4335b0_ag note that I only tested this on the Debian stretch image running 3.14.29 kernel As for the dvb drivers they are out of tree and I had to compile the whole kernel to be able to load them without crashing the kernel, I hope that you can include them In your future releases. One last question: do you know how to configure lirc in linux for these boxes (ir remote)?Do I need to modify the dtb for it to work ? Thanks
  • Create New...