All Activity

Hi, I hate you (sorry just joke) 🙂 I have no UART to USB cable so I found old Teensy 3.2 board. Made program for Serial to USB bridge. Updated SPI flash with new firmware with debug mode. And.... It works now! Dam or huray... 😉 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB Manufacturer ID:0x6 CH0 RX Vref:27.5%, TX Vref:25.8%,25.8% CH1 RX Vref:25.8%, TX Vref:25.8%,25.8% CH2 RX Vref:27.9%, TX Vref:24.8%,24.8% CH3 RX Vref:27.1%, TX Vref:24.8%,24.8% change to F1: 528MHz change to F2: 1068MHz change to F3: 1560MHz change to F0: 2112MHz out U-Boot SPL board init U-Boot SPL 2017.09-gd1cf49135ee-220414-dirty #stephen (May 23 2024 - 19:39:28) Trying to boot from MMC2 MMC: no card present mmc_init: -123, time 0 spl: mmc init failed with error: -123 Trying to boot from MTD2 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK ## Checking uboot 0x00200000 ... sha256(25a398ffe0...) + OK ## Checking fdt 0x0031e9f8 ... sha256(5bee414074...) + OK ## Checking atf-2 0xff100000 ... sha256(4b2065349b...) + OK ## Checking atf-3 0x000f0000 ... sha256(aa71013e72...) + OK Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 489.724/719.766 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45 NOTICE: BL31: Built : 10:11:21, Dec 27 2023 INFO: spec: 0x1 INFO: code: 0x88 INFO: ext 32k is not valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework 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 U-Boot 2017.09-gd1cf49135ee-220414-dirty #stephen (May 23 2024 - 19:39:28 +0800) Model: Radxa ROCK 5B MPIDR: 0x81000000 PreSerial: 2, raw, 0xfeb50000 DRAM: 16 GiB Sysmem: init Relocation Offset: eda3f000 Relocation fdt: eb9f96c0 - eb9fecc8 CR: M/C/I Using default environment DM: v2 mmc@fe2c0000: 1, mmc@fe2e0000: 0 Bootdev(assign): mmc 0 MMC0: HS400 Enhanced Strobe, 200Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition Failed to load DTB, ret=-2 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 Model: Radxa ROCK 5B MPIDR: 0x81000000 CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A) b0pll 24000 KHz b1pll 24000 KHz lpll 24000 KHz v0pll 24000 KHz aupll 24000 KHz cpll 1500000 KHz gpll 1188000 KHz npll 24000 KHz ppll 1100000 KHz aclk_center_root 702000 KHz pclk_center_root 100000 KHz hclk_center_root 396000 KHz aclk_center_low_root 500000 KHz aclk_top_root 750000 KHz pclk_top_root 100000 KHz aclk_low_top_root 396000 KHz Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. MMC: no card present mmc_init: -123, time 0 pcie@fe150000: PCIe Linking... LTSSM is 0x0 pcie@fe150000: PCIe Linking... LTSSM is 0x0 pcie@fe150000: PCIe Linking... LTSSM is 0x6 pcie@fe150000: PCIe Linking... LTSSM is 0x210023 pcie@fe150000: PCIe Link up, LTSSM is 0x230011 pcie@fe150000: PCIE-0: Link up (Gen3-x2, Bus0) pcie@fe150000: invalid flags type! Device 0: unknown device Device 1: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3920 bytes read in 8 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0:1 172 bytes read in 8 ms (20.5 KiB/s) 26373283 bytes read in 112 ms (224.6 MiB/s) 32436736 bytes read in 142 ms (217.8 MiB/s) 163397 bytes read in 28 ms (5.6 MiB/s) Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' Fdt Ramdisk skip relocation No misc partition ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 26373219 Bytes = 25.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0x08300000 Booting using the fdt blob at 0x08300000 reserving fdt memory region: addr=8300000 size=8e000 Using Device Tree in place at 0000000008300000, end 0000000008390fff can't found rockchip,drm-logo, use rockchip,fb-logo WARNING: could not set reg FDT_ERR_BADOFFSET. failed to reserve fb-loader-logo memory WARNING: could not set reg FDT_ERR_BADOFFSET. Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000) Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000) Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000) Total: 2321.467/3095.859 ms Starting kernel ...

