All Activity

This stream auto-updates     

  1. Past hour
  2. Maybe later ... I don't want to get indigestion doing too much branch switching ...
  3. 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.
  4. SPI Update done ! Now working perfectly ! I've booted my USB dongle without any eMMC or SDCard ... Many Thanks !
  5. Wow i didn't know that the vpu had an independent manufacturer. Gonna read more info about the hantro
  6. 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.
  7. @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 (https://pastebin.com/xJCtLXsH). It should solve the stability issues ... Edit: the recovery images are also updated: sata-images and uart-images
  8. It is even trying to boot a kernel present in the Flash : Thanks ! I will proceed to SPI Update ... I will post results later ...
  9. 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.
  10. Today
  11. What version does Piteboot write after running at the top of the screen ? update to lates version https://wiki.odroid.com/odroid-n2/os_images/petitboot
  12. 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 ...
  13. Yes, you're right, thanks for clarifying.
  14. 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 System.map-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 System.map-4.4.167-rt176 vmlinuz-4.4.174-rockchip64
  15. I have updated the 18.12 branch with patches from current development stream. Please check if it improves the stability. https://github.com/MarvellEmbeddedProcessors/A3700-utils-marvell/commits/A3700_utils-armada-18.12
  16. 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.
  17. Is there a newbie friendly way to do that? Or can you link me to a simple guide or a search term?
  18. 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.
  19. My RockPro died yesterday ... I had my office window opened, a sudden windy storm started, some rain drops bumped onto my desk, the RockPro was to near of that area ...
  20. Gathered and checked the startup script of the system Armbian kernel 4.9. Everything works. Scripts on the site are marked according to the kernel used. Before using these scripts on existing systems, be sure to rename them correctly after writing to USB media. The file name must be boot.scr. In the new images Armbian 5.87 these scripts are already in both versions of the images and not to add in the is not necessary. When you start the system from an SD card or eMMC with a new u-boot , in the "boot.ini", you need to comment out or delete this line . if test "${display_autodetect}" = "true"; then hdmitx edid; fi
  21. OK, I will try it. Btw, what's the purpose of the u-boot writing step for other than libreelec/coreelec?
  22. Bluetooth is supported in my kernel. All you need is have firmware in /lib/firmware and then run: btmgmt public-addr 00:03:19:9e:8b:00 or some other address. After boot. How to get FW is described here: https://megous.com/git/linux/commit/?h=opi3-5.2&id=9c296799c4d3dd90986833cfded392098c1979bd (On orange pi 3 that is)
  23. For LibreELEC, this is possible.
  24. Hi, I got a Phicomm N1 TV Box, which is Amlogic S905D. I'm trying to build libreelec/coreelect for it. I saw there is a step in the build script to build and write the u-boot to the header of the output disk image. I don't understand the purpose of this step. In my understanding, u-boot is already in the NAND of the box. What's the purpose to write it into the disk image? Is this step needed for my device? Currently I can see these u-boot env variables with my device: start_autoscript=if usb start ; then run start_usb_autoscript; fi; if mmcinfo; then run start_mmc_autoscript; fi; run start_emmc_autoscript; start_emmc_autoscript=if fatload mmc 1 1020000 emmc_autoscript; then autoscr 1020000; fi; start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi; start_usb_autoscript=if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 1 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 2 1020000 s905_autoscript; then autoscr 1020000; fi; if fatload usb 3 1020000 s905_autoscript; then autoscr 1020000; fi; Is it OK if I skip the u-boot writing step and just put the s905_autoscript and other necessary files in the root of the disk image the burn to the sdcard? I just want it boot into the libreelec/coreelect on the sdcard.
  25. The result depends on the problem to be solved. In some tasks (terms of use) N2 is better and in others Khadas EDGE (RK3399) is better. To recommend something,you need to know the list of tasks and conditions of use. If you do not compile anything on the device, do not put extra packages, it can create unnecessary problems (if you do not understand their purpose). To update the kernel, you only need to install two packages "deb" "image"
  1. Load more activity