Search the Community

Test version of the Armbian+EDK2 system (UEFI\grub) is available. The system startup control is performed as on a regular PC - through the menu on the monitor screen, therefore, to fully use all the features of selective startup, you need to have a connected monitor and keyboard To use this option. Download the EDK2 image. https://users.armbian.com/balbes150/edk2/ https://disk.yandex.ru/d/kK6KIqHShRHLyw Unpack and burn to SD card. Download the Armbian image (kernel 6.1.0-rc7), For Station M2 https://disk.yandex.ru/d/C4Ql9v0BvhKPjQ For Station P2 https://disk.yandex.ru/d/5XuGz9WgF7FGCg unpack and burn it to a USB drive (8-16GB flash drives are recommended, I haven't checked other options). Connect the SD card and USB drive. Turn on the power. If the system does not start immediately, go to settings and select the device to start. On the EDK2 boot screen, select "Maintaining Manager boot" in the menu item and configure the device used for startup in it (change "none" to "UEFI ...."). Select Reset. If you did everything correctly, after restarting EDK2, you will receive a GRUB menu with a choice of system\kernel. If you do not select anything, the default system will be started in 5 seconds, and in 10-20 seconds (depending on the type of USB flash drive) there will be a standard Armbian customizer for the first launch. If desired, you can place the entire system on an SD card, but additional steps will be required at startup. At startup, the kernel switches the UART console to the correct value for RK (1500000) and you can monitor the kernel startup process and control the system through the UART console. That is, the parameters 115200 can only be useful for viewing the primary output from EDK2 itself, but this is only necessary for developers, for ordinary users, kernel output and system management are more useful, so I recommend using the standard value for Rockchip of 150000. https://github.com/150balbes/edk2_uefi

Hi guys. I've been working with the 4.19 kernel before on M2. I upgraded to the kernel version 5.18 today. I found that I can't find the registered udc device anymore. This is auto-registered on the 4.19 kernel and you can find it under /sys/class/udc. root@station-m2:/boot# ls /sys/class/udc fcc00000.dwc3 I would like to ask how to enable the udc device on the 5.18 kernel. Thank you.

I get no audio devices in Gnome/Jammy userland on an Armbian 5.18 kernel. From the console, alsamixer has controls for Analog RK809, but no Playback Mux for the speaker (mini jack) and changing the card Default to HDMI reports "This Sound Device Does Not Have Any Controls". The Gnome/Ubuntu audio applet has only a dummy device. Thanks!

Bluetooth device does not appear on my armbian (kernel is 5.17.5-media, tried on edge-media and current-media as well). # hciconfig version Can't get device info: No such device # bluetoothctl Agent registered [bluetooth]# devices No default controller available HCI socket does not seem to be created. Got this in dmesg: [ 11.990128] Bluetooth: HCI device and connection manager initialized [ 11.990145] Bluetooth: HCI socket layer initialized [ 11.990164] Bluetooth: L2CAP socket layer initialized [ 11.990188] Bluetooth: SCO socket layer initialized [ 12.081220] Bluetooth: HCI UART driver ver 2.3 [ 12.081245] Bluetooth: HCI UART protocol H4 registered [ 12.081250] Bluetooth: HCI UART protocol BCSP registered [ 12.081352] Bluetooth: HCI UART protocol LL registered [ 12.081358] Bluetooth: HCI UART protocol ATH3K registered [ 12.081397] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 12.081760] Bluetooth: HCI UART protocol Intel registered [ 12.082139] Bluetooth: HCI UART protocol Broadcom registered [ 12.082205] Bluetooth: HCI UART protocol QCA registered [ 12.082211] Bluetooth: HCI UART protocol AG6XX registered [ 12.082335] Bluetooth: HCI UART protocol Marvell registered [ 12.082530] rockchip-pinctrl pinctrl: pin gpio0-17 already requested by fdd50000.serial; cannot claim for serial0-0 [ 12.082544] rockchip-pinctrl pinctrl: pin-17 (serial0-0) status -22 [ 12.082550] rockchip-pinctrl pinctrl: could not request pin 17 (gpio0-17) from group bt-enable-h on device rockchip-pinctrl [ 12.082557] hci_uart_bcm serial0-0: Error applying setting, reverse things back [ 12.297655] cfg80211: failed to load regulatory.db [ 12.308441] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.firefly,rk3566-roc-pc.txt failed with error -2 [ 12.308466] brcmfmac mmc2:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43455-sdio.firefly,rk3566-roc-pc.txt [ 12.549006] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 12.589256] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04 Looks like wifi firmware loaded okay (not sure if the chip uses same blob for bluetooth and wifi, probably not), but there's some conflict with fdd50000.serial (which is uart0, another strange thing). To me it looks like a bug in .dts, but could not find it so far. Tried removing uart0 from .dtd. HCI device appears after that, but HCI socket is down and not responding. (Maybe I need to trigger gpio pin to enable bluetooth, but why doesn't it happen automatically?) Any ideas?

Hey guys, looks like there's no support for board serial number in latest images for Station M2. Serial number on rk356x is coming from otp memory, so: 1) there are no bindings for `otp` and `cpuinfo` devices in .dts, like here 2) there are no kernel driver to extract data from otp memory, like here I'm ready to contribute, but not sure what's the future plan for those.