pask

Members
  • Content Count

    26
  • Joined

  • Last visited

About pask

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    IT

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Great job, @piter75! "current" buster desktop works well for me. The debug ttl console too. Performance are much better than default friendlyelec 4.4.y kernel's ones, although not overall better than those of the ddr3 version 1 nanopi m4 (see https://www.cnx-software.com/2019/10/28/nanopi-m4v2-kit-review-part-2-friendlycore-desktop/): Memory performance (big.LITTLE cores measured individually): memcpy: 1880.5 MB/s (0.6%) memset: 8430.7 MB/s (0.6%) memcpy: 3729.4 MB/s memset: 8492.3 MB/s (1.0%) Complete sbc-bech results here: http://ix.io/23eC Both sd card read and write speeds are good: 70MB/s with a sandisk 32GB extreme pro card Stability also looks good, but requires more time to be tested. As soon I'll be able to run some panfrost benchmarks, I'll update. By the way, desktop experience is smooth and stable and sound works too, but lack of acceleration is limiting when watching videos, although the 5.4 kernel improved speed over the 4.4.y is evident. The only "small" issue I have found so far, is that boot is a bit slow. And for about 30 seconds I do not see any activity, neither on the serial console, nor on hdmi. Perhaps because of "printk: bootconsole [uart8250] disabled" ? I'm going to do some usb storage tests, before considering this board ready for replacing the raspberry pi4 I use at the moment as my home nextcloud server.
  2. My usb ttl dongle is a "DSD TECH SH-U09C5" with a FTDI FT232RL chip. Here is today dmesg from the default kernel image http://ix.io/22SV and it doesn't look like totally "healthy" to me Yes I use TX,RX and GND wires. As soon as I plug in the dongle (or connect the gnd to the board), the nanopi m4v2 freezes. The problem is that I do not see anything recorded in the logs of the freezing event.
  3. @Enrico You can use the minimal "test" image shared by @piter75 some posts above: it works already quite well, altough more testing is needed. You can also compile it yourself using nanopim4v2 ddr branch from armbian/build git repository.
  4. Thank you @piter75 While booting your minimal default image (as well a default desktop one compiled by me using your last commits), if the ttl serial dongle is plugged in, my board gets stuck somewhere at kernel time. Here is a log http://ix.io/22L4 For many tries I had not understood that the problem was, actually, the ttl dongle itself. But, as a last try (given that I was suspicions because of the lack of hdmi activity during kernel boot, at least until it went stuck), I have disconnected the serial debug dongle, and finally I have seen hdmi activity and, at the end, the login prompt. In other words, the problem with the default kernel image seems to be the serial dongle plugged in. On the other hand, once booted the board (default kernel) without the ttl dongle plugged, and once normally running the Armbian OS, if I try to plug the ttl usb dongle into my laptop usb port, the board freezes.
  5. Indeed, the dev kernel image worked for me too. Could you also check a default kernel image, please? (using the nanopi-m4v2-u-boot-v2019.10-ddr-miniloader branch) Only this one failed on my M4v2, instead. ./compile.sh BOARD=nanopim4v2 BRANCH=default RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no Thank you @piter75 . Comparing the two default image boot logs, mine and yours, they have some "small" differences. Yours: ChipType = 0x10, 316 Mine: ChipType = 0x10, 250 I do not know to what this attribute references . Perhaps to the sd card vendor/model? Yours: ## Executing script at 00500000 Boot script loaded from mmc 1 244 bytes read in 9 ms (26.4 KiB/s) 6514583 bytes read in 421 ms (14.8 MiB/s) 18395144 bytes read in 1172 ms (15 MiB/s) 103833 bytes read in 19 ms (5.2 MiB/s) ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 6514519 Bytes = 6.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f58c6000, end f5efc757 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0) Loading Device Tree to 00000000f5844000, end 00000000f58c5fff ... OK Mine: ## Executing script at 00500000 Boot script loaded from mmc 1 142 bytes read in 5 ms (27.3 KiB/s) 7556947 bytes read in 480 ms (15 MiB/s) 18395144 bytes read in 1161 ms (15.1 MiB/s) 103833 bytes read in 14 ms (7.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7556883 Bytes = 7.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f57c8000, end f5efcf13 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0) Loading Device Tree to 00000000f5746000, end 00000000f57c7fff ... OK On the same hardware, the same running software shouldn't lead to the same amount of bytes read? Anyway, I'll try the debug enabled image and I'll further check. In the meantime, could you also share the default minimal image it's working to you? Just to be sure I'm not doing some dumb error while compiling the image I'm not aware of.
  6. @piter75 the dev kernel boots correctly: https://pastebin.com/jrghsmPi I have also tried the desktop version which works quite well if panfrost is disabled. Audio doesn't work: strangely it seems that this kernel version doesn't support the Realtek ACL 5651: I tried to manually edit the .config, but with no success Instead, images with the default kernel fail (tested with various sd cards): https://pastebin.com/FSfEs9Kq I guess that the friendlyelec 4.4.y kernel dts isn't compatible with the 2019 uboot branch
  7. Hello @piter75 compile.sh fails because of some absolute paths left into the code. pack uboot.img success! /home/pask/armbian-master-build/config/sources/rk3399.conf: line 70: /home/vagrant/armbian/patch/atf/atf-rk3399/add-trust-ini.patch: No such file or directory config(trust.ini) not found! merge failed! [ error ] ERROR in function compile_uboot [ compilation.sh:216 ] [ error ] U-boot file not found [ trust.bin ] [ o.k. ] Process terminated which was easy to fix by myself. But, some steps later: pack input ./u-boot-dtb.bin pack file size: 829663 crc = 0xdf37889f pack uboot.img success! /home/pask/armbian-master-build #pask info patching file trust.ini out:trust.bin E: [mergetrust] filter_elf /home/vagrant/armbian/cache/sources/rkbin-tools/rk33/rk3399_bl31_v1.30.elf file failed merge failed! [ error ] ERROR in function compile_uboot [ compilation.sh:216 ] [ error ] U-boot file not found [ trust.bin ] [ o.k. ] Process terminated which I don't have time to catch at the moment as I'm already (very) late for going to work
  8. @piter75 At the moment I'm running Manjaro with 5.3.11 kernel on the M4v2: I'm experiencing lots of freezes that I'm not been able to diagnose and troubleshoot so far. I was suspecting power issues (which could also explain the USB issues that @NicoDdescribes). But, this morning I tried to use the Raspberry Pi4 official power adapter and cable, which I know to be dependable. But while I was doing a dd of a 4GB file on the SD card, the board got stuck for the umpteenth time: so, now I believe my issues might be related to the SD card / controller. Anyway, in the evening I'll burn a M4 image with the default kernel to see if it's stable under high CPU and I/O load. @piter75 Do you have any link to share explaining all the components needed and where to get them, to build from scratch and burn the bootloader for arm rk3399 boards? I found so much information around but nothing clear and simple enough I could use
  9. Hello Nico, your reviews go so deep and are so well made that I learn something from you everytime I watch one of them. Thanks
  10. @sfx2000 It's not a question of performance, but of convenience. At least to me. Small fanless ARM personal computer devices are getting faster and faster on one hand. On the other, they can be easy installed at home or other places where space, energy costs, and even cooling, are an issue. And left there running 24h. So, you can launch heavy duty compiling tasks and forget them, till the next morning or the evening when you return back home. BTW, I understand that building a working arm64 toolchain could be not easy. Actually, I can't imagine the effort required. I would have to deepen armbian code or be given some hint where to start by somebody more experienced than me.
  11. This is an excellent idea: I have an odroid n2 always on the Internet using a public IP, I'd like to use to compile Armbian for other boards (at the moment a NanoPiM4-v2). Sadly, it seems that the author abandoned, or could not continue this interesting project. On the other side, for what I have understood reading some of the Armbian code, It's not easy to archive the goal of compiling directly on arm64 hardware.
  12. pask

    M4 V2

    @pkfox The long part of my emmc card has an hole for a screw: this part has to be aligned to the screw holder, in the opposite side with respect to the hdmi. Il you buyed the emmc for the first version of the m4, I suspect yours does not have the hole. Try to place as if it had.
  13. pask

    M4 V2

    @pkfox Are you sure you inserted the emmc in the right way? The emmc socket is mechanically symmetrical, not electrically
  14. pask

    M4 V2

    @pkfox 1- be sure to connect the usb2ttl dongle to the NanoPi-M4v2 correctly: only rx tx and gnd have to be connected 2 - use "picocom --baud 1500000 /dev/ttyUSB0" to start the serial console (thanks to @martinayotte for recommending a good tool to use) 3 - boot from sd card while keeping the emmc card disconnected. During the boot process, keep a key pressed: the u-boot loader will stop just before launching the kernel 4 - carefully insert the emmc card (pay attention to connect it in the right way!) (thanks to @martinayotte for this smart&fast method) 5 - write command "boot" in the console. The kernel will boot, hopefully recognizing the emmc card and creating the proper device (in my case mmcblk2) 6 - sudo nand-sata-install to launch the armbian tool for transferring the sd content to the emmc card in the proper way. At the end of the transfer, DO NOT reboot, but exit to the console 7 - patch the new emmc install to replace the not-yet-working bootloader: sudo dd if=8M_after64ibs_uboot_working_rockpi4image_on_nanopim4v2.dd of=/dev/mmcblk2 seek=64 Enjoy your armbian running from the emmc card (tested on buster and the dev kernel)
  15. Perhaps the only serial terminal program I had not tried yet, It's the working one: I can confirm my dongle with the FTDI chip, works in linux too, at a rate of 1500000 baud using picocom. No special config needed. thank you