Some sort of logs would be great, otherwise very hard to track down

I did not look well enough and also at a local PDF copy of the wiki which I see is more than 2 years old. Same text is there, but not in red at that time. I think I noticed it at the I was soldering the wire, but I clearly forgot the typing the message i this topic. Anyway, I have no good idea how to solve your remote power issue. I use a MOSFET that has low Vgs on (works directly on 3.3V , but is not for common GND. Else PoE managed switch where I can toggle power when fatal lockup or so. Or else instruct someone to pull the plug, wait 10 seconds, stick it back in again. If you use CoW filesystems, it is no problem to do this.

thanks @eselarm. I think I may not have made myself clear. I want to be able to "Power On" i.e. boot the board using a remote switch and not Power (provide 5v) to the board via the GPIO pins. The Banana Pi docs here (half way down page to GPIO section) actually states that you cannot use the GPIO pins for injecting power only drawing power for ancillary boards etc. When testing the board and setting it up I accidentally touch the SATA case against the GPIO pins and the board started, I'm not sure what pin it was and if it might cause damage long term starting the board this way but I need to know if its possible and which pin(s) i need to short to ground? As regards SATA drive I'm fixing the 2.5" drive to the lid of the box and using one of these SATA right angle adapters and a short100mm very flexible SATA cable to connect to the SATA port on the board and the adapter. when its built I will upload a photo. In the meantime I need to be able to reboot the board externally when the power has been disrupted. I could unsolder the existing switch but the solder pads look tiny.

Hi all, I’m trying to enable the front VFD/LED display on an RK3318 TV box. OS: Armbian 23.11.1 Jammy, kernel 6.18.10-current-rockchip64 DTB: rk3318-box.dtb (fdtfile=rockchip/rk3318-box.dtb) In DTB I found: fd628_dev { compatible = "fd628_dev"; fd628_gpio_clk = <0x7a 0x10 0x00>; // bank2, offset16 fd628_gpio_dat = <0x7a 0x0f 0x00>; // bank2, offset15 }; I built linux_openvfd and added an openvfd node in DTB: openvfd { compatible = "open,vfd"; dev_name = "openvfd"; status = "okay"; }; Module loads, /dev/openvfd appears with: vfd_gpio_clk=2,16,0 vfd_gpio_dat=2,15,0 vfd_gpio_stb=2,19,0 vfd_display_type=0,0,0,0 vfd_chars=0,1,2,3,4,5,6 vfd_dot_bits=0,1,2,3,4,5,6,0 dmesg shows: OpenVFD: Select FD628 controller OpenVFD: SPI 3-wire interface initialized (LSB mode) /sys/class/leds/openvfd exists, but no indicators light up. Tried multiple display_type values and STB pins (bank2 offsets 18–22 + other banks) — still no output. Question: Does anyone know the correct GPIO pins (CLK/DAT/STB) for rk3318-box VFD, or a working driver/service for FD628/FD650 on this board? Any confirmed configs for RK3318 boxes would be greatly appreciated. I’ve been working on this for ~2 weeks and tried multiple configs/drivers without success. Thanks!

One interesting thing I discovered today is that you can actually boot from a flash drive, if you don't have a SD Card! In my case, I would have to buy a SD Card and had a flash drive laying around so I thought I might just give it a try, worked on an Arm Cortex-A53 CPU. I used u-boot-s905x-912 for .ext and meson-gxl-s905x-p212.dtb.