lanefu Posted March 28, 2021 Posted March 28, 2021 2 hours ago, piter75 said: I am not sure of that. My understanding is that we are still building release images from master branch and the removal of this line from targets.conf: -rockpi-4b legacy focal cli stable yes means that focal legacy image for rockpi-4b will not be built. Lack of focal legacy image among 20.02.3 release images (built after the referred commit was merged) seems to corroborate that theory ;-) Hmm. when I doubt just blame @Igor 0 Quote
Igor Posted March 28, 2021 Posted March 28, 2021 11 minutes ago, lanefu said: Hmm. when I doubt just blame Haha. Well, it's possible that its my fault. I tend to enforce cleaning activities to save some space. If we need focal image(s) for those boards, someone just add them (best is that person that needs it send a PR) and ping me for remake. 0 Quote
piter75 Posted March 28, 2021 Author Posted March 28, 2021 11 minutes ago, Igor said: I tend to enforce cleaning activities to save some space +1 We need to do that from time to time. 9 minutes ago, Igor said: If we need focal image(s) for those boards, someone just add them I am not particularly missing them ;p 0 Quote
rockchab Posted April 17, 2021 Posted April 17, 2021 Am 9.3.2021 um 20:51 schrieb madmailman: Never-mind! It seems to be a problem with the Focal (4.4.y) image. I downloaded the Focal (5.10.y) image and it's worked as described. Which also means that the XPG SX6000 Lite 128GB PCIe 3D NAND PCIe Gen3x4 M.2 2280 NVMe (ASX6000LNP-128GT-C) works well with this setup. Its a cheap and cheerful NVME purchased from Amazon. Now I just need to get nfs server working to share data between my Macs and other servers (ubuntu and Raspbian). I've found a few hundred tutorials and they are all just a little different and so far none have worked. :-/ Thanks for the great work on this! i have the same when i use a 4.4.y Image after adding the line "param_spinor_spi_bus=1" and reboot -> Kernel Crash i tried two different 4.4.y Images instead of the 5.10.x because of the behaviour with the reboot Problem booting from nvme 0 Quote
jeanrhum Posted April 23, 2021 Posted April 23, 2021 Hi, Thanks for this great work. I can confirm that PNY 500GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4 works well, but not Crucial P1 (250GB). Do you know if there are some plans to integrate others nvme drivers like the Crucial ones? 0 Quote
footz Posted July 2, 2021 Posted July 2, 2021 Hi, can you add an additional SPI NOR Flash chip, please? I have a 32MBit MX25L25645 SPI Nor flash. Boot log: U-Boot 2020.10-armbian (May 06 2021 - 19:22:15 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Radxa ROCK Pi 4B DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPIFlash... unrecognized JEDEC id bytes: c2, 20, 19 *** Warning - spi_flash_probe_bus_cs() failed, using default environment PS: Maybe it's also not such a good idea to white-list individual Flash chips, since this breaks users' setup by default when there is no real reason to do so. Imho it is a better idea to blacklist chips, if they are known to not work. Thanks and best regards! 0 Quote
Joaho Posted August 15, 2021 Posted August 15, 2021 My friends Rockpi4 has lost audio output, it got less and less and then it was gone. Still warranty, Allnet reacted PERFECTLY, sent replacement within days. I am the one to install it. Easy job, same computer, fully installed M.2 HD. So I thought... When I ran Nand-Sata-install it asked me if I am ok with formatting the HD, I said of course NO - and got thrown out. So I had to swallow it and do it all again, keyboard-layout, editor, his software, bring in the backup of data (lots of music) etc. Can't it accept a NO and still do it's job i.e. write to SPI? Is this a valid suggestion? 0 Quote
piter75 Posted August 18, 2021 Author Posted August 18, 2021 On 8/15/2021 at 11:13 PM, Joaho said: Can't it accept a NO and still do it's job i.e. write to SPI? Is this a valid suggestion? You have probably used the option "Boot from SPI - system on SATA, USB or NVMe" which transfers the current system to SSD and needs to clean it. There is another option - better suited for your case - "Install/Update the bootloader to SPI Flash". It does not touch the existing partitions only writes to SPI Flash. 0 Quote
wureka Posted September 11, 2021 Posted September 11, 2021 On 11/30/2020 at 3:53 AM, 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). If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot 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.) 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 Reboot 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) Two questions: 1. In addition to the above NVME SSDs, how do I know whether other NVME SSD, say ADATA XPG SX8200 Pro 256GB, can be used ? 2. Does the above steps still work for Armbian v21.08 ? Thanks 0 Quote
Igor Posted September 12, 2021 Posted September 12, 2021 On 9/11/2021 at 6:31 AM, wureka said: In addition to the above NVME SSDs, how do I know whether other NVME SSD, say ADATA XPG SX8200 Pro 256GB, can be used ? If this device is not along known to work ones, nobody knows until its plugged. None of those vendors (Radxa / Adata) are supporting us, so we don't have devices you are asking about in the lab. Also even hardware would be on the table, who will cover the time for testing? I don't need to know this to waste my precious time ... On 9/11/2021 at 6:31 AM, wureka said: Does the above steps still work for Armbian v21.08 ? No idea. There is almost no interest from community to improve testings which means we can only run basic testing and what you are asking is certainly not. It would require manual testing, which is simply too expensive if we pay everything. For you and the vendor of your choice. Download and test. I would need to do the same. Then report. It might help someone. 0 Quote
piter75 Posted September 12, 2021 Author Posted September 12, 2021 8 hours ago, Igor said: If this device is not along known to work ones, nobody knows until its plugged. +100 😉 @wureka given this report it may either work or not, or... work intermittently. I don't have any sm2262en(g) based drive to verify... 0 Quote
sergvpurik Posted November 29, 2021 Posted November 29, 2021 Hi. Thanks for this guide. I tried it with Armbian 21.08.1 and can confirm that Patriot Scorch M2 PS256GPM280SSDR (PCIe Gen3 x2) works well. I always get the warning message: *** Warning - bad CRC, using default environment But I can boot my Rock Pi only from the 1-st partition. In case of installing Armbian to the non 1-st NVME partiotion i get 'Filed to load ...' errors. 0 Quote
evadim Posted December 11, 2021 Posted December 11, 2021 (edited) Successfully installed on Rockpi 4C and Samsung PM981 512 Gb ( MZVLB512HAJQ-000L7 ) image: Armbian_21.08.1_Rockpi-4b_focal_current_5.10.60.img.xz Edited December 11, 2021 by evadim 0 Quote
Joaomrq Posted January 29, 2022 Posted January 29, 2022 Hi, Is it possible to use this method to boot from usb? Thank you 0 Quote
Excalibur Posted February 25, 2022 Posted February 25, 2022 Since Armbian no longer provides precompiled image I have to build my own image with the following command `/compile.sh docker BOARD=rockpi-4b BRANCH=current RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no`. I then flashed this image to a microSD card and was hoping to update my U-Boot on SPI. Instead I got the following message once I updated SPI with `nand-sata-install`: Quote U-Boot TPL 2021.07-armbian (Feb 25 2022 - 06:35:14) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2021.07-armbian (Feb 25 2022 - 06:35:14 +0000) Trying to boot from SPI The system stuck on the last line. I then tried to `dpkg -i linux-u-boot-current-rockpi-4b_21.08.1_arm64.deb` and reinstalled SPI bootloader. This actually get me a little bit further: Quote U-Boot TPL 2020.10-armbian (Aug 08 2021 - 18:04:03) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.10-armbian (Aug 08 2021 - 18:04:03 +0200) Trying to boot from SPI NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: If lpddr4 need support multi frequency, INFO: please update loader! INFO: Current ctl index[0] freq=400MHz INFO: Current ctl index[1] freq=800MHz INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 Then the system also stops here. Hopefully this can be fixed soon. 0 Quote
mo123 Posted February 25, 2022 Posted February 25, 2022 How do you build Armbian for RK3399, RockPi4 with edge 5.15/16 kernel instead of current that is 5.10? The GUI only shows legacy and current to select. 0 Quote
piter75 Posted February 25, 2022 Author Posted February 25, 2022 11 hours ago, Excalibur said: Hopefully this can be fixed soon. The truth is I did not test the SPI booting lately. Will give it a shot as soon as I find some spare time. 4 hours ago, mo123 said: How do you build Armbian for RK3399, RockPi4 with edge 5.15/16 kernel instead of current that is 5.10? It's not merged into master yet: https://github.com/armbian/build/pull/3489 1 Quote
camelator Posted May 5, 2022 Posted May 5, 2022 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). If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot 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.) 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 Reboot 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? 0 Quote
Werner Posted May 5, 2022 Posted May 5, 2022 14 minutes ago, camelator said: on ubuntu 20.04 Retry with Jammy as stated mandatory in the docs: https://docs.armbian.com/Developer-Guide_Build-Preparation/ 0 Quote
camelator Posted May 5, 2022 Posted May 5, 2022 Thank you for your answer, so there is no other way to get armbian for rockpi 4B? I have to change my OS and compile the image by myself? 0 Quote
Igor Posted May 5, 2022 Posted May 5, 2022 34 minutes ago, camelator said: Thank you for your answer, so there is no other way to get armbian for rockpi 4B? I have to change my OS and compile the image by myself? It is. Try here: https://armbian.systemonachip.net/archive/ but also get a bit more familiar with a build system. Official fresh images when someone takes responsibility for https://docs.armbian.com/Release_Board-Maintainers/ those boards. Until then ... 0 Quote
camelator Posted May 6, 2022 Posted May 6, 2022 14 hours ago, Igor said: It is. Try here: https://armbian.systemonachip.net/archive/ but also get a bit more familiar with a build system. Official fresh images when someone takes responsibility for https://docs.armbian.com/Release_Board-Maintainers/ those boards. Until then ... ok, done, thank you I have to choose a nvme disk now ! 0 Quote
hyma Posted March 27, 2023 Posted March 27, 2023 (edited) Sorry for stupid question. I tried install the instruction on my rock 3a (different board, but similar). rock-3a:~:% uname -r 6.1.11-rk35xx rock-3a:~:% ls /dev/mtdblock0 /dev/mtdblock0 I choose option: "Boot from MTD Flash - system on SATA, USB or NVMe". It does not work. (solved usb-flash bug) Now, load from USB-flash not working. When I take out the SDcard, the system will not boot and the blue LED is on continuously rock-3a:~:% df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 787664 9260 778404 2% /run /dev/sda2 29124480 2041448 25578216 8% / tmpfs 3938308 0 3938308 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 3938308 0 3938308 0% /tmp /dev/zram1 47960 4284 40092 10% /var/log tmpfs 787660 0 787660 0% /run/user/1000 rock-3a:~:% blkid /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/mmcblk0p2: LABEL="armbi_root" UUID="6ce28e93-ed91-46ae-9035-701bfe34a5fd" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="631abe0e-026d-4f46-a209-65697a9d40e9" /dev/sda2: UUID="c5b2342e-c45a-49ce-9039-7670e6627166" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="329b8277-78bb-3d46-bd0a-fdfb8c76629d" /dev/sda1: SEC_TYPE="msdos" LABEL_FATBOOT="armbi_boot" LABEL="armbi_boot" UUID="5F4E-9DB1" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="bootfs" PARTUUID="651eafa5-90c1-b34a-88be-6db5e1c4611c" /dev/zram0: UUID="96093c4c-52ef-4482-9b77-b78a24cdf555" TYPE="swap" /dev/zram1: LABEL="log2ram" UUID="4970e224-e849-4923-bdbd-99584839f39b" BLOCK_SIZE="4096" TYPE="ext4" /dev/mtdblock0: PTUUID="ce22cf47-be9f-48cd-8ff4-cba055568687" PTTYPE="gpt" Any ideas Edited March 27, 2023 by hyma 0 Quote
hyma Posted March 27, 2023 Posted March 27, 2023 rock-3a:~:% lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 28.6G 0 disk ├─sda1 8:1 1 256M 0 part └─sda2 8:2 1 28.4G 0 part /var/log.hdd / mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 59.5G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part └─mmcblk0p2 179:2 0 58.6G 0 part zram0 252:0 0 3.8G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk is mtdblock0 ok? 0 Quote
S1120 Posted April 2, 2023 Posted April 2, 2023 Hi. Thansk a lot for this guide and topic. I'm really appretiate it. But I need help with "silent" U-boot. Now I'm running Armbian 23.02.2 Jammy on RockPi4A 1.43. System installed on Kingston A2000 512GB and perfectly booting from SPI-flash XT25F32BW soldered on the board by manufacturer. I flashed rkspi_loader-v20.11.2-trunk-v2.img from this topic using dd command. The next step is to make some cosmetic changes. I'm using vertical orientation screen and boot process for me looks no so good (boot_1, boot_2, boot_3). I decided to make u-boot with "remove-boot-messages-from-hdmi" patch from neighbour topic. So, my steps was: sudo apt install git git clone --depth=1 --branch=main https://github.com/armbian/build Then I put files board-rock-pi-4-enable-spi-flash.patch (from "patches" folder) and remove-boot-messages-from-hdmi.patch (from neighboug topic) to "userpatches" folder and run ./compile.sh u-boot BOARD="rockpi-4a" BRANCH="edge" After executing script i had linux-u-boot-rockpi-4a-edge_23.05.0-trunk--2022.07-Se092-Pbb0c-Bc990_arm64.deb in output. Then I used dpkg -x command to unpack. As a result I have rkspi_loader.img that I flashed to SPI IC using dd command. And finally my system didn't boot. The only way to make it bootable again is to flash rkspi_loader-v20.11.2-trunk-v2.img again. I tried a lot of patches combinations. So, my question is how to compile working SPI image with one of this options: 1. vertical orientaton output or 2. turned off HDMI output or 3. boot image during u-boot instead of text output Any option is ok. Or maybe somebody can compile u-boot for me with any of 3 options above? Thanks 0 Quote
dnnr Posted April 30, 2023 Posted April 30, 2023 Kingston NV2 [SNV2S/250G] - working well. Thanks TS 0 Quote
Andre Van Der Weide Posted August 2, 2023 Posted August 2, 2023 Also working perfect on a Rock pi 4b+ v1.73 with boot in spi and SSD 960 EVO NVMe M.2 250 GB thanks 0 Quote
evadim Posted August 17, 2023 Posted August 17, 2023 (edited) Spent a few days trying various combinations with Rockpi4c and Armbian 23.05.1 Bookworm with Linux 6.1.30-rockchip64 to get it working. Bootoader in SPI just hang at early start: U-Boot TPL 2022.07-armbian (May 27 2023 - 19:29:37) Few times I saw something like "DRAM init failed -19". Guide to flash SPI on Radxa Wiki completely changed to rkdeveloptool and maskrom mode. After a while I found which image nand-sata-install uses and flash via rkdeveloptool /usr/lib/linux-u-boot-current-rockpi-4c_23.05.1_arm64/rkspi_loader.img instead of Radxa uboot spi img. Works from first try! In boot console I see this warning: Loading Environment from SPIFlash... SF: Detected XT25F32B with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment Not sure what changed. I hope this helps someone. SSD is cheap (but with DRAM onboard) A-Data XPG SX6000LNP Lite 128Gb Edited August 17, 2023 by evadim 0 Quote
Energokom Posted August 26, 2023 Posted August 26, 2023 (edited) If the system does not start after writing to SPIOR, then you can clean it with the command dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=4 Edited August 26, 2023 by Energokom 0 Quote
evadim Posted October 11, 2023 Posted October 11, 2023 Is there way to disable SPI flashing after u-boot upgrade? 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.