What's the problem with closed source drivers? Why aren't they used on linux?

u-boot-radxa-rk3588/legacy: use 000.patching_config; fix boot from SD when combined with from-factory eMMC blobs (TEE mismatch) u-boot-radxa-rk3588/legacy: rewrite u-boot patches, no changes u-boot-radxa-rk3588/legacy: add 0000.patching_config.yaml and move all null-patches into dt and defconfig dirs as bare files DTs and defconfigs should be identical to their null-patch equivalents u-boot-radxa-rk3588/legacy: rewrite nanopc_t6_defconfig -- no changes CONFIG_REGULATOR_RK806=y seems a leftover that's not really used? u-boot-radxa-rk3588/legacy: rewrite nanopc_cm3588_defconfig -- no changes CONFIG_REGULATOR_RK806=y seems a leftover that's not really used? u-boot-radxa-rk3588/legacy: nanopc_cm3588_defconfig: disable OPTEE (for OOB working boot with from-factory blobs in eMMC) makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC Armbian itself doesn't ship TEE blobs when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot but then proceeds to fail with optee api revision is too low disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian u-boot-radxa-rk3588/legacy: nanopc_t6_defconfig: disable OPTEE (for OOB working boot with from-factory blobs in eMMC) makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC Armbian itself doesn't ship TEE blobs when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot but then proceeds to fail with optee api revision is too low disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian View the full article

Last week I attended the GStreamer spring hackfest in Thessaloniki to work on the PipeWire GStreamer elements and connect with the community. View the full article

@usual user@Efe Çetin it seem to work with i burned an sd card with the new compiled Armbian-unofficial_24.8.0-trunk_Orangepi5-plus_bookworm_legacy.5.10.160 image . I boot from the sdcard It seems to work as i have no crash copying a 250GB file between a usb ssd and the mvne. I'm trying now memtester 31G. ... ... trying mlock ...Killed BUT not crash trying memtester 30G is working ... ... and it does not crash. @Efe Çetin Is it possible to make the official release working for the 32Gb version ?

Since a board with 16G RAM practically has a little less than 16 GiB RAM, probably mem=16G limits it a little too less to prevent the crash 100% reliably, while mem=15G would do. I don't know how exactly those limits are applied, and at which point exactly the power usage of the RAM raises above the critical point (in case really this is the reason for the crashes), so this is just a guess which can be tested.

Yes. Added it to other arguments, like this: extraargs=fsck.mode=force fsck.repair=yes mem=16G free -h shows 16G after this.

@Eddie as @MichaIng explain me did you add the next in the armbienEnv.txt ?

I can add that Orange Pi Zero 3 users have similar problems, i.e. after turning on the power or, for example, after reboot. This is not a cyclical phenomenon. So when it happens that you need to reboot remotely, it may turn out that Orange Pi Zero 3 requires physical intervention by turning the power on and off.

https://debug.armbian.de

https://debug.armbian.de

Hi, New builds (hosted by armbian AND self compiled) of armbian do not post / boot at all. Completely black screen on hdmi outpout. Ethernet link lights do not light up. It's like there is no bootable media inserted (it definitely is). I have tried many combinations of different kernels and ubuntu versions. None work. Board: nanopc t6 8gb ram They used to work, and archived copies from november 2023 work, booting perfectly. I also compiled one back then which also worked. But now this is not working any more. Does anyone have idea why it no longer posts? Thanks Luke

