Jump to content

Search the Community

Showing results for tags 'rockpi-4b'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es". II. Features Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K). - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV. ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed. III. Sources This is the list of the sources used for the packages: IV. FAQ ¿Why did you use Debian Buster as a base for this implementation? It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal. ¿Why Legacy instead of Mainline? This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels. ¿Will you add new features to this implementation? No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
  2. Hi, i just received my Rock 4 Se and a 32GB eMMC module today, and i'm currently not sure if the Image is incompatible, or if my storage modules are broken. I tried emmc standalone and SD for boot with nvme (from an dell notebook) for rootfs When i use the emmc, the filesystem goes into read only as soon as i do some apt upgrade. On reboot i often end up in initramfs nd have to fsck. I could gether some dmesg output: After this trace i get a lot of I/O Errors: Im not sure if this is an os or an emmc module issue. Any guess whats going wrong here? after that i coppied the current image ( Armbian_22.11.1_Rockpi-4b_bullseye_current_5.15.80.img.xz) onto a micro SD card, addedthe nvme drive, bootet that and made an armbian-install to migrate the rootfs to the nvme. After a reboot, i could actually start to instlall software. But after a while i still had some freeze of the whole system, so i had to power the board off and turn it on again. Sadly i do not have any more output from this situation. i'm also going to try a version with older kernel, will reportlater if that worked
  3. Hi I want to modify base armbian image using choot in order to install necessary software. I am also creating user during that process. My question is how can I skip or prefill the form that appears on first run? (user creation, time zone setting etc.) I was surfing the forum and found this answer. So, I came up with few options: 1) It looks like I can prefill my desired values for the form in "/usr/lib/armbian/armbian_firstlogin" file by editing it during chroot 2) I can remove user input parts in "/usr/lib/armbian/armbian_firstlogin", but preserve other important lines, since user will be created during chroot Is this valid options or there is more proper way to do this?
  4. I enabled spi-spidev through armbian-config but it does not show in the /dev/ directory. How do i fix this?
  5. Hello everyone, I was going to purchase Rock Pi 4 model B+ (with WiFi/BT and eMMC chip). I see that Rock Pi 4 family is supported by Armbian (https://www.armbian.com/rockpi4/), however, there is no mention of models A+ and B+. There are just A, B and C+. Could you please confirm/refute that Rock Pi 4 B+ is supported by Armbian and point me to the image for that model?
  6. Trying to build an image for a RockPi 4b. The build process runs all the way through until this. This happens on Ubuntu and Debian (both latest) and on both Cinnamon and XFCE (if that matters). I haven't touched any video settings! H
  7. I am in the process to migrate a project from a Raspberry Pi 4B to a Rock Pi 4B+. Among others external devices shall be connected via WiFi AP, I2C, 1-Wire and UART to the Rock Pi. To emphasis, the system is running healthy on a Rasberry. I managed to get WiFi AP and 1-Wire up and running on the Rock Pi. Now I got stuck with UART/UART4. Armbian 22.11.1 Bullseye with Linux 5.15.80-rockchip64 I enabled UART4 via Armbian-Config. Therefore, /boot/armbianEnv.txt shows: ... overlays=i2c7 uart4 w1-gpio param_w1_pin=GPIO4_D6 param_w1_pin_int_pullup=1 ... I can take a jump wire and bridge the TX-pin (GPIO1_B0, Pin#19) and RX-pin (GPIO1_A7, Pin#21). When sending bytes to the TX-pin I am receiving them instantly on the RX-Pin. That indicates to me the UART4 is working. On my system the serial port is /dev/ttyS4, with a baud rate of 1000!!. (I am doing this test via Node Red using a standard serial node) However, if I connect my TTL-signal cable to the RX-pin (TX disconnected), I do not see anything the RX-Pin (however this setup works on the Rasberry). I have done the same test on UART (/dev/ttyS2) with same result, not showing anything. I have no experience in Armbian or Rock Pi and would appreciate any hint into which direction to look. Is the unusual baud rate of 1000 a problem, or do I need some pull-up resistors or do I need to compile another dtbo driver like for the 1-wire?
  8. Hi just a quick question What package is dt-bindings normally located in, i would assume kernel headers but i tried installation via armbian-config and couldn't see them. Can anyone confirm what package it normally is in or was i blind thanks. Was just working on adding support Waveshare Dual RS232 on SPI2, uploaded DTS to https://github.com/radxa/overlays/blob/main/arch/arm64/boot/dts/rockchip/overlays/rk3399-spi2-sc16is752.dts Atm i hardcoded the defines on machine but not ideal if it changes in the future Thanks
  9. Hello, Devices: RockPi 4b v1.5 + remotable eMMC + NVMe KingSpec M.2 NMVe SSD NE 2280 512 GB I am using instructions to erase SPI https://wiki.radxa.com/Rockpi4/dev/spi-install $ sudo rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom $ sudo rkdeveloptool db ./rk3399_loader_spinor_v1.20.126.bin Downloading bootloader succeeded. $ dd if=/dev/zero of=./zero.img bs=1M count=4 4+0 records in 4+0 records out 4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0160027 s, 262 MB/s $ sudo rkdeveloptool wl 0 ./zero.img Write LBA from file (100%) $ sudo rkdeveloptool td Test Device OK. $ sudo rkdeveloptool rd Reset Device OK. After that, insert eMMC and use instruction to write image to eMMChttps://wiki.radxa.com/Rockpi4/dev/usb-install $ sudo rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom $ sudo rkdeveloptool db ./rk3399_loader_v1.20.119.bin Downloading bootloader succeeded. $ sudo rkdeveloptool wl 0 ./Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img Write LBA from file (100%) $ sudo rkdeveloptool rd Reset Device OK. After reboot device work fine. But if I insert NVMe the system not booting, blue led just blinking and that all. I tryed several images: Armbian_22.11.0-trunk_Rockpi-4b_bullseye_current_5.15.76_minimal.img Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img rockpi-4b-debian-bullseye-xfce4-arm64-20221101-0519-gpt.img rockpi-4b-debian-buster-xfce4-arm64-20220401-0335-gpt.img The main goal is system on eMMC and stored data on NVMe (like mini NAS) Also if I use armbian-install have the same issue. Any help with it ?
  10. Hi guys, I am building armbian image for rockpi4b+ and its kernel is 6.0.11(edge version) and the bluetooth failed start up. If anyone knows what kernel 6.0.11 did that cause the problem: wzkiro@rockpi-4bplus:~$ dmesg | grep brcm [ 7.069061] brcmfmac: F1 signature read @0x18000000=0x15294345 [ 7.108688] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 7.109142] usbcore: registered new interface driver brcmfmac [ 7.236547] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 7.245940] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Feb 11 2020 11:54:51 version 7.45.96.61 (be7af2d@shgit) (r745790) FWID 01-a41d86bd es7.c5.n4.a3 wzkiro@rockpi-4bplus:~$ dmesg | grep Bluetooth [ 7.089775] Bluetooth: Core ver 2.22 [ 7.089894] Bluetooth: HCI device and connection manager initialized [ 7.089914] Bluetooth: HCI socket layer initialized [ 7.089922] Bluetooth: L2CAP socket layer initialized [ 7.089943] Bluetooth: SCO socket layer initialized [ 7.394043] Bluetooth: HCI UART driver ver 2.3 [ 7.394074] Bluetooth: HCI UART protocol H4 registered [ 7.394081] Bluetooth: HCI UART protocol BCSP registered [ 7.403820] Bluetooth: HCI UART protocol LL registered [ 7.403831] Bluetooth: HCI UART protocol ATH3K registered [ 7.405384] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 7.416771] Bluetooth: HCI UART protocol Intel registered [ 7.440646] Bluetooth: HCI UART protocol Broadcom registered [ 7.453388] Bluetooth: HCI UART protocol QCA registered [ 7.453410] Bluetooth: HCI UART protocol AG6XX registered [ 7.459664] Bluetooth: HCI UART protocol Marvell registered [ 9.738700] Bluetooth: hci0: command 0xfc18 tx timeout [ 13.642153] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 13.642193] Bluetooth: BNEP filters: protocol multicast [ 13.642220] Bluetooth: BNEP socket layer initialized [ 17.894543] Bluetooth: hci0: BCM: failed to write update baudrate (-110) [ 17.894570] Bluetooth: hci0: Failed to set baudrate [ 19.910475] Bluetooth: hci0: command 0x0c03 tx timeout [ 28.484626] Bluetooth: hci0: BCM: Reset failed (-110)
  11. Hi, my current CI build fails, and i cannot make up, whats wrong with it. It was working previously until i moved my project within the GitLab instance to another folder. Now i'm getting the following errors: tail output.log OBJCOPY lib/efi_loader/dtbdump.efi CC lib/vsprintf.o CC lib/strto.o CC lib/abuf.o OBJCOPY lib/efi_loader/initrddump.efi CC lib/date.o CC lib/rtc-lib.o CC lib/elf.o AR lib/built-in.o [ error ] ERROR in function compile_uboot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:261 -> functions/main/build-tasks.sh:128 -> functions/compilation/uboot.sh:131 -> functions/logging/traps.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated # somewhere in the middle of the compilation.log CC cmd/sf.o AR drivers/nvme/built-in.o AR drivers/power/battery/built-in.o AR drivers/power/fuel_gauge/built-in.o CC cmd/sysboot.o drivers/net/phy/phy.c: In function ‘get_phy_driver’: drivers/net/phy/phy.c:652:15: error: ‘YT_8531C_PHY_ID’ undeclared (first use in this function) 652 | if(phy_id == YT_8531C_PHY_ID) | ^~~~~~~~~~~~~~~ drivers/net/phy/phy.c:652:15: note: each undeclared identifier is reported only once for each function > AR drivers/power/mfd/built-in.o make[3]: *** [scripts/Makefile.build:254: drivers/net/phy/phy.o] Error 1 make[2]: *** [scripts/Makefile.build:394: drivers/net/phy] Error 2 make[2]: *** Waiting for unfinished jobs.... CC drivers/pinctrl/pinctrl-uclass.o CC drivers/power/pmic/pmic-uclass.o CC drivers/power/regulator/regulator-uclass.o tail compilation.log CC drivers/video/panel-uclass.o CC drivers/video/simple_panel.o TTF drivers/video/u_boot_logo.S OBJCOPY lib/efi_loader/initrddump.efi CC drivers/video/dw_hdmi.o AR lib/built-in.o AS drivers/video/u_boot_logo.o AR drivers/video/rockchip/built-in.o AR drivers/video/built-in.o make: *** [Makefile:1894: drivers] Error 2 I have tried to switch the repo mirrors, or different tags. I even deleted the entire checked out directory (build) and checked it out again. After cloning the repo and running the compile script with my config-default.config i'm ending up with the same error. Any idea, what could be wrong? I already checked the permissions (actually I'm running the compile script as root). It seems there is some issue with the network driver? my config-default.conf # Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/ # for detailed explanation of these options and for additional options not listed here # leave empty to select each time, set to "yes" or "no"> KERNEL_ONLY="no" # leave empty to select each time, set to "yes" or "no" to skip> KERNEL_CONFIGURE="no" # comma-separated list of clean targets: "make" = make clean for select> # "debs" = delete packages in "./output> # "alldebs" = delete all packages in ".> # "cache" = delete "./output/cache", "s> # "oldcache" = remove old cached rootfs> CLEAN_LEVEL="make,debs,cache" # yes: use kernel config file from previous compilation for the same branch, device family and version # no: use default or user-provided config file KERNEL_KEEP_CONFIG="yes" # comma-separated list of core modules which will be installed > # "u-boot", "kernel", "bsp", "armbian-config", "armbian-firmwar> # leave empty to build from sources or use local cache REPOSITORY_INSTALL="" BUILD_DESKTOP="yes" DEST_LANG="de_DE.UTF-8" # advanced # compile and install or install prebuilt additional packages EXTERNAL_NEW="prebuilt" # change to "branchname" to use any branch currently available. LIB_TAG="v22.08" # additions to compile 'unattended' DESKTOP_ENVIRONMENT="xfce" DESKTOP_APPGROUPS_SELECTED="editors, internet" DESKTOP_ENVIRONMENT_CONFIG_NAME="config_base" # additions to compile for the rock-pi4 BOARD="rockpi-4b" BRANCH="current" RELEASE="bullseye" # yes: will stop the script and prompt for adding userpatches (kernel, u-boot) CREATE_PATCHES="no" # creates logs in output/debug PROGRESS_LOG_TO_FILE="yes" # set to yes, to prevent cloning from git OFFLINE_WORK="no" # provides a faster download USE_MAINLINE_GOOGLE_MIRROR="yes" USE_GITHUB_UBOOT_MIRROR="yes" # create compressed archive with image file and GPG signature f> # yes - compatibility shorcut for sha,gpg,7z COMPRESS_OUTPUTIMAGE="yes"
  12. Hello. I am finished Armbian Jammy 22.05 Bulseye edge 5.16.20 gnome desktop on a Rockpi4 (rk3399). When I try to overclock from Armbian-config, it doesn't work. That is, I can enter the application, apply rockchip-rk3399-opp-2ghz.dtbo. Then reboot, go to armbian-config and set a new unlocked CPU clock speed of 2.2Ghz. But instead it is only available up to a maximum of 1.8hz. How can this be fixed? Do I have to create an image from scratch, or maybe there is some trick?
  13. tried several armbian images with kernel 5.15.76, no success! even tried to disable SPI flash, although radxa says "no SPI Flash on the board" in contrast to the 4B version official 4.4 radxa image is booting: rockpi-4b-debian-bullseye-xfce4-arm64-20221109-1447-gpt.img can someone send me armbian bullseye image with older kernel?
  14. Hi! After update to kernel 5.15.75 via apt upgrade, boot fails. Though I can flash an older image, I would prefer trying to recover existing setup and rollback to a previous kernel. What would be the best approach, ie flash image to usb, boot from usb and what then? I will appreciate any advice. U-Boot 2022.07-armbian (Oct 18 2022 - 07:36:22 +0000)SoC: Rockchip rk3399Reset cause: PORModel: Radxa ROCK Pi 4BDRAM: 3.9 GiBPMIC: RK808Core: 285 devices, 31 uclasses, devicetree: separateMMC: mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0Loading Environment from SPIFlash... jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff*** Warning - spi_flash_probe_bus_cs() failed, using default environmentIn: serialOut: serialErr: serialModel: Radxa ROCK Pi 4BNet: eth0: ethernet@fe300000Hit any key to stop autoboot: 0starting USB...Bus usb@fe380000: ehci_generic usb@fe380000: Failed to get clocks (ret=-19)Port not available.Bus usb@fe3c0000: ehci_generic usb@fe3c0000: Failed to get clocks (ret=-19)Port not available.Bus usb@fe800000: Register 2000140 NbrPorts 2Starting the controllerUSB XHCI 1.10Bus usb@fe900000: Register 2000140 NbrPorts 2Starting the controllerUSB XHCI 1.10scanning bus usb@fe800000 for devices... 1 USB Device(s) foundscanning bus usb@fe900000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) foundDevice 0: unknown deviceCard did not respond to voltage select! : -110switch to partitions #0, OKmmc0(part 0) is current deviceScanning mmc 0:1...Found U-Boot script /boot/boot.scr3185 bytes read in 19 ms (163.1 KiB/s)## Executing script at 00500000Boot script loaded from mmc 0266 bytes read in 15 ms (16.6 KiB/s)17307706 bytes read in 1665 ms (9.9 MiB/s)30540288 bytes read in 2916 ms (10 MiB/s)76240 bytes read in 48 ms (1.5 MiB/s)376 bytes read in 37 ms (9.8 KiB/s)Applying kernel provided DT overlay rockchip-rk3399-opp-2ghz.dtbo1314 bytes read in 44 ms (28.3 KiB/s)Applying kernel provided DT overlay rockchip-spi-jedec-nor.dtbo2698 bytes read in 39 ms (67.4 KiB/s)Applying kernel provided DT fixup script (rockchip-fixup.scr)## Executing script at 09000000Moving Image from 0x2080000 to 0x2200000, end=3fc0000## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17307642 Bytes = 16.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f0e8a000, end f1f0b7fa ... OK Loading Device Tree to 00000000f0e0f000, end 00000000f0e89fff ... OKStarting kernel ...efi_free_pool: illegal free 0x00000000f0f0d040efi_free_pool: illegal free 0x00000000f0f0a040[ 3.806881] Internal error: implementation fault (unsupported exclusive): 96000035 [#1] PREEMPT SMP[ 3.807711] Modules linked in:[ 3.808001] CPU: 2 PID: 224 Comm: kworker/u12:4 Not tainted 5.15.75-rockchip64 #22.08.8[ 3.808728] Hardware name: Radxa ROCK Pi 4B (DT)[ 3.809152] Workqueue: events_unbound deferred_probe_work_func[ 3.809698] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)[ 3.810334] pc : ww_mutex_lock_interruptible+0x1a4/0x308[ 3.810830] lr : phy_power_off+0x28/0xd8[ 3.811200] sp : ffff80000a713ab0[ 3.811505] x29: ffff80000a713ab0 x28: 00000000fffffffe x27: 0000000000a000c4[ 3.812167] x26: 0000000000a000c4 x25: 0000000010624dd3 x24: 0000000000900004[ 3.812828] x23: 0000000000900004 x22: 0000000000000000 x21: ffff80000f000300[ 3.813489] x20: 00000000e2808257 x19: ffff80000f000000 x18: 0000000000000001[ 3.814149] x17: 7469772074756f65 x16: 6d697420316e6567 x15: 00000000000001b5[ 3.814810] x14: ffff80000a713730 x13: 00000000ffffffea x12: ffff800009b1fd10[ 3.815472] x11: 0000000000000003 x10: ffff800009b07cd0 x9 : ffff800009b07d28[ 3.816133] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001[ 3.816793] x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : ffff80000f000300[ 3.817453] x2 : ffff00000120d880 x1 : 0000000000000000 x0 : ffff80000f000300[ 3.818113] Call trace:[ 3.818341] ww_mutex_lock_interruptible+0x1a4/0x308[ 3.818803] phy_power_off+0x28/0xd8[ 3.819142] rockchip_pcie_host_init_port+0x564/0x5a0[ 3.819616] rockchip_pcie_probe+0xf8/0x4c0[ 3.820011] platform_probe+0x68/0xd8[ 3.820359] really_probe+0xbc/0x428[ 3.820696] __driver_probe_device+0x114/0x188[ 3.821111] driver_probe_device+0xb0/0x110[ 3.821502] __device_attach_driver+0xbc/0x158[ 3.821917] bus_for_each_drv+0x7c/0xd0[ 3.822284] __device_attach+0xec/0x1a8[ 3.822644] device_initial_probe+0x14/0x20[ 3.823036] bus_probe_device+0x9c/0xa8[ 3.823396] deferred_probe_work_func+0x9c/0xf0[ 3.823817] process_one_work+0x20c/0x4c8[ 3.824199] worker_thread+0x208/0x478[ 3.824554] kthread+0x138/0x150[ 3.824863] ret_from_fork+0x10/0x20[ 3.825211] Code: c8017e60 35ffffa1 17fffd08 f9800071 (c85ffc60)[ 3.825769] ---[ end trace a4970fb3a1b23494 ]---
  15. This is for those experiencing a similar issue on the Rock Pi 4B (possibly RK3399 in general) who don't have a fix yet. On Armbian Focal current for the Rock Pi 4B the sound from both HDMI and the audio jack stopped working and became undetectable to the system (Both Pulse-audio and ALSA couldn't detect anything except hdmi-sound and even then HDMI sound did not work). I fixed the issue by rolling back to the latest "current" kernel version in armbian-config (5.10.63-rockchip64). Now the system sound has gone back to normal.
  16. Hi, i'd like to know if it's possible to disable the first run wizard (set up of root password, timezone locale etc) via armbian build framework? I have build my own image, and set the parameter DEST_LANG="de_DE.UTF-8" , but still the wizard shows up after flashing and asks me for the locale. Can i do this type of customization in the customize-image.sh? (sorry if that's a too stupid or obvious question). This is my customize-image.sh script (i have truncated it). #!/bin/bash # arguments: $RELEASE $LINUXFAMILY $BOARD $BUILD_DESKTOP # # This is the image customization script # NOTE: It is copied to /tmp directory inside the image # and executed there inside chroot environment # so don't reference any files that are not already installed # NOTE: If you want to transfer files between chroot and host # userpatches/overlay directory on host is bind-mounted to /tmp/overlay in chroot # The sd card's root path is accessible via $SDCARD variable. echo "add user rock" useradd -s /bin/bash -m -c "rock" rock -p rock echo "set hostname" hostname -b "myrockpi" echo "update armbianEnv" ARMBIANENV="/boot/armbianEnv.txt" if grep -q "console=" "$ARMBIANENV"; then sed -i 's/console=.*/console=display/g' $ARMBIANENV else echo "console=display" >> $ARMBIANENV fi Michael
  17. Hi, I am using Rock Pi 4B and want to be able to turn the system on after sleep (suspend/hibernate or any other state that would allow it). Previously, I have used MRAA library to set an interrupt, and called system("shutdown now") inside interrupt code. I did it according to the following post and according to the MRAA examples. I wrote a shell script, which executes the MRAA program. Shell script, in its turn, is called by a service on a start-up. So, with this method I was able to shutdown the system, but I cannot get out of this state via button press. I researched few posts, such as: 1, 2, and 3. It looks like either I have to modify the DTS file and generate new OS image, or perhaps there is a method to set the pin as a wake-up source inside the OS. While on Debian, when I go into directory: cd /sys/kernel/irq/<PIN #>/ There is a field called wakeup When doing cat wakeup it shows disabled Though I didn't find this folder in Armbian, but I suppose they may share similar settings for the pins. Can anyone please help me to achieve my goal? I came across another similar post, but unfortunately there was no solution there.
  18. Hello everyone, I have a screen of 1280x800 resolution. while connecting the screen to my rockpi-4b, the resolution is set to 1024x768, and there is no 1280x800 option in the display setting panel. after learning from Internet for days, I think the root is that my screen doesn't have a correct EDID information. so I made some changes to let the kernel ignores the screen's edid information and use specified edid file. The resolution is successfully set to 1280x800, the only problem is that the screen display is shaking, as the attached video shows. The edid file's timing settings are shown as below: I tried to change the settings but it doesn't work. It would be greatly appreciated if somebody can share with me the correct edid file of 1280x800 resolution. Thanks, Yuming normal video.mp4
  19. Hello everyone, I'm using SBC Rockpi4b running the Armbian system. I encountered a problem when using the Ethernet port. I connected the SBC to my laptop via an ethernet cable directly, just like what I did with the RaspberryPi. while playing with RaspberryPi (Raspbian OS) I can get the ethernet connected, the ip address is set to 168.254.xxx.xxx, i.e., private address. then I can successfully ping the RaspberryPi's ip address in my PC. while playing with the SBC (Armbian OS), the network manager seems to keep waiting a DHCP server repeatedly; and after a while (around 40 seconds) it pops up saying the ethernet disconnected; the only way I can make it connected is to set static ip addresses, but it's not the proper solution. After googling for days I realized that the two OS (Raspbian vs Armbian) run different programs for the DHCP. Raspbian apply dhcpcd, Armbian apply NetworkManager. so the first idea came to my mind was using the dhcpcd in Armbian. I have learnt that the NetworkManager can specify to use the dhcpcd as dhcp client. I followed some tutorials: 1. installing dhcpcd (sudo apt-get install dhcpcd5); 2. modifying the /etc/NetworkManager/NetworkManager.conf to add: [main] dhcp=dhcpcd it seems work at the beginning, I can see a 169.254.xxx.xxx ip address in the "ifconfig" output, but after a while it was destroyed. I checked the two services' status: pi@192.168.0.108:~$ sudo systemctl status dhcpcd ● dhcpcd.service - DHCP Client Daemon Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-07-11 14:32:17 CST; 6min ago Docs: man:dhcpcd(8) Process: 861 ExecStart=/usr/sbin/dhcpcd (code=exited, status=0/SUCCESS) Main PID: 1128 (dhcpcd) Tasks: 1 (limit: 4461) Memory: 968.0K CGroup: /system.slice/dhcpcd.service └─1128 /usr/sbin/dhcpcd Jul 11 14:33:25 rockpi-4b dhcpcd[1128]: eth0: adding address fe80::3eb:def9:d81e:17aa Jul 11 14:33:25 rockpi-4b dhcpcd[1128]: ipv6_addaddr1: Permission denied Jul 11 14:33:26 rockpi-4b dhcpcd[1128]: eth0: soliciting a DHCP lease Jul 11 14:33:26 rockpi-4b dhcpcd[1128]: eth0: soliciting an IPv6 router Jul 11 14:33:31 rockpi-4b dhcpcd[1128]: eth0: probing for an IPv4LL address Jul 11 14:33:35 rockpi-4b dhcpcd[1128]: eth0: using IPv4LL address 169.254.39.239 Jul 11 14:33:35 rockpi-4b dhcpcd[1128]: eth0: adding route to 169.254.0.0/16 Jul 11 14:33:51 rockpi-4b dhcpcd[1128]: eth0: deleted route to 169.254.0.0/16 Jul 11 14:33:51 rockpi-4b dhcpcd[1128]: eth0: adding route to 169.254.0.0/16 Jul 11 14:33:51 rockpi-4b dhcpcd[1128]: if_route (ADD): Invalid argument pi@192.168.0.108:~$ sudo systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-07-11 14:32:17 CST; 6min ago Docs: man:NetworkManager(8) Main PID: 860 (NetworkManager) Tasks: 3 (limit: 4461) Memory: 13.8M CGroup: /system.slice/NetworkManager.service └─860 /usr/sbin/NetworkManager --no-daemon Jul 11 14:34:36 rockpi-4b NetworkManager[860]: <info> [1657521276.7314] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jul 11 14:34:36 rockpi-4b NetworkManager[860]: <info> [1657521276.7344] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <warn> [1657521321.6769] dhcp4 (eth0): request timed out Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.6771] dhcp4 (eth0): state changed unknown -> timeout Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.6773] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'ma> Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <warn> [1657521321.6828] device (eth0): Activation: failed for connection 'Wired connection 1' Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.6842] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.7049] dhcp4 (eth0): canceled DHCP transaction Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.7051] dhcp4 (eth0): state changed timeout -> done Jul 11 14:35:21 rockpi-4b NetworkManager[860]: <info> [1657521321.7177] manager: startup complete It's my first post here, it will be greatly appreciated if anyone could tell me how to make the NetworkManager stop reinitializing the ethernet connection and assign a private ip address (169.254.xxx.xxx) instead? Regards, Yuming
  20. Has anyone gotten this display to work in Armbian? I'm on a Rock Pi 4b and its getting power but I can't get any kind of display out of it over the MIPI cable. I can't find any kind of documentation for how to do this, just vague discussions of overlays - I did try the rock pi raspberry pi display overlay and it doesn't work. Thanks.
  21. rock@rock-3a:~$ dmesg |grep spi [ 6.279244] spi-nor spi4.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00 [ 6.279275] spi-nor: probe of spi4.0 failed with error -2 the armbianEnv is as below. verbosity=1 bootlogo=false extraargs=systemd.unified_cgroup_hierarchy=0 overlay_prefix=rk35xx fdtfile=rockchip/rk3568-rock-3a.dtb rootdev=UUID=6359cdcb-b9a7-4930-9257-30f4e34b0a4f rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0 param_spidev_max_freq=40000000 Is there anyone know which version is ok for Rock 3a or rock p;i 4b?
  22. Hello, how to get I2C-2 device support in overlay? I have checked /boot/dtb/rockchip/overlay/README.rockchip-overlays and only i2c-7 and i2c-8 seems to be there. GPIO pins are here GPIO2_A0 and GPIO2_A1 https://wiki.radxa.com/Rockpi4/hardware/gpio#Rock_Pi_4A_.2F_4A_Plus_.2F_4B_.2F_4B_Plus_.2F_4C_.2F_4C_Plus.28.3E.3DV1.2.29_general_purpose_input-output_.28GPIO.29_connector Thank you!
  23. 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.
  24. Hello all, I have a RockPi 4B in use and wanted to connect my 7" display from Raspberry via the display port. According to these instructions, it should also work. https://wiki.radxa.com/Rockpi4/hardware/display#Raspberry_Pi_7_inch_Touch_Display But unfortunately I can't find this file under "boot" because I'm using an ARMBIAN image. How can I address this 7" display? Can anyone help me here? Best regards from Berlin Z. Matthias
  25. Hi, I'm using a RockPi 4 B as a wifi access point. Everything is working fine with good performances until the Wifi stop working, usually after 3-4 days. When that happens, dmesg is flooded with these logs : [221057.075187] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221057.075202] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 [221124.657840] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217786] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110 [221127.217806] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110 Reloading `brcmfmac` module do not fix the issue, only a reboot. I'm using the latest firmware provided by armbian-firmare : # dmesg | grep brcm Jan 28 09:36:13 crumble kernel: [240969.028417] brcmfmac: F1 signature read @0x18000000=0x15294345 Jan 28 09:36:13 crumble kernel: [240969.038152] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.041051] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.radxa,rockpi4b.txt failed with error -2 Jan 28 09:36:13 crumble kernel: [240969.042548] usbcore: registered new interface driver brcmfmac Jan 28 09:36:13 crumble kernel: [240969.149643] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 Jan 28 09:36:13 crumble kernel: [240969.149719] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available Jan 28 09:36:13 crumble kernel: [240969.149965] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Feb 11 2020 11:54:51 version 7.45.96.61 (be7af2d@shgit) (r745790) FWID 01-a41d86bd es7.c5.n4.a3 I'm not sure where to go from there. How can I debug or workaround this issue ?
×
×
  • Create New...