• Content Count

  • Joined

  • Last visited

Everything posted by nightseas

  1. Cool! I was just wandering if there had an Armbian build for i.MX8M then I saw your post. BTW: Do you know if there's any graphic support for i.MX8M? I'd like to try headless first and then move to HMI with LCD kiosk display. Thanks & BR.
  2. Really great work! Is there any way to select specific version of ARMBIAN to build? 5.36 for example. I could checkout the specific release tag, but the build scripts would always switch to master and build the latest version. Thanks & BR.
  3. I had a NanoPi NEO2 working well with ARMBIAN 5.34.171121. After apt-get upgrade, ARMBIAN has been changed to ARMBIAN 5.37.171208 with below firmware update: Get:1 xenial/main arm64 linux-dtb-next-sunxi64 arm64 5.37.171208 [25.0 kB] Get:2 xenial/main arm64 linux-image-next-sunxi64 arm64 5.37.171208 [14.7 MB] Get:3 xenial/main arm64 linux-u-boot-nanopineo2-next arm64 5.37.171208 [222 kB] Get:4 xenial/main arm64 linux-xenial-root-next-nanopineo2 arm64 5.37.171208 [318 kB] T
  4. What about an universal lib which is totally decoupled from HW platform, and with functions (SPI, I2C, UART, GPIO) separated? - It should be not only able to run on Allwinner SoCs, but also other - No kernel driver hacking or physical register access, only based on Linux userspace interface I did port the wiringPi last year. Both C and Python (Cython based) are supported. The only customizing needed is to fill in the GPIO number map (standard Linux GPIO number) and device number (SPI1, ttyS2 etc.) https:/
  5. You should better build your own image, with several configurations changed from rk3399-evb to firefly, such as dtb, uboot config...
  6. Thanks for the hints. Do I also need to install Rockchip DRM packages while testing glmark2?
  7. Attached is the full OpenCV 3.3.0 + OpenCL perf test report except video test part, which failed probably because of corrupted GLES. Just for your reference. x86_opencv_perf_reports_20170817.html
  8. I have made the initial support for RK3399. Currently working on GPU stuff.
  9. I tried to build libmali deb pack for RK3399 but failed. There's no instruction or guide, so I may need to ask Rockchip for help again. Then I manually linked the lib in /usr/lib and destroyed the the desktop GUI. After some experiment the desktop was back but still could not test gles2 as you suggested. The good news is, OpenCL works well. I'll do some OpenCV + OpenCL perf test and put the result here.
  10. The driver works fine so that is not a like a software issue. I have tested the SanDisk Ultra 8GB/16GB C10 cards and seen no such error. If the U-Boot shows no mmc1 device then it means the dwmmc controller doesn't detect anything, and I'm afraid there's something wrong with your hardware or SD card.
  11. Which kernel are you using? Kernel 4.4 from Rockchip official repo: If it's mainline Kernel from then which version is it? Other 3rd-party repo? There's a bug in the RK official u-boot, which is caused by missing dwmmc driver and leads to SD card boot failure.
  12. I asked the owner about the stock. There are less than 100 boards in stock and I see the correct quantity in system now. I'm not sure if I can help on ordering boards because of possible issues on China Customs (tax stuff), production quality or transportation damage. Just don't have time to test all the boards.
  13. Well, the biggest problem is that the mali userspace lib from RK is not compatible to the xserver and desktop display infrastructure installed in ARMBIAN. You have to install RK's xserver packs and also new desktop from some unkonwn source (maybe that's the Debian source under developing or source from RK). I have faced it once when I was customizing a RK3288 board and I'm sure that it'll be still standing in my way. So Let me do some experiments and make as many functions work as I can.
  14. Thanks a lot for the hints. I chose the Marvell 64-bit patch instead of RK3288 to replace compressed zImage with the binary Image. Now Armbian 5.32 (Ubuntu 16.04 Desktop) is successfully running on my board. I forked the repo and make my own commit to add the support for RK3399. You can find the changes to original repo here: Know issues: 1. No GPU or VPU pack installed
  15. Now the bootloader and kernel built with Armbian scripts are running. But there's a strange issue, in which the ramdisk system can not mount rootfs partition on SD card (SanDisk Ultra 8GB Class10 Micro SD): Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 rootf
  16. I just did some simple test and didn't know if it was in a correct way. As I was using the rk-rootfs-build scripts, I assumed that the packs were working. Unfortunately, no time for further test. Take a look at the deb packs here: And actually ARM guys won't do anything for Firefly RK3399. Rockchip will, but only in there official repo. Screenshot of es2gears test.
  17. I'm starting to add RK3399 to Armbian, in my spare time. Here's the board I got, RK3399 official EVB, which spent me 500CNY (~63EURO) on Taobao, quite cheap comparing to Firefly. Spec: - Rockchip RK3399 (2xA72 + 4xA53, Mali T860 MP4) - 4GBytes Dual channel LPDDR3 (64-bit in total) - 8GBytes eMMC, Micro SD Slot - USB 3.0 Type-A, USB Type-C (DP over Type-C), USB2.0, HDMI - 1G Ethernet - Raspberry Pi compatible 2x20 pin header
  18. Yep, that's why I only put it as an alternative option. Maybe I should use the term "if you insist".
  19. Hey guys, I've written a brief guide of getting ARMBIAN running on ClearFog Base, hoping it will be helpful for new bees. It's like a note of how I was managed to write images and to boot ARMBIAN from USB, eMMC, or SATA SSD. And some details of A388 SoC boot selection. The guide is based on ARMBIAN 5.30 and ClearFog Base + A388 SoM with eMMC, and I believe that all the steps were verified, although I've tried several versions of ARMBIAN (both Deibian and Ubuntu) and got lots of boot failure. If there's any mistake in t
  20. And it has 4GB dual-channel LPDDR3 by default, a small cortex-M4 MCU for board management or real time processing. The real purpose of this board is not for SBC but micro blade server cluster. that's why all connectors are placed to one side, as front panel in the future. I was also planning a real open cluster project to DIY blade system with managed switch blade ( the SOM on clearfog could be a good start ), backplane power delivery and cooling control. Just need more TIME. Ouch...
  21. Mark this topic as solved since RK3288 has already been supported by Armbian. I've talked to some cooperators of RK and it seems RK is officially contributing to the project ( not confirmed ), and they are willing to pay more attention to opensoure work. Good good!
  22. Hi, Is there any plan fro Armbian to support Rockchip processors like RK3288 or RK3399? Any guide on how to port Armbian on them? These processors have official support on GPU (both openCL and openGL ES), HW video codec (like H264 encoding and decoding with gstream), and also open-sourced Kernel 4.4.x. And most important thing is they are willing to support opensource community and fix their bugs continuously. I've got a RK3288 proto board which was able to run Linux 4.4 + Debian with HW accelerated desktop and video playing, and it worked perfect. The only