November 27, 20232 yr Hi people! I'm trying to use Armbian 23.8.1 CLI with the Rock 4 SE board without success. I write the eMMC in the classic way: xzcat Armbian_23.8.1_Rockpi-4b_bookworm_current_6.1.50.img.xz | sudo dd of=/dev/sdb bs=4M status=progress; sync but nothing seems to happens, i have only the green led on, the blue led is not blinking and the display says "no hdmi signal". No problems with the image from radxa. Do you have any idea what's going wrong?
November 28, 20232 yr Author Hi, thank for the answer, the serial is really useful! The problem was the screen, i had used an HDMI/DP converter. I changed the monitor with one with HDMI and now it works perfectly. Thank you very much, you saved me a lot of hours!
November 30, 20232 yr Author Well probably was just a lucky shot. I checked the image with hexdump and at least first MBs are identical, so data should be ok. The power comes from a fast charger with a proper cable, both of a known brand. Trying with other 2 devices (still rock4 se) problems are back: ------------------------------------------------------------------------------ U-Boot TPL 2022.07-armbian (Aug 22 2023 - 15:14:34) Channel 0: col error Cap error! Channel 1: col error Cap error! 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... <--------[OFTEN IS STUCK HERE] ------------------------------------------------------------------------------ trying again and again (with other power supply, with or without devices....), get stuck in different positions: ------------------------------------------------------------------------------ U-Boot TPL 2022.07-armbian (Aug 22 2023 - 15:14:34) Channel 0: col error Cap error! Channel 1: col error Cap error! 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 TPL 2022.07-armbian (Aug 22 2023 - 15:14:34) Channel 0: row errorCap error! Channel 1: col error Cap error! no 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... <--------[SOMETIMES GOES FURTHER] U-Boot SPL 2022.07-armbian (Aug 22 2023 - 15:14:34 +0000) Trying to boot from MMC2 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 Trying to boot from MMC1 NOTICE: BL31: v1.3(release):845ee93 NOTICE: BL31: Built : 15:51:11, Jul 22 2020 NOTICE: BL31: Rockchip release version: v1. detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: INFO: If lpddr4 need support multi frequency, INFO: please update loader! INFO: Currectl index[0] freq=400MHz INFO: freq=800MHz INFO: plat_rockchip_pmu_init(1196): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE inin SMC_UNK ERROR: Error initializing runtime service opteed_fa BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 <--------[CAUGHT ALSO HERE] U-Boot 2022.07-armbian (Aug 22 2023 - 15:14:34 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Radxa ROCK Pi 4B DRAM: 1.5 GiB <--------[CAUGHT ALSO HERE] ------------------------------------------------------------------------------ By insisting, everything starts working properly. It behaves like a diesel engine...
November 30, 20232 yr Author Some hints: --------------------------------------------- U-Boot TPL 2022.07-armbian (Aug 22 2023 - 15:14:34) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=4 CS0 Row=16/15 CS=1 Die BW=16 Size=768MB Channel 1: LPDDR4, 50MHz BW=32 Col=9 Bk=4 5 CS=1 Die BW=16 Size=384MB ... ... ... SoC: Rockchip rk3399 Reset cause: POR Model: Radxa ROCK Pi 4B DRAM: --------------------------------------------- My impression is that it doesn't take the right RAM size, so it only works when it luckily addresses enough space...
February 5, 20242 yr Same here: U-Boot TPL 2022.07-armbian (Nov 26 2023 - 16:22:55) Channel 0: col error Cap error! Channel 1: col error Cap error! 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... I'm not able to get past that whatever I do. It boots Radxa own debian image, but it's old and bulky with gui which I don't need. Happens on both CLI and Desktop image: Armbian_23.11.1_Rockpi-4c_bookworm_current_6.1.63.img.xz Armbian_23.11.1_Rockpi-4c_jammy_current_6.1.63_xfce_desktop.img.xz
February 5, 20242 yr Forgot to add - SDcard boot, don't have eMMC It seems to be RAM training problem. That is why on OP it fails on different stages. https://lore.kernel.org/all/20220811075848.1791050-1-lee@kernel.org/T/ Edited February 7, 20242 yr by janno
February 24, 20242 yr Try using Armbian builder to build an image there is a 4se config in there I added it after helping some one in irc one night. I don't recall the state. I don't have a 4se https://github.com/armbian/build/blob/main/config/boards/rock-4se.csc
March 5, 20242 yr We found the same issue. It does boot with the dedicated rock-4se target, hence pretty surely an issue with the updated DDR blob. The Armbian repo ships functional U-Boot packages already: https://apt.armbian.com/pool/main/l/linux-u-boot-rock-4se-current/ But WiFi does not work. We tried with rk3399-rock-4se.dtb as well as rk3399-rock-pi-4b.dtb (as used in armbianEnv.txt with rock-4se target). Still trying to figure out what is missing: The correct brcmfmac driver loads. With ROCK 4 SE device tree, it tries to load the brcm/brcmfmac43455-sdio.radxa,rock-4se.bin, else brcm/brcmfmac43455-sdio.radxa,rockpi4b.bin, but actually it uses brcm/brcmfmac43455-sdio without the device-specific appendix anyway. Also creating symlinks for the device-specific suffix mutes the warning, but does not fix WiFi: The adapter is just not showing up in e.g. `ip link`. Does someone know why the ROCK 4B device tree is explicitly used for the ROCK 4 SE target? For the U-Boot config, there is a note that upstream U-Boot ROCK 4 SE target is/was broken, but no hint why the 4B device tree is used. I thought that some patches might patch the 4B device tree only, but as far as we tested, both device trees generally work, but with none of them onboard WiFi is working on the ROCK 4 SE. Edited March 5, 20242 yr by MichaIng
March 13Mar 13 I just tested the latest Armbian distros, Armbian 26.2.0-trunk.493 XFCE and Armbian 26.2.0-trunk.493 Minimal / IOT, and none worked. Then I tried Radxa system images, rock-4se_bookworm_kde_r4.output_512.img.xz did not work. So I got confused because my Rock 4SE v 1.53 SBC worked a long time ago. Found backup of old boot image, which I used with the NVMe drive, because it could not boot on its own. And do you know what? Finally, I saw a picture on the screen with boot log information, which made me happy because it proved my SBC had not died. Then I started looking at some old system images for this board and found one which is booting, it is rock-4se_debian_bullseye_kde_b38.img. Edited March 13Mar 13 by technik007_cz
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.