Hi, I do not konow, it this is the right place to raise the this ticket. But in stable releases of Armbian it works fine, but there is no video acceleration. I have tried Kodi on Armbian Noble Gnome + trunk MESA/VPU: Armbian_24.8.0-trunk.85_Rock-5b_noble_vendor_6.1.43_gnome-oibaf_desktop.img Kodi falling when I'm trying to install some of extensions. For example https://repo.sc2.zone/ Crash log in the attachment. System log: 2024-06-05T12:01:28.534687+02:00 rock-5b kodi.desktop[3739]: Fatal Python error: PyImport_AppendInittab: PyImport_AppendInittab() may not be called after Py_Initialize() 2024-06-05T12:01:28.535024+02:00 rock-5b kodi.desktop[3739]: Python runtime state: initialized 2024-06-05T12:01:28.535112+02:00 rock-5b kodi.desktop[3739]: Thread 0x0000ffff3afde0c0 (most recent call first): 2024-06-05T12:01:28.535191+02:00 rock-5b kodi.desktop[3739]: <no Python frame> 2024-06-05T12:01:28.612980+02:00 rock-5b kodi.desktop[3732]: Aborted 2024-06-05T12:01:28.640388+02:00 rock-5b kodi.desktop[3732]: Crash report available at /home/tomogo/kodi_crashlog-20240605_120128.log kodi_crashlog-20240605_115433.log

Hello @ALIGMSTEN, I want to use UART5, which is located on the TX-PH2 and RX-PH3 pins. As far as I understand, this UART is initially disabled. To enable it, I tried using the command armbian-config -> System -> Hardware, but I couldn't do it because nothing was displayed in the graphical interface (as shown in the screenshot above). After doing some research, I started experimenting with the /boot/armbianEnv.txt file. I added the line overlay_prefix=sun50i-h616. After rebooting the board, I tried using armbian-config -> System -> Hardware again, and now the interface displays the hardware peripherals along with the UART5 that I need. By enabling it, I can receive data through the TX-PH2 and RX-PH3 pins via /dev/ttyS1. So, I have essentially solved my problem, but I still have a few questions: Is there a simpler or recommended way to enable UART5 on this board without manually editing the /boot/armbianEnv.txt file? Are there any potential issues or pitfalls I should be aware of when using this method? Is it a bug that the interface in armbian-config -> System -> Hardware did not display initially on various versions of the system? Thank you.

Hi, I've installed Armbian_24.5.1_Rock-5b_bookworm_vendor_6.1.43_cinnamon_desktop.img on my Rock 5b and when I have tried to do apt update get error message with armbian.com url. (timeout error) I did all necessary and now it work fine. But for dev info, there is some problem probably with all Stable images.

Many thanks to all those who helped me launch the TV-box, I am very grateful to these people who help out newcomers with their advice. Thanks jock, I deleted brltty using the command: and oh, a miracle the board worked, the connection to the printer took place!

Hi, I have tried Rock 5b images with Kernel 6.8.10. Any of image I've tested will not start. No LED flashing, no HDMI signal.. nothing. The others with Kernel 6.1.43 starts fine.

Hello @Dmytro Lazor UART is enabled by default, you can use a usb to ttl converter at a baud rate 115200 to connect to a serial consel. Please be more specific what you are trying to achieve?

No matter which DTB I use, HDMI doesn't respond. What's going on？

Hello! Can't say if a step is missing, normally an sdcard with multitool on it is sufficient to let it boot from sdcard. I don't know if you have an ancient version installed without the sdcard boot or a very new installation with the missing feature in u-boot. You may take a look to this:

Then compile it by yourself?

I have armbian-firmware-full installed. By the way, the config you mentioned in github is linux-rk35xx-legacy(kernel 5.10), not the linux-rk35xx-vendor(kernel 6.1) used in Armbian 24.5.1 Stable. This topic has also mentioned about the lost rtl8852be driver: No WiFi on latest image - Orange Pi 5 Plus - Armbian Community Forums Thanks!

Odd. It is enabled in config:https://github.com/armbian/build/blob/aa2d4696cac76148d01977f63cc831e492c0f7a2/config/kernel/linux-rk35xx-legacy.config#L2945 Have you installed armbian-firmware-full? Maybe just the firmware is missing.

Do you have a TV with hdmi port? Maybe these links can help. https://forums.raspberrypi.com/viewtopic.php?t=353936&start=50 https://forums.raspberrypi.com/viewtopic.php?t=24679&start=225

Sorry, I haven't got time to tinker with it. I'm staying with vendor kernel and trying to get nextcloud running, so 6.8 is not a priority for me now. I don't think it's possible to just add this overlay at boot time. I wanted to recompile the kernel with modified dts and then include this overlay. Why I think it's necessery is because of the __symbols__ node in decompiled versions of dtb's. 6.1 dp0_in_vp1 = "/dp@fde50000/ports/port@0/endpoint@1"; dp0_in_vp2 = "/dp@fde50000/ports/port@0/endpoint@2"; dp0_out = "/dp@fde50000/ports/port@1/endpoint"; hdcp1 = "/hdcp@fde70000"; hdmi0 = "/hdmi@fde80000"; hdmi0_in = "/hdmi@fde80000/ports/port@0"; hdmi0_in_vp0 = "/hdmi@fde80000/ports/port@0/endpoint@0"; hdmi0_in_vp1 = "/hdmi@fde80000/ports/port@0/endpoint@1"; hdmi0_in_vp2 = "/hdmi@fde80000/ports/port@0/endpoint@2"; edp0 = "/edp@fdec0000"; edp0_in_vp0 = "/edp@fdec0000/ports/port@0/endpoint@0"; edp0_in_vp1 = "/edp@fdec0000/ports/port@0/endpoint@1"; edp0_in_vp2 = "/edp@fdec0000/ports/port@0/endpoint@2"; dp1 = "/dp@fde60000"; dp1_in_vp0 = "/dp@fde60000/ports/port@0/endpoint@0"; dp1_in_vp1 = "/dp@fde60000/ports/port@0/endpoint@1"; dp1_in_vp2 = "/dp@fde60000/ports/port@0/endpoint@2"; dp1_out = "/dp@fde60000/ports/port@1/endpoint"; hdmi1 = "/hdmi@fdea0000"; hdmi1_in = "/hdmi@fdea0000/ports/port@0"; hdmi1_in_vp0 = "/hdmi@fdea0000/ports/port@0/endpoint@0"; hdmi1_in_vp1 = "/hdmi@fdea0000/ports/port@0/endpoint@1"; hdmi1_in_vp2 = "/hdmi@fdea0000/ports/port@0/endpoint@2"; edp1 = "/edp@fded0000"; edp1_in_vp0 = "/edp@fded0000/ports/port@0/endpoint@0"; edp1_in_vp1 = "/edp@fded0000/ports/port@0/endpoint@1"; edp1_in_vp2 = "/edp@fded0000/ports/port@0/endpoint@2"; 6.8 sys_grf = "/syscon@fd58c000"; hdptxphy0_grf = "/syscon@fd5e0000"; hdmi0 = "/hdmi@fde80000"; hdmi0_in = "/hdmi@fde80000/ports/port@0"; hdmi0_in_vp0 = "/hdmi@fde80000/ports/port@0/endpoint"; hdmi0_out = "/hdmi@fde80000/ports/port@1"; hdmi0_out_con = "/hdmi@fde80000/ports/port@1/endpoint"; vop_grf = "/syscon@fd5a4000"; vo0_grf = "/syscon@fd5a6000"; vo1_grf = "/syscon@fd5a8000"; usb_grf = "/syscon@fd5ac000"; And overlay patches __fixups__ { hdmi0_in_vp0 = "/fragment@0:target:0"; hdmi0_in_vp1 = "/fragment@1:target:0"; hdmi1_in_vp0 = "/fragment@2:target:0"; hdmi1_in_vp1 = "/fragment@3:target:0"; }; 6.8 does not even have hdm1* nodes, so we either need to somehow change the overlay or modify dts and rebuild kernel