nightseas

Members
  • Content Count

    21
  • Joined

  • Last visited

3 Followers

About nightseas

  • Rank
    Member

Recent Profile Visitors

764 profile views
  1. 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.
  2. 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 http://beta.armbian.com xenial/main arm64 linux-dtb-next-sunxi64 arm64 5.37.171208 [25.0 kB] Get:2 http://beta.armbian.com xenial/main arm64 linux-image-next-sunxi64 arm64 5.37.171208 [14.7 MB] Get:3 http://beta.armbian.com xenial/main arm64 linux-u-boot-nanopineo2-next arm64 5.37.171208 [222 kB] Get:4 http://beta.armbian.com xenial/main arm64 linux-xenial-root-next-nanopineo2 arm64 5.37.171208 [318 kB] Then the Ethernet port is no longer working. Kernel message shows MDIO register failure: root@NEO2-ST0:~# dmesg | grep -i eth [ 0.000000] psci: probing for conduit method from DT. [ 1.661750] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838435] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 1.838566] dwmac-sun8i 1c30000.ethernet: Will use external PHY [ 1.944368] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 1.944381] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 1.944391] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 1.944401] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 1.944412] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 1.944422] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 1.944984] dwmac-sun8i 1c30000.ethernet: Cannot register the MDIO bus [ 1.945003] dwmac-sun8i 1c30000.ethernet: stmmac_dvr_probe: MDIO bus (id: 0) registration failed Any hack do I need on device tree or driver to make it work again? BTW: Is there any way to select specific version of ARMBIAN to build? 5.36 for example. Even if I checkout the specific release tag the build scripts will always switch to master and build the latest version. Thanks & BR, Xiaohai Li
  3. 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://github.com/nightseas/nightWiring https://github.com/nightseas/python-nightWiring/
  4. You should better build your own image, with several configurations changed from rk3399-evb to firefly, such as dtb, uboot config...
  5. Thanks for the hints. Do I also need to install Rockchip DRM packages while testing glmark2?
  6. 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
  7. I have made the initial support for RK3399. Currently working on GPU stuff. https://github.com/nightseas/armbian-build
  8. 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.
  9. 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.
  10. Which kernel are you using? Kernel 4.4 from Rockchip official repo: https://github.com/rockchip-linux/kernel If it's mainline Kernel from kernel.org 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. https://github.com/nightseas/rockchip-uboot/commit/80b82a7ba084b36c4f4ffbe7b67ffe98ff349f21
  11. 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.
  12. 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.
  13. Thanks a lot for the hints. I chose the Marvell 64-bit patch instead of RK3288 to replace compressed zImage with the binary Image. https://github.com/armbian/build/blob/master/patch/kernel/mvebu64-default/packaging-4.x-with-postinstall-scripts.patch 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: https://github.com/nightseas/armbian-build/ Know issues: 1. No GPU or VPU pack installed for now; 2. There's a binary tool from RK used to convert u-boot, which can't be packed into the u-boot deb because it's for x86_64. Means you can't update bootloader in a running Armbian. Next step will be GPU and VPU userspace lib porting. Screenshot of desktop, with CPU, temperature, and frequency:
  14. 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 rootfs: recovering journal rootfs: clean, 145627/219024 files, 636583/875520 blocks done. mount: mounting /dev/mmcblk0p1 on /root failed: No such device done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 No init found. Try passing init= bootarg. BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) But the fsck.ext4 successfully operated the partition, and in the ramdisk system I was able to mount the system manually. (initramfs) ls /dev/ ttyFIQ0 tty24 fuse network_latency rfkill tty25 vpu_service network_throughput mem tty26 rkvdec memory_bandwidth null tty27 ptmx mali0 port tty28 ttyS1 mmcblk1 zero tty29 ttyS3 mmcblk1rpmb full tty30 ttyS0 mmcblk1boot1 random tty31 ttyS2 mmcblk1boot0 urandom tty32 hwrng usbmon3 kmsg tty33 ram0 usbmon4 tty tty34 loop-control usbmon5 console tty35 loop0 usbmon6 tty0 tty36 loop1 input vcs tty37 loop2 i2c-9 vcsa tty38 loop3 hdmi_hdcp1x vcs1 tty39 loop4 fb0 vcsa1 tty40 loop5 vendor_storage tty1 tty41 loop6 dri tty2 tty42 loop7 pts tty3 tty43 zram0 fd tty4 tty44 net stdin tty5 tty45 ppp stdout tty6 tty46 usbmon0 stderr tty7 tty47 usbmon1 char tty8 tty48 bus block tty9 tty49 usbmon2 disk tty10 tty50 uinput rtc tty11 tty51 i2c-0 vcs2 tty12 tty52 rtc0 vcsa2 tty13 tty53 i2c-1 vcs3 tty14 tty54 i2c-4 vcsa3 tty15 tty55 mapper vcs4 tty16 tty56 vhci vcsa4 tty17 tty57 uhid vcs5 tty18 tty58 ashmem vcsa5 tty19 tty59 iio:device0 vcs6 tty20 tty60 snd vcsa6 tty21 tty61 mmcblk0 tty22 tty62 mmcblk0p1 tty23 tty63 cpu_dma_latency (initramfs) [ 27.588426] random: nonblocking pool is initialized (initramfs) (initramfs) (initramfs) mount -t ext4 /dev/mmcblk0p1 /root [ 43.477832] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) (initramfs) ls /root/ sys tmp usr lost+found media opt boot home proc selinux run var lib dev mnt bin root etc srv sbin The boot scripts and full log are attached. Just ignore the eDP and SDIO WiFi errors, because they are not connected. I guess I'll need to check the kernel config (also attached) then.
  15. 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: https://github.com/rockchip-linux/rk-rootfs-build/tree/master/packages/arm64/libmali And actually ARM guys won't do anything for Firefly RK3399. Rockchip will, but only in there official repo. Screenshot of es2gears test.