Search the Community

Hello, I have this combinations which was probably a mistake, because I cannot get the camera running whatever I do. Was someone able to get it up or give me some advice, lead me a good direction? Thanks a lot.

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)

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!

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.

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.

Hi, I'm new to armbian and I've started with RockPi4b board. I would like to add fan control with PWM, but adding pwm (or pwm0) overlay doesn't work. I can't also find the overlay for it at /boot/dtb-5.8.6-rockchip64/rockchip/overlay/. Is it supported? I've checked and the /sys/class/pwm/pwmchip0 is present, but accessing export, as described here : doesn't work and /sys/class/pwm/pwmchip0/pwm0 is not present. I've tried to find pwm access examples for this board, but none of it works on armbian (all are vendor builds specific). Can anybody point me in the right direction or give any hint how to enable pwm? EDIT : I've managed to enable/dosable PWM pin with sudo mraa-gpio set 11 1 Although, its GPIO, rather PWM access so I can't control the FAN speed and only power on/off the fan.