Jump to content

camelator

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by camelator

  1. On 11/29/2020 at 8:53 PM, piter75 said:
     

    With Armbian v20.11 one can write mainline u-boot image to board's SPI and enjoy booting nvme drives without any mmc devices.

    Prerequisities: ROCK Pi 4(A/B/C) v1.4 or 1.3 with SPI soldered in (v1.3 comes without SPI flash from the factory).

     

    1. If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot
    2. Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C)
    3. Add the following lines to /boot/armbianEnv.txt
      • overlays=spi-jedec-nor
      • param_spinor_spi_bus=1
    4. Reboot
    5. If you shorted 23-25 pins in 1.) then:
      • disconnect them after the ROCK Pi 4 fully boot's 
      • enable spi-nor by executing (as root):
        echo spi1.0 > /sys/bus/spi/drivers/spi-nor/bind
      • verify that the SPI mtd interface is enabled by running
        ls /dev/mtdblock0
      • if the last command does not list any file then something went wrong between 3.) and 5.)
    6. Run nand-sata-install
      • choose option: "Boot from SPI - system on SATA, USB or NVMe"
      • choose NVMe partition, eg. /dev/nvme0n1p1
      • accept erasing of the choosen partition with "Yes"
      • choose fs type (tested with ext4)
      • wait a few minutes for rootfs transfer to chosen partition
      • choose writing SPI bootloader with "Yes"
      • confirm that you want to flash it with "Yes"
      • wait ~60 seconds for writing
      • choose Exit
    7. Reboot
    8. Enjoy Armbian booting with SPI / NVMe

     

    Why bother with mainline u-boot?

    It is known to boot some NVMe drives that legacy u-boot from Radxa has issues with, eg. SAMSUNG 970 EVO Plus and SAMSUNG PM981.

    This does not mean that all NVMe drives are supported, YMMV.

     

    Which NVMe drives are known to be working?

    Corsair MP510 240GB/480GB/960GB

    Gigabyte SSD M.2 2280 PCIe x2 Model:GP-GSM2NE8128GNTD

    HP SSD EX900 M.2 NVMe 120GB. Model: 2YY42AA#ABB
    Intel SSD 660p Model:SSDPEKNW512GB
    Kingston A1000 SSD 240GB (PHISON PS5008-E8-10)

    Kingston A2000 M.2 2280 PCIe NVMe

    PNY 250GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4

    Sabrent Rocket 256GB NVMe PCIe M.2 2280

    Samsung 970 EVO Plus SSD 250GB M.2 2280, PCIe 3.0 x4, NVMe, 3500/2300 MB/s

    Samsung PM981 256GB

    XPG SX6000 Lite 128GB (ASX6000LNP-128GT-C)

     

    Why not using Radxa's u-boot SPI image?

    Ambian's u-boot configuration is incompatible with Radxa's SPI image :(

     

    Why Armbian is using u-boot that is incompatible with Radxa's?

    It uses mainline u-boot with Open Source TPL/SPL/proper and BL31 from Rockchip packaged into u-boot and we may switch to using open source ATF instead of the BL31 in the future.

     

    Can I boot Radxa's images with Armbian's u-boot written to SPI?

    Yes. Armbian's SPI u-boot is compatible with Radxa's images available here: https://github.com/radxa/rock-pi-images-released/releases

    It may not be compatible with some older images (released before July 2020) because of the device tree filename change.

     

     

    Sorry for stupid question,

    "Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C)"

    Where to find a fresh image of armbian for rocckpi 4B+ ????

     

    I tried the download page on the armbian web site => not found (i can't see the image for Rockpi 4B, there is only Rockpi 4A)

    I tried to build a custom image on ubuntu 20.04 from https://github.com/armbian/build

    It does not work.

    Running sudo ./compile.sh  having rockpi4B selected from the menu return the following error:

    [ error ] ERROR in function download_and_verify [ main.sh:589 -> main.sh:434 -> general.sh:1545 -> general.sh:1788 -> general.sh:0 ]
    [ error ] verification failed
    [ o.k. ] Process terminated

     

    Running sudo ./compile.sh docker return the following errors:

    W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
    E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
    E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
    E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
    W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
    E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
    E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
    E: Sub-process returned an error code
    The command '/bin/sh -c apt-get update && apt-get -y install        joe        software-properties-common        gnupg        gnupg1        gpgv1        curl     && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

     

     

    What can I do?

     

     

     

     

     

     

  2. same here:

    I confirm since last update I had random crashes and wifi lost (i post a topic about it)

    I just change the cpufrequtils and the random crashes disapeard, but wifi is still lost.

    But now with this configuration I suspect I have some waiting-time when the workload is too important or temperature too high, I don't know.

    For example a simple apt update on a 60KB file can pause the system for .. let say 1 or 2 minutes, and then things are fast

    strange behaviour

     

  3. Hi,

    just after enabled wifi with armbian-config I reset the board, and no network... Just plugged the network cable, the wifi item in armbian-config disapeared.

    dmesg provide strange lines:

    [    7.496991] brcmfmac: F1 signature read @0x18000000=0x17224356
    [    7.502070] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2
    [    7.502410] usbcore: registered new interface driver brcmfmac
    [    7.504815] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.bin failed with error -2

     

    any help?

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines