sfx2000

Members
  • Content Count

    580
  • Joined

  • Last visited


Reputation Activity

  1. Like
    sfx2000 got a reaction from ftp-bin2fex in Lichee Pi zero   
    Nice work - must have been a bit of effort to squeeze a liter of code into 250 ml bucket...
  2. Like
    sfx2000 got a reaction from guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Cool - now we possibly know who to attribute the actual script changes to - it was not attributed over at the WLAN PI distro...
     
    I'm not on DietPI's group - but someone should encourage the author to do a pull request on FE's github, as it's obviously a good thing to include.
     
    FWIW - on the stats screen, you can change the padding from "2" to "0", which brings the bottom line back onto the screen... (it prints a couple of pixels down)
     
        elif page_index==1:         # Draw some shapes.         # First define some constants to allow easy resizing of shapes.         # padding = 2 # FE's script draws off canvas here, so we remove the pad for this screen padding = 0         top = padding         bottom = height-padding         # Move left to right keeping track of the current x position for drawing shapes.  
  3. Like
    sfx2000 reacted to guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Thanks for the information
    Additionally I did found "this" patch also in the dietpi-forum:
    [Tutorial] How to get your NanoHatOLED to work

    For dietpi there are much more dependencies, because it claims to be smaller than armbian in the basic-configuration
     
    There are also the .zip files of the complete patch - in 2 versions - written by the user Phillski (see inside the spoiler)
     
    for backup-reasons I will attach the 2 versions also here
     
    I had only to extract the .zip above the NanHatOLED-Directory and reboot - no need for an additinally installation
     
     
    NanoHatOLED_v2_2Minutes_DietPi.zip
    NanoHatOLED_v1_5Minutes_DietPi.zip
  4. Like
    sfx2000 got a reaction from guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Save the diff I posted about as bakebit_nanohat_oled.patch - then using patch, patch your corresponding file like this...
     
    patch -b < bakebit_nanohat_oled.patch
     
    This will patch the existing file, and create a back up of the original...
     
    That should do it - then for your logo file - you'll see where to put the name of the logo file, and keep the logo in the same dir...
     
    Then just run the install script, which will pick everything up and rebuild the nanohat oled
  5. Like
    sfx2000 got a reaction from guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Here's my local copy of the file in case you get stuck...
     
     
    bakebit_nanohat_oled.py
  6. Like
    sfx2000 got a reaction from guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Works perfect - sorting the dependency for pillow was the key....
     
    Works fine with 5.65 stable for Neo2
     
     
     
    Plays well with NanoPI NEO (the H3 version) as well.
     
    Thx!
  7. Like
    sfx2000 got a reaction from gounthar in Sunvell H3 2GB RAM + 16GB ROM TV Box   
    mtd should work - https://www.kernel.org/doc/html/v4.14/driver-api/mtdnand.html
     
    Would need to tweak uboot, build the partitions - jffs as a file system - but might just be use the NAND as a pseudo SPI, and boot the rest from USB or the SD Card....
  8. Like
    sfx2000 reacted to guidol in [Info] NanoPi Neo/Neo2-OLED-Hat does work with armbian   
    Today I swapped my old Neo2 against a Neo2 LTS 1GB in my NAS case - so I had a old Neo2 512MB free for the black Aluminum-OLED-case which I got in a drawer.
     
    Now I did try to activate the OLED in 
    ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi64 Linux npi-neo2-27 4.19.4-sunxi64 #6 SMP Fri Nov 30 14:02:43 +03 2018 aarch64 GNU/Linux
    First (like on a i2c-clock" I activated i2c0 in armbian-config:
     
    root@npi-neo2-27(192.168.6.27):~# armbian-config System --> Hardware --> [*] i2c0 After the reboot I checked for the i2c-OLED-device and got:
     
    root@npi-neo2-27(192.168.6.27):~# apt install i2c-tools root@npi-neo2-27(192.168.6.27):~# i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  After some trial and error(-messages) I did found the following dependencies for compiling/installing the software for the OLED-Board:
    apt-get install python-setuptools libjpeg-dev  
    After that I did the normal "5 Enable NanoHat-OLED manually" from
    http://wiki.friendlyarm.com/wiki/index.php/NanoHat_OLED
    with
     
    root@npi-neo2-27(192.168.6.27):~# cd /home/guido root@npi-neo2-27(192.168.6.27):~# git clone https://github.com/friendlyarm/NanoHatOLED.git root@npi-neo2-27(192.168.6.27):~# cd NanoHatOLED root@npi-neo2-27(192.168.6.27):~# ./install.sh And after the next reboot the OLED-Display did work
  9. Like
    sfx2000 reacted to jerryn in GQRX RTL-SDR is working on NanoPC-T4   
    Here's a video of GQRX receiving NOAA Weather Radio on my NanoPC-T4
     
    armbian-nanopc-t4-gqrx-gnuradio.mp4
  10. Like
    sfx2000 reacted to mindee in NanoPi M4 performance and consumption review   
    Thanks for your suggestion, we made a SATA HAT prototype for NanoPi M4, it can connect  with 4x 3.5inch hard drive and work well.
     
     
  11. Like
    sfx2000 reacted to TonyMac32 in Recommended SBC below 20USD range.   
    Well, it's one of only two with 4 fast cores, the other being XU4.  The RK3399 doesn't even have that going for it.  It honestly is in the top 3 performers in any case, every time I use any other board I get a rude awakening about how bad a desktop experience can be. RK3399 is somewhat better but is still poorly supported kernel wise by comparison.
  12. Like
    sfx2000 got a reaction from guidol in [Info] FriendlyARM PCM5102A-Hat with NanoPi Neo under mainline 4.x.x and dev 5.3.3   
    Nice job, and very well written up.
  13. Like
    sfx2000 reacted to guidol in [Info] FriendlyARM PCM5102A-Hat with NanoPi Neo under mainline 4.x.x and dev 5.3.3   
    I did that on a NanoPi Neo with the FriendlyARM PCM5102A Hat
    ( https://www.friendlyarm.com/index.php?route=product/product&amp;product_id=169 )
    using kernel 4.14.87-sunxi and armbian 5.67 (or later would be only 5.65?)
    (before that I did use legacy kernel 3.4.x with the PCM510A)

    and the armbian-BuildSystem
    plus (THANKS to) informations in threads from  @dony71 , @Christos, @Valery Rezvyakov
    and the the Reference-Threads you could find above
     
    ----------------------------------------------------------------------------------------------------------------------------------
    BACKUP DTB (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cp /boot/dtb/sun8i-h3-nanopi-neo.dtb /boot/dtb/sun8i-h3-nanopi-neo.dtb_org
     
    ----------------------------------------------------------------------------------------------------------------------------------
    CONVERT dtb to dts (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    dtc -I dtb -O dts /boot/dtb/sun8i-h3-nanopi-neo.dtb -o /boot/dtb/sun8i-h3-nanopi-neo.dts
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT /boot/dtb/sun8i-h3-nanopi-neo.dts
    ----------------------------------------------------------------------------------------------------------------------------------
    nano /boot/dtb/sun8i-h3-nanopi-neo.dts
     
    - change: status from "disabled" to "okay"
    ----------------------------------------------------------------------------------------------------------------------------------
    FROM
     
                    i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "disabled";                         phandle = <0x4e>;                 };  

    TO
     
                    i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "okay";                         phandle = <0x4e>;                 };
    ----------------------------------------------------------------------------------------------------------------------------------
    CONVERT (BACK) dts to dtb (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    dtc -I dts -O dtb /boot/dtb/sun8i-h3-nanopi-neo.dts -o /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay
     
    ----------------------------------------------------------------------------------------------------------------------------------
    COPY new dtb over dtb (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cp /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay /boot/dtb/sun8i-h3-nanopi-neo.dtb
                    
    ----------------------------------------------------------------------------------------------------------------------------------
    COPY sun8i-h3-I2S-out.dts to home (working directory on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    copy sun8i-h3-I2S-out.dts -->  /home/guido/
     
    ----------------------------------------------------------------------------------------------------------------------------------
    armbian-add-overlay (on NanoPi Neo)
    does only work if you got the kernel-headers installed for your actual kernel-version
    (at this time the lastest kernel-header are (via armbian-config -> Software -> Install Headers)
    Linux kernel headers for 4.14.84-sunxi on armhf - so NOT for kernel 4.19.y)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# armbian-add-overlay ./sun8i-h3-I2S-out.dts
    Compiling the overlay
    Copying the compiled overlay file to /boot/overlay-user/
    Reboot is required to apply the changes

    ----------------------------------------------------------------------------------------------------------------------------------
    dtbo is created (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# ls -l /boot/overlay-user/
    insgesamt 4
    -rw-r--r-- 1 root root 1323 Dez  7 19:34 sun8i-h3-I2S-out.dtbo
     
    ----------------------------------------------------------------------------------------------------------------------------------
    user-overlay is created in /boot/armbianEnv.txt (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost1 usbhost2 rootdev=UUID=33ca90d6-130b-4d5f-a8f4-95b3b97ef5c0 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u user_overlays=sun8i-h3-I2S-out  
    ----------------------------------------------------------------------------------------------------------------------------------
    now REBOOT (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):~# lsmod|grep i2s
    sun4i_i2s              16384  0
    snd_soc_core          118784  2 sun4i_i2s,sun8i_codec_analog
    snd_pcm                69632  3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT config-default.conf (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    cd /home/guido/build
    nano ./config-default.conf
    replace content /home/guido/build/config-default.conf with attached
    config-default.conf_nanopineo
    ./compile
    -> With this conf, script compilation will stop to overwrite kernel source to build patch
    -> At that time, overwrite original Kconfig with the one you modified above
    (at "Make changes to U-Boot" press ENTER to proceed)
    wait for
    "Make your changes to /home/guido/build/cache/sources/linux-mainline/linux-4.14.y then press ENTER"
    BUT DONT PRESS ENTER YET
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT/SAVE Kconfig in a 2nd shell-Window (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    nano /home/guido/build/cache/sources/linux-mainline/linux-4.14.y/sound/soc/codecs/Kconfig
     
    the part FROM
     
    config SND_SOC_PCM5102A     tristate TO
     
    config SND_SOC_PCM5102A     tristate "Texas Instruments PCM5102A CODEC - I2S"  
    ----------------------------------------------------------------------------------------------------------------------------------
    NOW PRESS ENTER in the 1st shell-Windows (.compile.sh) (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    -> Then script compilation will stop again to ask whether you want to add pcm5102a to compile
    -> Default is N, so you need to enter m for module compilation
    Texas Instruments PCM5102A CODEC - I2S (SND_SOC_PCM5102A) [N/m/?] (NEW) m = m for module compilation
     
    After compile is complete
     
    ----------------------------------------------------------------------------------------------------------------------------------
    copy (via SCP/FTP?) the .deb's from /home/guido/build/output/debs (on armbian-BuildSystem) 
    to /home/guido/ (on the NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
     
    ----------------------------------------------------------------------------------------------------------------------------------
    INSTALL the .deb's (here only header and image - because it was already 5.67 (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cd /home/guido 
    dpkg -i ./linux-headers-next-sunxi_5.67_armhf.deb
    dpkg -i ./linux-image-next-sunxi_5.67_armhf.deb
    (image did include the .ko module for the pcm5102a)
     
    ----------------------------------------------------------------------------------------------------------------------------------
    now REBOOT (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
     
    =====================================================================================
    =====================================================================================
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!! ATTENTION: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    After reboot my NanoPi Neo show the following armbian-version:
    ARMBIAN 5.65 stable Debian GNU/Linux 9 (stretch) 4.14.84-sunxi
    and 2 upgrades for headers&image (without the PCM5102A support)
    please keep in mind to freeze the kernel-updates in armbian-config
    for not to loose the support (module) for the PCM5120A!
    armbian-config -> system -> Freeze Disable kernel upgrades
    =====================================================================================
    =====================================================================================

    ----------------------------------------------------------------------------------------------------------------------------------
    BE HAPPY about a successful i2s mapping in dmesg (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):~# dmesg|grep -i i2s
    [    6.911751] asoc-simple-card sound_i2s: pcm5102a-hifi <-> 1c22000.i2s mapping ok
     
    ----------------------------------------------------------------------------------------------------------------------------------
    I enabled also ananlog-Codec (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# aplay -l
    **** Liste der Hardware-Geräte (PLAYBACK) ****
    Karte 0: Codec [H3 Audio Codec], Gerät 0: CDC PCM Codec-0 []
      Sub-Geräte: 1/1
      Sub-Gerät #0: subdevice #0
    Karte 1: I2Smaster [I2S-master], Gerät 0: 1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0 []
      Sub-Geräte: 1/1
      Sub-Gerät #0: subdevice #0

    ----------------------------------------------------------------------------------------------------------------------------------
    /etc/asound.conf (on NanoPi Neo) - later I2S did switch automatically to card 0
    ----------------------------------------------------------------------------------------------------------------------------------
     
    pcm.!default {     type hw     card 1     device 0 } ctl.!default {     type hw     card 1 }  
    ----------------------------------------------------------------------------------------------------------------------------------
    Reference-Threads
    ----------------------------------------------------------------------------------------------------------------------------------
     
    config-default.conf.mod_nanopineo
    sun8i-h3-I2S-out.dts
  14. Like
    sfx2000 got a reaction from gounthar in Orange PI Zero optimization   
    Friends don't let friend use PPTP.... it's not very secure and it's been deprecated across pretty much all platforms.
     
    As someone suggested - wireguard is present, and worse case, one can always consider using OpenVPN...
  15. Like
    sfx2000 got a reaction from tommy in Recommended SBC below 20USD range.   
    I suppose another way of saying things - Fast, Good, Cheap - pick any two...
     
    This isn't going to win fans here perhaps - but shop around - Intel PC on a Stick running Ubuntu...
     
    $35 shipped in US from Amazon - and that Baytrail chip sku does support AES-NI...
     
     

  16. Like
    sfx2000 got a reaction from tommy in Recommended SBC below 20USD range.   
    That's a bit harsh
     
    Heck, most of these SBC's are simple toys - but it's what we do with them that is really the important part - and some of the boards have more flexibility and capability than what the RPF offers in their line.
     
    The issues with the Pi are mostly wrapped about VC4 and its design - VC4 is common to all the Pi's, it 40nm, and it's limited to single channel, and 1GB (that, and the binary closed source blob that is VcOS/ThreadX)- I seriously doubt that Broadcom is going to do anything with VC4 like a die-shrink, so either RPf/Broadcom moves forward with VC5 on a smaller node, or RPf has kind of run their course... HW is one thing, but also they're still shipping ARMv6 stuff (Pi Zero/Zero W) and want to keep a single distro, which holds back the Pi3's (and perhaps Pi2')...
     
    Their last couple of board releases are actually very well engineered (Pi Zero W and Pi3 B+ 1.3) - I think they learned quite a bit with the Pi3 and WiFi, and having to do global wireless certs brought their hardware forward. Layouts are better, and they're doing a good job on the BOM front, keeping costs low - and just look at the board - the number of passives (caps/resistors/inductors) says a lot about the design team - the lastest boards look pretty good
     
    That RPf shipped Pi Zero W - they kept the BCM2835 ARMv6 well past the use by date - similar to what Apple did with Ipad2 and variants (iPad Mini/iPod Touch 5G) - which hurt the SW side as those devices drug out compatibility requirements well past the useful dates as ARM and Apple accelerated performance..
     
    https://allenpike.com/2014/the-ipad-zombie/
     
    The Pi Zero W is the Raspberry Pi Zombie... and it holds back an entire platform that is Raspberry Pi... none the less - they ship a lot of those board and Pi3 B+'s as well...
     
    I'll agree - Pi is not industrial grade components, but with their OEM partners (Sony and Embest), good manufacturing and good software QA for the most part...  There's been some exceptions with first-run boards, and that's happened more than once.
     
    FWIW - totally concur on the mess that was the official PoE hat - I don't think it was a good design, and even shipped, it had problems... seemed kinda rushed, and perhaps it was an answer to a question that had already been answered.
  17. Like
    sfx2000 got a reaction from unlue in Some Wifi Issue...   
    There's a couple of ways to do this - with your use case, have you looked at ESP32/ESP8266? They have a softAP mode that is intrinsic to the module there, and it's lower cost than the device you're looking at.
     
     
  18. Like
    sfx2000 got a reaction from Igor in ambian vs armhf vs openwrt   
    ++ board bring up is easier with Armbian compared to many other environments
  19. Like
    sfx2000 reacted to Igor in SOLVED - How to disable armbian-ram-logging correctly?   
    This should fix this issue.
  20. Like
    sfx2000 got a reaction from gas_85 in SOLVED - How to disable armbian-ram-logging correctly?   
    Take a look at /etc/cron.daily/armbian-ram-logging - might want to comment that line as well...
     
    In any event - the services and crontab entries for ramlogging at well intentioned to keep pressure off the flash, so step carefully...
  21. Like
    sfx2000 got a reaction from gas_85 in SOLVED - How to disable armbian-ram-logging correctly?   
    Long story short - it's a chained series of events that gets one to here...
     
    in systemd... (nice that these are in systemd - I have no skin in the whole systemd discussion other than to recognize that it's there)
     
    armbian-ramlog.service
    armbian-zram-config.service
     
    One can disable them easily enough by just doing systemctl... 
     
    the crontab tip is good...
     
    To get zram back - install zram-config, and for the log stuff once the ramlog is disable (along with the crontab entry), look at logrotate...
  22. Like
    sfx2000 reacted to mboehmer in Thanks for the fish!   
    It is a research program, one of our professors from TU Muenchen cooperates with the Canadians (who operate the sub sea infrastructure).
    The goal of this setup was to measure water quality in North Pacific (more specific, this special site) by deploying some light emitters and light detectors on two strings.
    We want to learn about bioluminescence and radioactivity induced light, which both are kind of noise for the measurements intended later.
    Let's say it like this: it's dark there, really, you have a perfect stable temperature, and it's easier to get things there (and back again) than going for deep holes in ice.
     
    Moreover, we had to learn all necessary things about sub sea technics in a short period of time, including deployment technis (thanks to one guy supporting us, we made the job).
     
    The setup is still operational (which I call success), and with some luck we will extend it with a third string next year, including some Odroid C2 based setups and (as we go for real fibre that time instead of good ol' copper lines) some more sophisticated electronics.
     
    As soon as our paper is published, I can give more details (while I "just" did the electronics, there will be some more physics included )
  23. Like
    sfx2000 got a reaction from NicoD in sbc-bench   
    Up to @tkaiser for results on sbc-bench...
     
    working on an addition - byte-unixbench and sorting out things... removing some gcc over optimizations, looking at threads...
     
    https://github.com/sfx2000/byte-unixbench
     
    It's a better bench than sysbench, and portable... Doing a -c 1 -1 and -c4 -i 1  keeps things short - however - letting it run thru pushes heat/throttles...
     
    UnixBench is interesting from a system perspective...
     
    RPI3 B Plus vs Tinker....
     
    Tinker is 15 pounds of power in a 5 pound sack - RPi3 B+ is a CPU that can do better that it is with raspbian....
     
    Tinkerboard - Cortex-A12/A17 - Armbian ------------------------------------------------------------------------ Benchmark Run: Sat Oct 20 2018 17:02:37 - 17:31:22 4 CPUs in system; running 1 parallel copy of tests System Benchmarks Index Values               BASELINE       RESULT    INDEX Dhrystone 2 using register variables         116700.0    8709974.2    746.4 Double-Precision Whetstone                       55.0       1031.4    187.5 Execl Throughput                                 43.0       1095.7    254.8 File Copy 1024 bufsize 2000 maxblocks          3960.0      91960.7    232.2 File Copy 256 bufsize 500 maxblocks            1655.0      26583.4    160.6 File Copy 4096 bufsize 8000 maxblocks          5800.0     246267.0    424.6 Pipe Throughput                               12440.0     149851.8    120.5 Pipe-based Context Switching                   4000.0      25850.9     64.6 Process Creation                                126.0       2429.0    192.8 Shell Scripts (1 concurrent)                     42.4       2061.9    486.3 Shell Scripts (8 concurrent)                      6.0        432.0    720.1 System Call Overhead                          15000.0     442992.8    295.3                                                                    ======== System Benchmarks Index Score                                         258.2 System Benchmarks Index Values               BASELINE       RESULT    INDEX Dhrystone 2 using register variables         116700.0   13538575.0   1160.1 Double-Precision Whetstone                       55.0       1982.4    360.4 Execl Throughput                                 43.0       1752.7    407.6 File Copy 1024 bufsize 2000 maxblocks          3960.0      87122.4    220.0 File Copy 256 bufsize 500 maxblocks            1655.0      22948.6    138.7 File Copy 4096 bufsize 8000 maxblocks          5800.0     281302.7    485.0 Pipe Throughput                               12440.0     321233.1    258.2 Pipe-based Context Switching                   4000.0      40012.9    100.0 Process Creation                                126.0       3820.3    303.2 Shell Scripts (1 concurrent)                     42.4       3399.0    801.7 Shell Scripts (8 concurrent)                      6.0        433.6    722.7 System Call Overhead                          15000.0     952658.0    635.1                                                                    ======== System Benchmarks Index Score                                         373.1 Rpi 3B+ - Cortex-A53 - VCOS/ThreadX - Raspian ------------------------------------------------------------------------ Benchmark Run: Sat Oct 20 2018 17:02:32 - 17:30:38 4 CPUs in system; running 1 parallel copy of tests System Benchmarks Index Values               BASELINE       RESULT    INDEX Dhrystone 2 using register variables         116700.0    4324740.1    370.6 Double-Precision Whetstone                       55.0        957.4    174.1 Execl Throughput                                 43.0        908.8    211.4 File Copy 1024 bufsize 2000 maxblocks          3960.0     140312.9    354.3 File Copy 256 bufsize 500 maxblocks            1655.0      40618.4    245.4 File Copy 4096 bufsize 8000 maxblocks          5800.0     353296.2    609.1 Pipe Throughput                               12440.0     280908.2    225.8 Pipe-based Context Switching                   4000.0      50734.2    126.8 Process Creation                                126.0       2212.2    175.6 Shell Scripts (1 concurrent)                     42.4       1780.5    419.9 Shell Scripts (8 concurrent)                      6.0        575.7    959.5 System Call Overhead                          15000.0     594784.0    396.5                                                                    ======== System Benchmarks Index Score                                         302.2 System Benchmarks Index Values               BASELINE       RESULT    INDEX Dhrystone 2 using register variables         116700.0   17082008.4   1463.8 Double-Precision Whetstone                       55.0       3803.4    691.5 Execl Throughput                                 43.0       2240.8    521.1 File Copy 1024 bufsize 2000 maxblocks          3960.0     228921.9    578.1 File Copy 256 bufsize 500 maxblocks            1655.0      62777.0    379.3 File Copy 4096 bufsize 8000 maxblocks          5800.0     578721.9    997.8 Pipe Throughput                               12440.0    1112342.2    894.2 Pipe-based Context Switching                   4000.0      98478.8    246.2 Process Creation                                126.0       4789.7    380.1 Shell Scripts (1 concurrent)                     42.4       4464.7   1053.0 Shell Scripts (8 concurrent)                      6.0        589.0    981.7 System Call Overhead                          15000.0    2289227.2   1526.2                                                                    ======== System Benchmarks Index Score                                         705.6  
  24. Like
    sfx2000 got a reaction from NicoD in sbc-bench   
    Gah - watched the video - and a lot of problems across the board (pardon the pun).
     
    Different kernels, built with different versions of GCC, userland (for example, Raspbian userland is all ARMv6 with exception of the kernel for the A7/A53 boards)....
     
    (I wouldn't have included the any of the Pi's in the set of boards being evaluated because of the userland - <soapbox> nothing against Pi's in general, one must appreciate that 35M+ boards means they're doing something right, and they've spawned an entire HW/SW ecosystem around their platform, that's ok - and that ecosystem has in turn made affordable ARM boards available for hobbyists, makers, and developers - before Pi, if one wanted to do development around ARM, boards were expensive, and SW support was very limited to the vendor BSP - these days, it's a lot more open - not perfect, but much better than it was</soapbox>)
     
    Rock64 vs Odroid XU4 - Quad A53 vs A7/A15 big.LITTLE - the big.LITTLE is a challenge for the scheduler, and depending on the BSP from the OEM, it's easy to get wrong, where threads can land on the lesser preferred core, this is an issue even on Android, where much work has been done outside of the mainline kernels (ARM and Qualcomm, I know they've done a lot of research there, but much of that has not been pushed back to mainline).
     
    In my experience, with supported boards (for me this is Tinker and NanoPi NEO), Armbian is generally faster than the vendor's images - and that's doing Byte-Unixbench, which is discounted because it is compiler sensitive - that being said, it's still a useful tool when comparing apples to apples (e.g. tweaking settings on the same OS/Platform, but comparing Platform A to Platform B, one has to take the results with a grain of salt)
     
    I haven't found a lot of evidence of cheating by any of the SBC vendors - it's really hard to do with FOSS, compared to Android, where cheating has occurred with certain OEM's and specific benchmark APK's - Android has enough hooks to enable this kind of cheating in any event.
     
    sbc-bench, in my humble opinion, is a good benchmark for supported boards - as long as the boards being compared are all on the same version of Armbian - and this is made clear in the script comments (please review the script on github, and @tkaiser has been pushing updates, so if one has cloned the repo, it's worthwhile to do a git pull to get the latest revision.
     
    To answer your question about the different versions of Cortex...
     
    Small Cores - A7, A53 are the low power cores focused on efficiency
    Big Cores - A15, A12(A17), A72 - big cores... 
     
    Think of it like Atom (Small Core) vs Core i3/i5/i7 (Big Core) - even at the same clock, the big core is going to get more work done, but perhaps at the cost of heat, so thermal solution needs to be considered.
  25. Like
    sfx2000 got a reaction from gounthar in Sunvell H3 2GB RAM + 16GB ROM TV Box   
    Yeah - but for OP - it's perhaps a challenge to contribute
     
    Keep NAND sane and untouched - makes it possible to continue to use the TV box as an Android - and 7.x isn't a bad place to be there for the intended apps...
     
    Worst case - one can always run termux in the android space - which isn't bad actually - I do that with my little chromebook, and it's debian like enough...