All Activity

This stream auto-updates     

  1. Past hour
  2. It was never publicly available AFAIK. However, you can download i.MX8 documentation which has small overview of this core and registers description.
  3. true, would that then "just work"?
  4. Interesting find. They seem to talk about filling up a "form" to get more informations, but I can't find that form. Do you know if the hardware decoder documentation is still available on this site ?
  5. Today
  6. From the media script thread: Chromium is unusable right now. I'm having to use Firefox.
  7. I'm using the 5.75 image which comes with the 4.4 kernel, updated everything with "apt update -y && apt upgrade -y && apt dist-upgrade -y" and I installed system, chromium and mpv. mpv works fine.. however; chromium states: Flash Stage3D: Software only. Hardware acceleration disable And others too. it's slow and can't load youtube videos at 480p.... what next? EDIT: Yes, I ran the script and installed system, mpv and chromium. chromium under "chrome://gpu" states that it IS software only and not HW accelerated.....
  8. You can also purchase some USB-BT dongle ...
  9. nah, I'll wait. I basically "need" BT to use it to switch on some BT-light strips. And I can still do that with my phone, works. So for me, I'll wait.
  10. Maybe later ... I don't want to get indigestion doing too much branch switching ...
  11. There is also VP9 decoding IP core , which is present in Allwinner H6, NXP i.MX8 and I think Rockchip has it too. It may be connected to Hantro and Google, but I'm unsure who is the original author.
  12. SPI Update done ! Now working perfectly ! I've booted my USB dongle without any eMMC or SDCard ... Many Thanks !
  13. Wow i didn't know that the vpu had an independent manufacturer. Gonna read more info about the hantro
  14. Yes, I've seen this behavior. By the way, connect the image with the kernel 5.1 and you will see the work of the monitor\TV with the message of the reason that it was not possible to mount the root system. Piteboot will even show the available system on USB\SD (if they have the correct "boot.ini" from which it tries to read and form its startup script). By the way, on the old version of Piteboot (20190202) I normally started systems from SD card in u-boot SPI mode.
  15. @kostap Thank you very much ! @Anders Please find the updated bootloader here (u-boot is unchanged; WTMI is updated to 18.12.1) - it works fine on my V5_0_1 EspressoBin ( It should solve the stability issues ... Edit: the recovery images are also updated: sata-images and uart-images
  16. It is even trying to boot a kernel present in the Flash : Thanks ! I will proceed to SPI Update ... I will post results later ...
  17. Nope. The easiest way would be to wait until Linux 5.2 is released and the sunxi64 dev branch will be switched. Or you get lucky and @martinayotte wants to spare some free time to play around with the pre-5.2 sources.
  18. What version does Piteboot write after running at the top of the screen ? update to lates version
  19. I've tried again, but no, it still doesn't work. It seems a different U-Boot present in SPI which doesn't check keystrokes ...
  20. Yes, you're right, thanks for clarifying.
  21. Hello. I start this thread here because in not start it in 3399 forum section. I wanted preempt-rt kernel for my armbian rockpro64 so i have compiled and generated preempt-rt 4.4.167 deb kernel package. I have installed my custom kernel deb package but after reboot the system boot in old kernel not the custom kernel. How i can set the system to boot from custom installed kernel ?(4.4.167-rt176 is my custom kernel) s# ls -a /boot . boot.cmd dtb-4.4.174-rockchip64 .. boot-desktop.png Image uInitrd armbianEnv.txt boot.scr initrd.img-4.4.167-rt176 uInitrd-4.4.167-rt176 armbianEnv.txt.out config-4.4.167-rt176 initrd.img-4.4.174-rockchip64 uInitrd-4.4.174-rockchip64 armbian_first_run.txt.template config-4.4.174-rockchip64 .next vmlinuz-4.4.167-rt176 boot.bmp dtb vmlinuz-4.4.174-rockchip64
  22. I have updated the 18.12 branch with patches from current development stream. Please check if it improves the stability.
  23. These boards are using MAC addresses defined in u-boot environment. They are usually not updated by the manufacturer of the evaluation platform. You can replace them by defining the following variables and issuing "saveenv" afterwards: ethaddr=00:51:82:11:22:00 eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ...etc.
  24. Is there a newbie friendly way to do that? Or can you link me to a simple guide or a search term?
  25. If u-boot is present, these images can be run on any hardware where it is missing or corrupted, or there is a desire of the user to use the new version of u-boot-2019.
  1. Load more activity