paradigman

some added info, detail from the armbian monitor output: 527 [ 9.816528] brcmfmac: F1 signature read @0x18000000=0x16034334 529 [ 9.837294] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 530 [ 9.839398] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2 531 [ 9.843056] usbcore: registered new interface driver brcmfmac 533 [ 10.097755] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 534 [ 10.098076] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available 535 [ 10.099292] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 1437 [ 9.119553] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch 1444 [ 9.553660] brcmfmac: F1 signature read @0x18000000=0x16034334 1445 [ 9.573816] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 1446 [ 9.574117] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2 1447 [ 9.578548] usbcore: registered new interface driver brcmfmac 1449 [ 9.787851] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 1450 [ 9.788132] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available 1451 [ 9.788911] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 1455 [ 9.881905] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM ... 3162 [ 10.714799] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 4014 [ 10.135514] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 6565 [ 9.597587] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM ... 7212 [ 8.971401] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 7215 [ 9.194035] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 7217 [ 9.195003] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 7222 [ 9.597587] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 7223 [ 9.597636] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852 what can i do to be able to connect to Wi-Fi?

I had a problem with this wireless chip. Is this familiar to anyone? In one of the system messages I saw this as BCM 4334B1 / 6334. It can scan networks with the minimal image but cannot connect. Is there an overlay?

Thank you for your answer. I don't understand how can be bigger the backup than the another disk, because these three box is from one serie. I did try use the initramfs to repartition, but lokks like it not familiar anything command except the fsck.

I use @jock's great job (Armbian_22.02.0-trunk_Rk3318-box_bullseye_edge_5.15.16_minimal) in my H96 Max box. I would like to clone this content of box to another two H96 boxes. I do the backup with multitool and then use the restore function on the other with the same tool. Unfortunately, the result is not what I expect, it doesn't start at first: What to do or write to get started?

I tried to activate the i2c-7 overlay (which I think is actually I2c-1), but I couldn't create access to this bus because I found this in dmesg: [ 1.804400] rockchip-pinctrl pinctrl: pin gpio2-4 already requested by ff1b0000.pwm; cannot claim for ff160000.i2c [ 1.804429] rockchip-pinctrl pinctrl: pin-68 (ff160000.i2c) status -22 [ 1.804447] rockchip-pinctrl pinctrl: could not request pin 68 (gpio2-4) from group i2c1-xfer on device rockchip-pinctrl What could be the cause of the problem?

Using openvfd and the recommended settings, the display on my box works for me, but I can always only see the exact time. How can I display my own content using openvfd?

Of course. I wrote a little script for it that shortens the process a bit. It is important to know that I am not working as a root user within armbian. The necessary steps: copy openvfd-fd6551.dts to /home/<username> copy install_kernel_debs.sh to /home/<username> copy OpenVFDService file to /usr/sbin, AND set permission to 777 ! copy openvfd.service file to /lib/systemd/system sudo armbian-add-overlay openvfd-fd6551.dts sudo /bin/bash install_kernel_debs.sh After reboot: cd linux_openvfd/driver edit MAKE -> KERNELDIR = /lib/modules/$(shell uname -r)/build sudo make -j4 sudo make modules_install sudo modprobe openvfd sudo usermod -a -G i2c <username> Start the Service: sudo systemctl enable openvfd sudo systemctl start openvfd openvfd-fd6551.dts openvfd.service OpenVFDService install_kernel_debs.sh

I have a working openvfd configuration, the box displays the exact time after boot. Now the question is, is it possible to display "boot" during boot, as shown during boot of the factory Android firmware? Do I think this can be set in the openvfd overlay? That would be the goal:

@kruzer I think we have a very similar board, yet my LCD screen is still dark. I will list all the relevant sections here, would you see if you see any relevant differences from what you are experiencing? Many thanks. Edit: The problem was solved. There was an authorization problem accessing the service file and I discovered this using the systemctl status openvfd command.

Hi, I'm so glad you're dealing with this. I didn't put the vfd.conf file anywhere because if it was, it ignored every line of it. Instead, I define the configuration in DTS like this:

Thanks for checking the log. In fact, you confirmed my guess that there was a fault around the I2C bus. I find it strange that if I activate I2C-7 or I2C-8 (or even both at the same time) in the armbian-config, no new bus is detected in the system. In this case, if I run: ls -l /dev/i2*, it still shows the same I2C-4 that was previously available due to HDMI.

I understand it's half-finished, but as long as the display is blank, it's suitable for testing.

@lucky62: thanks for your descriptons. Unfortunately for me, not a single digit is still lit, even though I did everything as described. I can't run the OpenVFDService compile, so I used Jock's pre-compiled version. My configuration is in dts. don't know if it's important, but here's a relevant detail about dmesg's output. Please look at it, does it look good?

Thanks for your description, imerging with Jock's previous description like this and now I've been able to compile the driver so that it loads correctly. I do not use the config file because the jock dts overlay in principle contains the configurations required for FD6551. Ok, how to proceed after the module loads? What will show the current time on the display?

Hello, could you share a few details on how you were able to display the clock? If I could get here, maybe I could help you with your problem. This is because after compiling the driver, when I load the .ko module, it shows me: Message from syslogd @ rk3318-box at Jan 21 21:48:32 ... kernel: [591.624102] Internal error: Oops: 96000004 [# 1] PREEMPT SMP Message from syslogd @ rk3318-box at Jan 21 21:48:32 ... kernel: [591.968480] Code: 32000000 39016420 f9401a60 f9404be1 (f9406022) Segmentation error I saw that you had this error before, but then you didn't write what fixed it.