zador.blood.stained

Super moderator
  • Content Count

    3608
  • Joined

  • Last visited


Reputation Activity

  1. Like
    zador.blood.stained got a reaction from Tido in board support - general discussion / project aims   
    Yes, but is it still manufactured? Is it still sold worldwide? And what will you do if you are an "interested developer" and your board dies? Buy another one (if it would be even possible) or move it to "community supported"?
    I'm not saying that we should drop support for this particular board right now (I'm sure that @tkaiser would have a different opinion) but any device will fade out in time, regardless of the history.
     
  2. Like
    zador.blood.stained got a reaction from Tido in board support - general discussion / project aims   
    Things to add IMO, some general forum rules to let moderators make decisions based on written rules instead of personal opinions (yes, I think we already discussed this more than a year ago):
     - primary forum language is English, messages in other languages without translation outside of "General chit chat" section may be hidden or deleted
    - don't bump topics too often and don't create duplicate messages and topics to bring attention to your issue
    - be respectful to each other, follow the nettiquette
    - don't abuse private messaging for tech support
    - don't abuse forum for self-promotion and don't spam
    - breaking the rules will result in a warning, getting multiple warnings will result in a ban
     
     
  3. Like
    zador.blood.stained got a reaction from Tido in board support - general discussion / project aims   
    Then the project should be scaled back to the point where it is sustainable?
     
    If a problem requires too much time to solve then it should be ignored until someone more knowledgeable or more resourceful solves it?
     
    Then maybe "we" should not try to satisfy everyone? This includes answering to topics if you don't know the answer or can't solve the problem right now, includes providing nightly images and images for community supported devices (let people build images by themselves and share them without using the project infrastructure (i.e. via MEGA or Google Drive) since disk space and traffic costs money that doesn't come from nothing). Also includes working on and especially providing any images already for H6 which is (IMO) > 6 months away from getting enough green squares in the sunxi status matrix for making images suitable for everyday use. Includes providing "better" wireless drivers if integrating and testing them takes too much time.
     
    I think this would help too, I don't want to wash my eyes with a soap after reading some threads.
  4. Like
    zador.blood.stained got a reaction from Tido in board support - general discussion / project aims   
    Then the project should be scaled back to the point where it is sustainable?
     
    If a problem requires too much time to solve then it should be ignored until someone more knowledgeable or more resourceful solves it?
     
    Then maybe "we" should not try to satisfy everyone? This includes answering to topics if you don't know the answer or can't solve the problem right now, includes providing nightly images and images for community supported devices (let people build images by themselves and share them without using the project infrastructure (i.e. via MEGA or Google Drive) since disk space and traffic costs money that doesn't come from nothing). Also includes working on and especially providing any images already for H6 which is (IMO) > 6 months away from getting enough green squares in the sunxi status matrix for making images suitable for everyday use. Includes providing "better" wireless drivers if integrating and testing them takes too much time.
     
    I think this would help too, I don't want to wash my eyes with a soap after reading some threads.
  5. Like
    zador.blood.stained got a reaction from Jens Bauer in Clearfog Base with eMMC first boot tutorial   
    Did you add "emmc_fix=on" to /boot/armbianEnv.txt on the eMMC (you needed to mount it after flashing) or did you try to insert a SD card in the microSD slot on the board? Without this eMMC won't be detected by the kernel.
  6. Like
    zador.blood.stained got a reaction from Jens Bauer in Clearfog Base with eMMC first boot tutorial   
    You can copy it to the same USB stick (as a file) and dd it to the eMMC. Please note that you need to add/set "emmc_fix=on" in /boot/armbianEnv.txt both on your USB stick and on eMMC after you flash the image on it, or you can just insert any SD card into the SD slot.
     
    There is no USB OTG port here so UMS (mass storage gadget) or fastboot is not an option here. The only "better" solution could be tftp based to download the image to RAM or USB storage and flash it to eMMC, but it requires setting up a tftp server, or writing the image from USB to eMMC from u-boot.
  7. Like
    zador.blood.stained got a reaction from Jens Bauer in Clearfog Base with eMMC first boot tutorial   
    OFF,OFF,ON,ON,ON as per Solid-Run wiki for SD/eMMC. 
  8. Like
    zador.blood.stained got a reaction from Jens Bauer in Clearfog Base with eMMC first boot tutorial   
    Please try setting switches to OFF,ON,OFF,OFF,ON instead.
     
    I just tried to use kwboot from mainline u-boot and it worked fine for me
    git clone --depth 1 git://git.denx.de/u-boot.git cd u-boot make CROSS_COMPILE=arm-linux-gnueabihf- clearfog_defconfig make CROSS_COMPILE=arm-linux-gnueabihf- tools tools/kwboot -b ~/u-boot-uart.mmc /dev/ttyUSB0 screen /dev/ttyUSB0 115200  
  9. Like
    zador.blood.stained got a reaction from Jens Bauer in Clearfog Base with eMMC first boot tutorial   
    It may be easier to unpack the .deb package from here than mounting the existing image and extracting files from its filesystem.
     
    Not with PuTTY and I'm not sure if there is a good way to do it from Windows in general.
    I would recommend reading this tutorial and official Solid-Run instructions here.
    You can get the u-boot binary from Armbian packages and this binary can easily boot an image from USB flash with "run usbboot" but you still need to find a way to load the u-boot via UART (either using kwboot or scripts linked in the first tutorial).
     
    It is.
  10. Like
    zador.blood.stained got a reaction from esbeeb in Learning from DietPi!   
    IMO "linux-firmare" in Ubuntu based images should be installed by default as it contains firmware for popular wireless and multimedia devices. Solving random firmware related problems is a complicated task for our user base.
  11. Like
    zador.blood.stained got a reaction from lanefu in why does passing KEY=value args to compile.sh work?   
    https://github.com/armbian/build/blob/master/compile.sh#L51-L59
    # Script parameters handling for i in "$@"; do if [[ $i == *=* ]]; then parameter=${i%%=*} value=${i##*=} display_alert "Command line: setting $parameter to" "${value:-(empty)}" "info" eval $parameter=$value fi done  
    Not sure if this solution is 100% bullet-proof (i.e. for handling special characters and values with spaces) but it works for the build script needs.
  12. Like
    zador.blood.stained got a reaction from tkaiser in Benchmarking CPUs   
    I thought more about this and also ran openssl and cryptsetup through strace and checked openssl build configuration in Ubuntu.
    Stock Ubuntu (and most likely Debian) OpenSSL will use userspace crypto. So if there are CPU instructions (NEON, ARMv8 CE) - it should use them, but it won't be using HW engines like sun4i-ss or CESA. At least we have some comparable numbers as long as we don't compare OpenSSL 1.0.x results with 1.1.x directly. This means that AES numbers in the table will not resemble performance in some real world scenarios that use in-kernel crypto (like disk and filesystem encryption) But people will still use your results table to compare boards, so IMO it's worth adding a note for boards where HW crypto engines are available. ARMv8 CE is not a crypto engine, its numbers should depend on CPU performance and should be affected by throttling, compared to, i.e., CESA that uses a fixed clock.
  13. Like
    zador.blood.stained got a reaction from tkaiser in Benchmarking CPUs   
    Since I had this image installed on eMMC and the board was ready to use I ran a benchmark and it produced +/- similar to already present in the table results.
    Log: http://ix.io/1iLy
  14. Like
    zador.blood.stained got a reaction from NicoD in Benchmarking CPUs   
    This script has CR+LF line endings, it needs to be converted to Unix format first
  15. Like
    zador.blood.stained got a reaction from 5kft in u-boot 2018.05 parser issue w/Armbian sunxi-next DT scripts (e.g., spi-spidev overlay configuration failure)   
    This.
     
    Both overlays and fixup scripts need updates after migration from 4.14 to 4.17.
  16. Like
    zador.blood.stained got a reaction from WarHawk_AVG in MMC: No card present error on Allwinner boards   
    Symptoms:
    Board does not boot Armbian from inserted SD card, but may boot other distributions (based on old/legacy u-boot).
    Following or similar output can be grabbed from the serial console:
    U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:04:04) DRAM: 2048 MiB Trying to boot from MMC1MMC: no card present spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### The key message here is "MMC: no card present"
     
    Most likely cause:
    Malfunctioning microSD slot card detect switch.
    It can be verified either visually (with a magnifying glass) or electronically (with a multimeter) - at least in the slots used on Orange Pi boards and on Pine64 the pin near the switch should be shorted to the ground (i.e. SD slot casing) when card is inserted.
     
    Illustration (example) of a working switch:

     
    Verification (with a multimeter):
    Probe 1 - slot pin near the switch (may be different for different slot types, but at least true for Oranges and Pine64)
    Probe 2 - microSD slot casing or other parts connected to GND (not shown on the photo)
    No card - circuit is open
    Card inserted - circuit is shorted
     
    Photos - card is not inseted on the left and is fully inserted on the right:
    Orange Pi
     
    Pine64 (switch is more visible)
     
    Can it be fixed?
    Yes if the switch is not broken completely, by carefully adjusting (bending) the stationary contact (left on the pictures and photos, it usually is a part of the SD slot casing) i.e using a needle so it touches the moving contact (mostly hidden inside the slot on the photos) when card is inserted and not touching it when it is not inserted.
  17. Like
    zador.blood.stained got a reaction from jscax in Pushing the I2C SSD1306 OLED to its limits   
    No. If you are using, for example, a H3 based device, a recent enough Armbian image and want to change frequency of the I2C controller 1, you need to install kernel headers, create a file (i.e. "i2c1-change-frequency.dts")
    /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&i2c1>; __overlay__ { clock-frequency = <200000>; }; }; }; and add it via "armbian-add-overlay"
     
    Or for testing purposes just decompile, change and recompile the DT in /boot/dtb using dtc. Since there will be no node labels you'll have to check the original DT for node names, i.e. I2C 1 node would be named "i2c@1c2b000".
  18. Like
    zador.blood.stained got a reaction from Tido in ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)   
    Desktop notifications + web browser + video/music player for example?
    And it's not about whether you need those sounds, it's about whether only the needed application will obtain the exclusive audio output (if you don't set up dmix).
     
    setting up ALSA dmix as the default output device is easy enough IMO
  19. Like
    zador.blood.stained got a reaction from chwe in Armbian-Stretch and IR-Remote?   
    If we are talking about connecting IR receiver to any GPIO (and not using a dedicated GPIO pin and an in-SoC CIR decoding HW) then it should be enough to use this which requires the appropriate kernel drivers, RC keymaps and DT modifications (since we don't have overlays support there yet).
  20. Like
    zador.blood.stained reacted to hjc in Firefly RK3399 support efforts (potential csc board?)   
    Yes, with some patches, in the same repo. Only succeeded to boot the 4.4 legacy kernel, though.
     
    Copy the device tree from FriendlyELEC's kernel, and it boots with Rockchip u-boot and kernel. Their kernel modifications are mostly for their accessories, like several LCD screens, touch screens, etc.
     
    It's a rough port, especially for u-boot. Since T4 does not have upstream u-boot support, and I only spent a few minutes creating the dts file from the Linux one. (Still a lot of bugs, like USB is not functional, so you cannot load kernel from a USB device. but that's sufficient for booting linux kernel from emmc/sd)
     
    As for 4.17 mainline kernel, it's still far from complete.
    1. CPU-bound tasks are not pinned to the Cortex-A72 core automatically
    2. HDMI not working
    3. USB3/USB-C not working
     
    so I did not spend time investigating on that running on T4. It may be a lot better later this year, though.
  21. Like
    zador.blood.stained reacted to Juanjo in u-boot dev branch won't boot from eMMC and next branch get stuck sometimes   
    Ok,
     
    Patched 2013-10-rc4 to enable SPL_WATCHDOG and that workaround the stuck SPL every 1 of 5 boots.
     
    And patched 2018-03-armbian (dev branch) to actually set USDHC3 pins on HummingBoard2 an enable it to actually have eMMC boot support from SPL seems to work, many reboots and no stuck SPL so far. Later will PR it.
     
  22. Like
    zador.blood.stained got a reaction from TonyMac32 in NanoPi K2 General Topics   
    There is no such config in our current build script: https://github.com/armbian/build/tree/master/config/boards
     
    Exactly
  23. Like
    zador.blood.stained got a reaction from gounthar in Armbian Stretch mainline kernel 4.14.y first start. How to log in?   
    Just so you don't waste your time, this kernel version does not support composite video output anyway.
  24. Like
    zador.blood.stained got a reaction from arronar in [SOLVED] openvpn - Cannot load CA certificate file ca.crt (no entries were read)   
    Possibly your CA certificate is malformed or invalid.
    The file size looks too large for a usual CA certificate. Please try to open it in a text editor and check if it looks like this
    -----BEGIN CERTIFICATE----- <several lines of characters> -----END CERTIFICATE----- or try to verify it with openssl
    openssl verify -CAfile /etc/openvpn/client/ca.crt /etc/openvpn/client/ca.crt  
  25. Like
    zador.blood.stained got a reaction from YaR in [OPi Plus 2] SPI1 pins   
    In theory - yes, but keep in mind that the bus bandwidth will be split between 3 devices so you'll get lower FPS and worse touch screen responsiveness than if they were connected to dedicated SPI controllers.
    You will need to add extra GPIO chip selects using this as an example and add 3 slave SPIdev devices like here.