CaWeissWz
Members
-
Joined
-
Last visited
-
-
Unfortunately I was not able to work on this topic appropriately and thus could not provide any helpful information. But in the meantime, others have done a lot of work on this topic. Thank you @uablrek for the link. So I tried and built a new image (from main branch) after https://github.com/armbian/build/pull/8449 had been merged. I can confirm that the Rock 4SE now boots with this version. Thanks to everyone involved for the solution!
-
-
Yes, I know how to compile images. I'm still learning how to use git efficiently, though. Git bisect, I had never heard of before; but from what I read, is seems to be the right tool to find the breaking commit. But before I start into this possibly lengthy process, I came up with one theory, that I intend to check first: The initial assumption was, that the error is due to an API incompatibility in the Arm Trusted Firmware. My first intention was, to check if a newer version of the ATF was available, I just didn't know for wich part exactly I should look. Now I found out, that the working Image starts the "BL31"-thing right at the point where the current images fail: So, the first thing for me to check will be which version of "BL31" is used for the current images and if a newer version would be available and could be used instead. Unfortunately, i might not be able to work on this until next week. But I will report back as soon as there is new information.,
-
-
My Radxa Rock 4SE does not boot since community-build 25.8.0-trunk.228. Current local builds based on the "main" branch are also affected. The bootloader log gives the following error: Checking hash(es) for config config-1 ... OK Checking hash(es) for Image atf-1 ... sha256+ OK Checking hash(es) for Image u-boot ... sha256+ OK Checking hash(es) for Image fdt-1 ... sha256+ OK Checking hash(es) for Image atf-2 ... sha256+ OK Checking hash(es) for Image atf-3 ... sha256+ OK ERROR: not expected type found -4001165690437497392 This source suggests, that it might be a problem with the ATF. However, my knowledge about details of the boot process are unforunately not sufficient to find a solution to this problem. How to reproduce? Download https://github.com/armbian/community/releases/download/25.8.0-trunk.228/Armbian_community_25.8.0-trunk.228_Rock-4se_bookworm_current_6.12.33_minimal.img.xz Install on SD card Try to boot Rock 4 SE from SD card image
-
In the meantime I was able to compile a customized armbian image with the Designware I2C driver enabled. This solved the problem for me ... until a kernel update was installed via apt. This made my DSI display unusable again. What I did: I used the official buildsystem from https://github.com/armbian/build. In the kernel config menu, I selected "Device Drivers / I2C support / I2C Hardware Bus support / Synopsis DesignWare I2C adapter" to be included as a module ("<M>"). This led to the line "CONFIG_I2C_DESIGNWARE_CORE=m" being present in the kernel configurafion file 'linux-bcm2711-current.config'. Finally I recieved the working armbian image with the modules 'i2c-designware-core.ko' and 'i2s-designware-platform.ko' being present under /usr/lib/modules/... To be able to perform kernel updates in the future, it would really be helpful to have the drivers already in the official armbian builds. What can I do to improve the situation? I came here to seek the 'standard' support. Should I try to raise an issue on github instead? I would really like to assist with this topic, but I am not familiar with the required processes and, at the end, do not want to create more confusion than it's worth.
-
A display connected to the DSI connector of Raspberry Pi 5 does not work when using Armbian. However, the display works perfectly when using the Raspberry OS. My OS image is: Armbian_25.2.2_Rpi4b_bookworm_current_6.12.15_cinnamon_desktop Dmesg reveals the following information: [ 13.283052] mipi-dsi 1f00118000.dsi.0: deferred probe pending: mipi-dsi: supplier 2.reg_bridge not ready [ 13.283060] platform 1.panel_disp: deferred probe pending: platform: wait for supplier /axi/pcie@120000/rp1/i2c@88000/reg_display@45 This forum post suggests, that the problem is due to the missing I2C driver "CONFIG_I2C_DESIGNWARE_PLATFORM": https://forums.raspberrypi.com/viewtopic.php?t=375851 And indeed, on the working Raspberry OS image, i find the following files in the directory /lib/modules/.../kernel/drivers/i2c/busses: - i2c-designware-core.ko.xz - i2c-designware-platform.ko.xz These files are not present on the Armbian image, I assume that these are the missing drivers. Could someone please add the drivers to the build configuration, so that DSI displays will work in the future on RPi5? https://paste.armbian.com/owihivazuc