Jump to content

Board Bring Up Station P1 rk3399, M1 rk3328


balbes150

Recommended Posts

14 часов назад, Chris4arm сказал:

I already posted these errors on 03/13/22 without answers.

 

What exactly does not work from the equipment on M1 ?

Link to comment
Share on other sites

6 hours ago, balbes150 said:

What exactly does not work from the equipment on M1 ?

 

apparently it works, but does it work as expected ?

Is it normal to have so many errors ? I have a TV box running Armbian (not officially supported) which has only 12 boot errors, none directly hardware related !

 

Link to comment
Share on other sites

Hi,

Poweroff and reboot don't work on my M1 (image Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img) :

Poweroff stops on "Apply kernel variables" then draws 400 mA !

Reboot ends on a black screen and stay there !

The power button does nothing.

 

Any hint ?

 

Chris

 

Link to comment
Share on other sites

On 5/9/2022 at 9:32 PM, Chris4arm said:

Hi,

Poweroff and reboot don't work on my M1 (image Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img) :

Poweroff stops on "Apply kernel variables" then draws 400 mA !

Reboot ends on a black screen and stay there !

The power button does nothing.

 

Any hint ?

 

Chris

 

 

 

Hi,

am I alone to (try to) use a Station M1 under Armbian ?

 

Chris

Link to comment
Share on other sites

12 часов назад, Chris4arm сказал:

am I alone to (try to) use a Station M1 under Armbian ?

If something is missing or is not working properly in the Armbian system, contact the hardware manufacturer to provide the necessary information or patches, or use the official versions from the manufacturer.

Link to comment
Share on other sites

13 hours ago, Chris4arm said:

 

 

Hi,

am I alone to (try to) use a Station M1 under Armbian ?

 

Chris

I use the M1 with Armbian Buster and the Default (Legacy) kernel, and it works mostly fine except for Bluetooth. I know that some people find it more exciting to use the Mainline kernel, but for me Default/Legacy works better

Link to comment
Share on other sites

I checked BT on M1 with the latest kernel version 5.18. Externally it looks like BT appears, but not completely and does not work. Perhaps the reason is the wrong firmware, but I do not know how to check it (I have never used BT and am not familiar with its operation).

 

root@station-m1:~# rfkill list
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
root@station-m1:~# hcitool dev
Devices:
root@station-m1:~# dmesg | grep tty
[    0.000000] Kernel command line: root=UUID=2ffc1c83-6aec-4615-9cdb-9d1d06520324 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian
[    0.002113] printk: console [tty0] enabled
[    1.944133] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 20, base_baud = 1500000) is a 16550A
[    1.944527] serial serial0: tty port ttyS2 registered
[    8.556574] systemd[1]: Created slice Slice /system/getty.
[    8.848242] systemd[1]: Created slice Slice /system/serial-getty.
[   12.618612] systemd[1]: Found device /dev/ttyS0.
root@station-m1:~# dmesg | grep Blu
[   12.294469] Bluetooth: Core ver 2.22
[   12.294495] Bluetooth: Starting self testing
[   12.317128] Bluetooth: ECDH test passed in 22095 usecs
[   12.324887] Bluetooth: SMP test passed in 7481 usecs
[   12.324993] Bluetooth: Finished self testing
[   12.325637] Bluetooth: HCI device and connection manager initialized
[   12.325657] Bluetooth: HCI socket layer initialized
[   12.325665] Bluetooth: L2CAP socket layer initialized
[   12.325699] Bluetooth: SCO socket layer initialized
[   12.511015] Bluetooth: HCI UART driver ver 2.3
[   12.511040] Bluetooth: HCI UART protocol H4 registered
[   12.511045] Bluetooth: HCI UART protocol BCSP registered
[   12.511202] Bluetooth: HCI UART protocol LL registered
[   12.511215] Bluetooth: HCI UART protocol ATH3K registered
[   12.511323] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   12.511817] Bluetooth: HCI UART protocol Intel registered
[   12.512291] Bluetooth: HCI UART protocol Broadcom registered
[   12.512373] Bluetooth: HCI UART protocol QCA registered
[   12.512387] Bluetooth: HCI UART protocol AG6XX registered
[   12.512436] Bluetooth: HCI UART protocol Marvell registered
[   13.377850] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723
[   13.382102] Bluetooth: hci0: RTL: rom_version status=0 version=2
[   13.382132] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_fw.bin
[   13.477842] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_config.bin
[   13.501454] Bluetooth: hci0: RTL: cfg_sz 47, total sz 30147
[   15.525293] Bluetooth: hci0: command 0xfc20 tx timeout
[   23.525310] Bluetooth: hci0: RTL: download fw command failed (-110)
[   42.372608] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   42.372629] Bluetooth: BNEP filters: protocol multicast
[   42.372646] Bluetooth: BNEP socket layer initialized

 

Link to comment
Share on other sites

Since we now have a dedicated place for this board (and basically every supported board) I'd strongly suggest to close this (and other) mega-thread and create individual threads per problem/question to increase user experience and readability. @balbes150

Link to comment
Share on other sites

On 5/20/2022 at 2:18 PM, Werner said:

Since we now have a dedicated place for this board (and basically every supported board) I'd strongly suggest to close this (and other) mega-thread and create individual threads per problem/question to increase user experience and readability. @balbes150

 

Hi Werner,

 

where is this dedicated place ?

 

Chris

Link to comment
Share on other sites

  • Werner locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines