Jump to content

Search the Community

Showing results for tags 'rockpi-5b'.

  • 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
    • Orange Pi 5
  • 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

Found 13 results

  1. Hello everyone, I would like to thank @lurk101 very much for his patience in helping me how to boot Armbian directly to NVMe in my ROCK5B. I could do that with the Official release 22.11 Jammy with Gnome from the website. The PSU I am using is a dumb 5V 3A which I used to power my Raspberry Pi 4. As I could boot the OS directly from NVMe, I asked if he would mind if I shared the information with you. He answered he doesn't, so here we go... However, I was not able to use Ethernet port neither my wifi m.2 adapter, so there is no network connection... If I have more information I will share with you, thanks a lot!!
  2. A test version of Armbian images to run from NVMe without having to write the curve of the official u-boot version to SPI (which breaks the launch of other systems from SD cards and other media). The whole system works completely with NVMe . https://disk.yandex.ru/d/V5AxXNN2yJnOfg The installation of the system on NVMe and u-boot in SPI was checked using the standard tools of the armbian-config utility. Everything works correctly. Also in this new u-boot, the ability to start the system in EFI mode is available. To install a system with EFI\grub on NVMe. Install a new bootloader in SPI. Start the system from the SD card and burn the system image with the EFI\grub DD utility to NVMe. images with EFI\grub support are located in directories with the extension "EFI"
  3. lurk101

    Rock-5b PWM

    With Linux rock-5b 5.10.72-rockchip-rk3588 #trunk.0102 SMP Sat Nov 5 07:56:18 UTC 2022 aarch64 GNU/Linux I see only one PWM controller pi@rock-5b:~$ ls /sys/class/pwm/pwmchip1/ device export npwm power subsystem uevent unexport pi@rock-5b:~$ cat /sys/class/pwm/pwmchip1/npwm 1 How do I figure out its header pin assignment? Is there a device tree overlay to expose all 4 PWM controllers?
  4. Hello to everybody, I am using rock 5b, PCB Version 1.42 with Armbian 22.11 CLI. I would like to connect IQaudIO DigiAMP+ based on the TAS5756 (https://shop.max2play.com/en/iqaudio-digiamp.html). According to the GPIO pinout of ROCK 5b and the datasheet of DigiAMP+ (page 21), this seams to be feasible from the electrical perspective. But the software perspective overwhelmes me as a linux novice. If I understand it correctly, I need more or less two things: a device tree overlay to activate the appropriate GPIOs with their I2S and I2C functionality and to tell the kernel about the attached device (DTS file or the compiled DTO file) an appropriate driver (kernel module) for the device I have not found any useful examples about how to write device tree overlay files for the rock 5 with I2S support. Does anybody out there have a generic I2S example for rock5b or maybe even a working device tree file for the the DigiAMP+? According to https://dev.seemoo.tu-darmstadt.de/bcm/bcm-rpi3/-/blob/master/kernel/arch/arm/boot/dts/overlays/iqaudio-dacplus-overlay.dts, the TAS5756 is compatible with the PCM5122. But according to the file /boot/config-5.10.110-rockchip-rk3588, line 5168 (content is # "CONFIG_SND_SOC_PCM512x_I2C is not set"), the standard armbian kernel is not compiled with support for this chip. Is this assumption correct? Thank you in advance! Regards, Klaus
  5. I installed the latest Armbian image and used a 1080P portable monitor to finish the install process. But when I use my bigger monitor with 2560x1440 resolution, it cannot output signal via HDMI. I searched about it, but most of them are about windows/x86 contents. Any idea about that?
  6. Hey all. Running the Dec 9th build of Armbian 22.11.2 Debian Bullseye CLI, and I've been running in to issues with consistently remotely connecting to the board. While ssh and other direct connections (IP:Port for services like Nextcloud, etc) work for a bit after a recent reboot, after some unknown amount of uptime I'm unable to connect to the board through any new remote connections. Attempting an SSH session provides me the error ssh: connect to host 192.168.50.5 port 22: No route to host When connected via the serial console, I am able to verify that the board has internet access while it is refusing these remote connections on the local network. When I restart the board it starts accepting remote connections again. Not sure what to do to troubleshoot this or if anyone else is dealing with the issue.
  7. I tried the "Armbian_22.11.1_Rock-5b_bullseye_legacy_5.10.72.img.xz" image on my Rock 5B. It worked on an SD card, but when I loaded it on an NVME drive on the build in M.2 slot, it worked with neither the SPI Boot image with armbian-install.sh, nor the SPI image from radxa. When I have SPI loaded, and I have the SD Card installed, it just seems to load from the SD Card. When I remove the SD card, and boot the system. It seems to just stay with the LED with the blue and green elements on. I've waited several minutes without it booting. I was able to get it to successfully boot once, but never again.
  8. Hi, I've flashed the Armbian SPI image following these instructions: https://wiki.radxa.com/Rock5/install/spi I've flashed this image: Armbian_22.11.2_Rock-5b_jammy_legacy_5.10.110_gnome_desktop.img.xz to a M.2 NVME SSD I own a DVB-S2 USB 2.0 device from PCTVSystems: https://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_DVB-S2_Stick_(461e) currently working in a RPi4 with OSMC. Firmware file (dvb-demod-m88ds3103.fw) is on /lib/firmware When I connect it to Rock5b I can see it with lsusb command Bus 002 Device 003: ID 2013:0258 PCTV Systems DVB-S2 Stick 461e and dmesg usb 2-1: new high-speed USB device number 3 using ehci-platform usb 2-1: New USB device found, idVendor=2013, idProduct=0258, bcdDevice= 1.00 usb 2-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2 usb 2-1: Product: PCTV 461 usb 2-1: Manufacturer: PCTV usb 2-1: SerialNumber: 0011530470 But I fail to see it on /dev (on the RPi4 i can see it as /dev/dvb) Any suggestion? How to diagnose this particular issue? Thanks, chapas
  9. Hello I just installed armbian (Gnome) on my NVME and all seems to work great (without SD card). So, the first issue I have is the resolution of the screen. I add 2560x1440 (1920x1080 was the maximum before) but the test in this mode not working. I think the cause is than I copy/paste the mode from a post on internet. In fact, cvt is not installed and impossible to calculate mysel the vesa CVT modline. How can I install CVT ? bash: cvt: command not found Thanks a lot Anakin
  10. Howdy, Just wanted folks to know that debian bullseye is generally getting what I need done. Specially Welcome to Armbian 22.11.1 Bullseye with Linux 5.10.72-rockchip-rk3588 is working. It is working headless just fine. Now what is not working for me. The HDMI is not showing up at all. Between my KVM and ultra wide monitor it may not be an OS issue. SD-card boot is the way I am going. Manual partitioning of the NVME was needed to install. It felt like I needed to reboot a few times to get the NVME to boot. Overall it was a better experience than the experience on the Firefly station P2 competing with Station OS. Thanks for all the work.
  11. I am trying to provision QEmu/KVM to run a Kubernetes cluster based on Ubuntu Cloud Image instances. I am using the latest release of Armbian on 16GB Rock 5B. Release kernel. After a relatively smooth setup I am able to provision and run instances. virt-install --connect qemu:///system --virt-type kvm --name virt1 --ram 2048 --vcpus=2 --os-variant ubuntu22.04 --disk path=/root/VMImages/virt1/virt1.qcow2,device=disk --disk path=/root/VMImages/virt1/virt1-seed.qcow2,device=disk --import --network network=default,model=virtio,mac=$MAC_ADDR --noautoconsole Everything works and I am able to log into the instance, but for some reason I am seeing 100% CPU load when the instance is idle. Obviously that is not good. Any pointers are welcome. Thanks.
  12. Igor

    Mainline kernel

    Download is possible from CI pipeline: https://github.com/armbian/build/releases Boot log: This board is looking for maintainer(s) and (this) forum moderator (contact @Werner).
×
×
  • Create New...