All Activity

As long as the board isn't dead it is starting to boot. That is why Werner directed you to how to capture the uboot booting messages via a uart connection to the board.

How do I get a log if the OS won't evenstart to boot?

yes, next week should arrive CH340G, will check with it

@jwillb00 I’m using miniarch patches with my build. This is kernel 6.12. I also have 6.14. When I have time I’ll update to 6.15. https://github.com/NickAlilovic/build/tree/v20250306/patch/u-boot/u-boot-h616 https://github.com/NickAlilovic/build/tree/v20250306/patch/kernel/archive/warpme-6.12

In this second article of a three-part series, I look at how Matt Godbolt uses modern C++ features to try to protect against misusing an API that deals with destructive state transition based on a talk he gave on making code easy to use and hard to misuse. View the full article

I don't know particular about this board so I can only give generic clues and hints how to help us helping you. What kind of dependencies you mean? There is uboot only. For variables and boot script check the contents of /boot Power loss is not an issue. Most that can happen is corrupted rootfs.

ok how i fix it? go next: sudo find /boot -type f -name '*cs0*dtbo' i see on next: rk356x-spi<BUS>-m<MUX>-cs<CS>-spidev.dtbo │ │ │ │ │ │ │ └─ номер Chip-Select (0 или 1) │ │ └─ «mux» — какие именно ноги вывели наружу (m0, m1…) │ └─ номер аппаратного SPI-контроллера (spi0…spi5) └─ серия SoC (rk3566 / rk3568 = rk356x, rk3588 …) next setup instruction: | Шаг | Команды (копируйте строка-в-строку) | Что должно получиться | | | ------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------ | ---------------------------------------- | | 1. Перейти в домашний каталог | `cd ~` | | | | 2. Создать исходник DTS | `nano rk356x-spi3-m0-cs1-spidev.dts` | вставьте текст снизу → **Ctrl-O, Enter, Ctrl-X** | | | 3. Скомпилировать в DTBO | `dtc -@ -I dts -O dtb -o rk356x-spi3-m0-cs1-spidev.dtbo rk356x-spi3-m0-cs1-spidev.dts` | файл *.dtbo* рядом | | | 4. Узнать каталог оверлеев | `export OVR=/boot/dtb/rockchip/overlay` | (у вас именно такой путь) | | | 5. Скопировать файл | `sudo cp rk356x-spi3-m0-cs1-spidev.dtbo $OVR/` | | | | 6. Проверить | \`ls \$OVR | grep cs1\` | увидите *rk356x-spi3-m0-cs1-spidev.dtbo* | | 7. Убедиться, что в `/boot/orangepiEnv.txt` есть строка | `overlays=spi3-m0-cs0-spidev spi3-m0-cs1-spidev` | если всё ок — дальше | | | 8. Перезагрузить | `sudo reboot` | | | | 9. После ребута | `ls /dev/spidev3.*` | **/dev/spidev3.0 /dev/spidev3.1** | | #6 can be ignored. at #2 next: rk356x-spi3-m0-cs1-spidev.dts <=== name code: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3566"; fragment@0 { target = <&spi3>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; spidev@1 { /* CS1 = регистр 1 */ compatible = "spidev"; reg = <1>; spi-max-frequency = <10000000>; }; }; }; }; sudo reboot after this: ls /dev/spidev3.* orangepi@orangepi3b:~$ ls /dev/spidev3.* /dev/spidev3.0 /dev/spidev3.1 make like

Ok this happened again and I'm out of ideas. @Werner Could you tell me the dependencies for the boot process on this board and how I could read out the values like the boot loader to verify they are still the same? There should be nothing wrong with cutting power right? I have had raspberry pi's be cut from power daily for years without issues and I assume it would work the same for the odroid boards?!

@deskwizard I don't know why I refer to OPi5Max, maybe I had other tab/topic open or so, but it is clear that it is about the OPi5. Now I have the ROCK5B, just cloned the Armbian Bookworm from ROCK3A but did not write SPI yet. Power up with fixed 12V in USB-C and from SD-card with Armbian rock5b vendor U-Boot. rootfs from NVMe, SATA overlay enabled for 3.5inch HDD. 5 audio cards: root@rock5b:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiphdmi0 [rockchip-hdmi0], device 0: rockchip-hdmi0 i2s-hifi-0 [rockchip-hdmi0 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchiphdmi1 [rockchip-hdmi1], device 0: rockchip-hdmi1 i2s-hifi-0 [rockchip-hdmi1 i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: rockchipdp0 [rockchip-dp0], device 0: rockchip-dp0 spdif-hifi-0 [rockchip-dp0 spdif-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 4: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card3 (unlisted) is HDMI-input I think, but disabled all in KDE settings tray except the 3.5mm plug ('headphones'). No further settings or volume change, mpv playing an mp3 instantly. I will likely do/test with 6.15 edge, also maybe 6.12 current (and other U-Boots as well). But first several mechanical/cooling things to tweak, need to drill/cut a hole for the SATA connector in the cooling metal I think.

hello guys, i hawe question, my device: orangepi 3b 8gb OS: 1.0.6 Jammy with Linux 5.10.160-rockchip-rk356x 3.3V → 3.3V → PIN 1 GND → GND → PIN 6 SCK → SPI SCK → PIN 23 MOSI → SPI MOSI → PIN 19 MISO → SPI MISO → PIN 21 SDA → CS → SPI CE0 → PIN 24 =========================== /boot/orangepiEnv.txt ``` verbosity=1 bootlogo=true extraargs=cma=128M overlay_prefix=rk356x rootdev=UUID=4b3309b6-9bbe-431d-8609-82360b5b6154 rootfstype=ext4 overlays=spi3-m0-cs0-spidev spi3-m0-cs1-spidev ``` orangepi@orangepi3b:~$ ls /dev/spidev* /dev/spidev3.0 <================= only one... cant add new spidev 3.1 and more.. for connect another mrfc522 how to fix?

@xiaobao80, The official use is the closed source Mali library. Panfrost is an open-source GPU library. It should be that the Panfrost module does not yet support rk3576

There are for once some inconsistencies in terms of prefixes across various soc families and for the other configng isn't perfect (yet ). Feel free to share your issue at its repository: https://github.com/armbian/configng/

I have the same question regarding official Armbian and S905W2. I would like to install it on a X96 Mini.

oh thanks! I didn't realize you already had an axp313 image. I've been compiling armbian with custom u-boot patches and it's been taking forever. I've been trying to adapt a dtb to my box, which one do you use? I tried including the one from miniarch but it seems like it gives warnings and I can't bypass them in the Armbian build system.

I can suggest only hard way - clear installation armbian then HA, without manipulation with driver and use rk3318-config to set device tree option

I am need to sleep more)) I stubbornly answered "y" instead of "yes" when pairing with the phone in bluetoothctl )))) It turned out to connect on "yes". 😀😀😀 Say me please an exists easier way to solve the my problem with Bluetooth?

I tried to do the following: 01) replace the driver (do symb link): ln -s /usr/lib/firmware/brcm/BCM43342.hcd /usr/lib/firmware/brcm/BCM.hcd. 02) Judging by armbianmonitor -u, the chip was recognized. 03) Installed the necessary packet: sudo apt install bluetooth -y 04) Tested that the service Bluetooth is running: sudo service bluetooth status. 05) Got "Running" 06) Only after these actions hciconfig -a gave a meaningful conclusion... 07) Next, after all this, I tried to control bluetooth via : sudo bluetoothctl 08) On the show command inside, I finally saw my device wiyh MAC and that it was active. 09) Put it into detected mode: discoverable on 10) Saw the alias rk3318-box on my phone when searching for Bluetooth devices around. 11) Despite the fact that an invitation with the same PIN code for connecting appeared both on the tvbox and on the phone, for some reason it is not possible to connect them. At the same time, for the tvbox mode Pairable: yes !!! THE REASON IS NOT CLEAR TO ME, but it is definitely associated with tvbox, because as soon as I confirm the connection (press "Y") on it, the connection is cut off... Phone confirmation does not interrupt the connection at first. WTF? I reinvent the wheel again????? PS After pair coomand on tvbox i see it: [agent] Confirm passkey 815681 (yes/no): y Failed to pair: org.bluez.Error.AuthenticationFailed

This method works for me, but I don't change Bluetooth driver's. You can also try command: apt reinstall bluez apt --fix-broken install

All the data above was collected after installing the necessary overlay in rk3318-config and then rebooting...

When using armbian-config to select an overlay ("DTO001")e.g. for uart2, one is offered the full names w/ overlay prefix, e.g. sun7i-a20-uart2. The system adds this to armbianEnv.txt: overlays=sun7i-a20-uart2 But it has also the line overlay_prefix=sun7i-a20 In the end, uart2 is not activated (no output from /dev/ttyS1) - after changing the overlay line to overlays=uart2, I can read from /dev/ttyS1. System is Armbian 25.2.2 stable (bookeworm), Armbian Linux 6.12.20-current-sunxi.

@Nick A I’m using the MiniArch image that was shared here on the forum. From it, I extracted the DTBs, Image, and other boot files, and replaced them in the Armbian image. I also took the bootloader from the MiniArch image and replaced the one in Armbian. With that, I managed to boot into Armbian, but unfortunately, no network adapters were detected.

Incbot, after set device tree option in the rk3318-config, try enter reboot command (don't reset power, need reboot only), then try hciconfig -a

I turned off overlay rockchip-RK3318-box-wlan-ap6330 in armbian-config (not a single overlay was selected here anymore) and selected the rk3318-box-led-conf1 option through rk3318-config (in this case, overlays rk3318-box-led-conf1 and rk3318-box-wlan-ap6334 are connected to boot). A certain Bluetooth block appeared in the text of the armbianmonitor -u output (see new output here), but apparently the driver is still not the same and hciconfig -a does not work (there is no command in the system). Any more ideas?

@Aleqssandro Farias which miniarch image are you using? Because I’m using miniarch patches so the dts should be the same.

Can you compare the device tree between your working system, and from the freshly installed 25.2.3/6.12.22 (write the img in a new microSD) View your device tree with: #(root) dtc -I fs -O dts /sys/firmware/devicetree/base (you need to find out which driver handles the audio, and search for that driver name in the working device tree) Also, check differences in armbianEnv.txt Also, check differences in ".config" in the /boot/ folder (specially anything related to audio) Also check the contents of "dmesg", searching for the audio driver name