All Activity

This stream auto-updates

  1. Today
  2. Moved to Common issues / peer to peer technical support
  3. Yesterday
  4. Hi to everyone, I'm a newbie in using python for sensors and pins, so I'm using Orange Pi Lite (h3) and i installed pyA20 but i can't find mfrc522 library ( i mean that code we import, my English is not very good ) that use pyA20, so is there any library you know? Or i have to make one? And if i have to make one, would you please help me with basics? Thanks 🙏
  5. @ArkhanLK - i played around with an h313 x96q box - it was working as well as a h616 box, but maybe the h313 are the lower quality ones as i was not able to reach as high cpu clocks with it like with h616 and it also got hotter - so maybe h313 are the lower quality binned versions of the h616 (similar to rk3318 vs rk3328 for rockchip) best wishes - hexdump
  6. In theory, yes. As long as it has DDR3 RAM (no other RAM type is supported currently). Not to my knowledge.
  7. Slightly off-topic... I am running armbian from external SSD. I have only u-boot flashed in the internal eMMC. Now I would like to try the new Android version - just to see what is this.. :-) Is possible to flash the new Android to the SD card and run it from here? I wouldn't to harm flashed U-boot in eMMC...
  8. Hello! I know this is for H616 and things are on early stages... But I read somewhere that the H313 is the same chip as H616, so I am wondering: would the images and procedure for H616 work on a H313 board? I don't have one yet to test, but I am planning on getting and trying. Just wondering if someone else has done it. Thanks and best!
  9. Hi, is it possible to turn off wifi and bluetooth, to save energy ?
  10. Hi. Around a month ago, my Rock 3A arrived and I got to playing with it. I noticed that there was a community build configuration for it, so I set up an Armbian build environment and got to building it. The image built without error and before I knew it my device had booted. However, since then, a few changes have been made to the Rock 3A (including receiving a proper Armbian maintainer), and now it seems to be completely broken. This issue seems to be reproducible, with people both being able to boot the board with old images as well as not being able to boot with fresh images. There seems to be some work happening towards fixing u-boot (which seems to be the issue) on GitHub, but it has been completely silent for almost two weeks. I realize that stuff like this takes time, as well as the fact that all of this work is community-driven. My main goal for asking this is so that I can contribute to the development for this board myself. I can't tell why booting this board isn't working from boot logs (available throughout this thread on the Radxa forum), so I'm largely at the mercy of those more knowledgeable about this part of Armbian and Linux than I am. Any and all info would be greatly appreciated. Thanks.
  11. Well, putting the image for rk322x on rk3318/28 is definitely not a smart move. Never tried myself, now we know it definitely bricks the board I bet your only chance is to go with maskrom mode, you have to find the eMMC clock pad on your board and put it to ground. edit: ah, about videos in chromium, they will be choppy until a lot things required for multimedia are squared out. Can be next year or can be never, surely accelerated video in browsers is a complex task.
  12. I will sell my helios64. never got a chance to use it as i went with a pc for server.
  13. Moved to Common issues / peer to peer technical support Your system is WAY outdated. Support for stoneage 3.4.y has been dropped almost two years ago. Also Xenial is no longer supported.
  14. Added to the armbian-config refactoring plan:
  15. VOP is Video Output Processor, the term Rockchip uses for the display subsystem. Its resources are exposed through the KMS/DRM framework. The rk3399 even has two of them (vopl and vopb in DT) In a virtual console you use it e. g. via GBM. No 3D accelerator involved for standard video playback. In Xwindow/Wayland, the display subsystem is occupied by the server, so an application must forward video content to it and cannot directly access KMS/DRM. Xorg uses the modesetting driver which emulates all 2D action via 3D accelerator (glamor) and transmits all results via dumb buffer to KMS/DRM. This prevents the use of specific acceleration features of the display subsystem. In Wayland world this is a completely different story. The DRM backend in Weston and the KWin Wayland compositor at least implement proper KMS/DRM API and make use of avilable display subsystem acceleration features. Thus, video content can be played without redirection via the 3D accelerator, as on a virtual console. Of course, the 3D accelerator, if it fits, is used for all graphic eye candy by the compositor. In IBM PC architecture world the modesetting way is the "right thing to do" (TM) as the GPU card also provides the scan out engine. Content uploaded to the GPU will never return to the CPU for display. The scan out is done direct in hardware from the GPU card. I get similar relatively rising values with the start of XvImageSink playback, but since the overall value fluctuates a lot, it's difficult to know which CPU cycles are really associated with video playback or are attributable to other desktop activities.
  16. Err:9 xenial/utils armhf Packages 404 Not Found Reading package lists... Done W: The repository ' xenial Release' does not have a Releas e file. I am getting above errors when trying to update. I have OrangePi One with "16.04.7 LTS (Xenial Xerus)" and "Armbian Linux 3.4.113-sun8i"
  17. And today we have geekbench v5 score from the same source. Its looks like chip is clocked 2.2/1.8GHz It looks promising, maybe even as a dailydriver ... Sent from my Redmi 4X using Tapatalk
  18. ssh won't work (you don't have an address to connect to), until you have a proper LAN connection, you can't use it (judging by the log, you don't have an IP address assigned to the LAN)
  19. Yes, this is the way to debug booting issues. All Armbian flavors share the very same kernel package so it is quite common if one does not work the others do not either.
  20. iamdrq

    Mainline VPU

    Oh, What is the VOP ? The auto negotiation selects XvImageSink(It has a window border better than waylandsink,glimagesink) that renders video frames to a drawable (XWindow) , but I use wayland it start a xwayland do it that I think it cost something.I did some test on my device, the best way is glimagesink that 4K 30fps normal paly only around 18% cpu (but it 's strange that some 1080p video waylandsink better than glimagesink), and I found this gl way also work on browser like webkit.
  21. Last week
  22. Ciao Michele, Multitool already burns generic images on flash, whatever flash it is. stepnand procedure is for armbian only, because it carries u-boot SPL in place of rockchip miniloader. Also the rockchip nand driver prevents the access to very first sectors of the flash, hence there is the need for offset and gpt with stepnand procedure. Libreelec (legacy 4.4 kernel) carries the rockchip proprietary miniloader and thus can be burned on NAND using the regular "burn image to flash" menu option and it should work: multitool should suggest you to ignore to burn the bootloader sectors and you should answer yes. Beware that you need the image with legacy 4.4 kernel: mainline kernel images have no nand driver and will never boot from nand.
  23. aha maybe it's something to do with these lines [ o.k. ] Cleaning [ u-boot/quartz64-a ] [ o.k. ] Compiling u-boot [ 2017.09 ] [ o.k. ] Compiler version [ aarch64-none-linux-gnu-gcc 9.2.1 ] [ .... ] Checking out to clean sources [ o.k. ] Cleaning [ u-boot/quartz64-a ] [ o.k. ] Started patching process for [ u-boot station-p2-quartz64-a-legacy ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-station-p2 ] I need to remove some of 150balbes userpatches I guess
  24. Time for an update. I can compile u-boot for the quartz64. Instructions are here I can modify armbian build to download that same u-boot code and compile it That code is here however when I run in build I get this error CFGCHK u-boot.cfg Unsupported u-boot processing configuration! on investigation I found that build/cache/sources/u-boot/quartz64-a/u-boot.cfg is not the same as the u-boot.cfg if I compile u-boot directly from my own source outside of the armbian build scripts. I don't yet understand why.
  25. Nice job! Have you released the design files, or any means to buy your adapter? Do you have any tips on booting from the external SSD?
  26. Hi, I thought I'd share this in case anyone else is in the same situation as I. I've been trying to get my Orange Pi Lite to boot the latest (Aug 26 2021) images. I've tried Focal, Bullseye and Hirsute, and the Lite doesn't seem to care for any of them. "Armbian_21.02.1_Orangepilite_buster_current_5.10.12_desktop" from the Archive section does boot, as do the versions of Ubuntu and Debian from the Orange Pi website. Perhaps if I had a serial terminal connected I would be able to troubleshoot this, but I don't yet. I'm using a Sandisk Ultra A1 64Gb and I'm monitoring my power supply with my oscilloscope and haven't noticed any dips below 5v.
  27. Hi all, I've a box with rk3228b, nand, ddr2 etc etc and I'm using it as mediacenter with Libreelec 9.2 installed on sdcard. The box recognize the nand, but I had never been able to install the operating system in it (tried with rkdeveloptool, dd and others but without succes). Until today, when I've discovered this beautiful tool called multitool I had to make a few small changes (basically removed offset and gpt creation in the nand flash code), but it works great. So my question is, it's possible to add an option to write a generic image, in order to make this tool more useful!? Last question, I think that the libreelec bootloader has some trouble when boot from NAND, but it's strange, because I've readed that the multitool one shoud be the same. It's true, or there are some changes that I can apply and retry?! Thanks for your hard work. Michele
  1. Load more activity