20240531瑞芯微官方Toybrick TB-RK3588开发板在Debian11下的关机尝试

20240531瑞芯微官方Toybrick TB-RK3588开发板在Debian11下的关机尝试
2024/5/31 9:10

https://t.rock-chips.com/forum.php?mod=forumdisplay&fid=51
在Toybrick的论坛以关键词搜索：关机
可以找到抱怨这个的人很多！

（一）【失败】
https://t.rock-chips.com/forum.php?mod=viewthread&tid=597&highlight=%E5%85%B3%E6%9C%BA
除了拔电源还有其他关机的方式吗

长按PWRON有时候可以有时候不可以

Linux 系统可以使用命令  shutdown   来关机

toybrick@debian:~$ 
toybrick@debian:~$ 
toybrick@debian:~$ shutdown -h now
-bash: shutdown: command not found
toybrick@debian:~$ busybox shutdown -h now
shutdown: applet not found
toybrick@debian:~$ su
Password: 
root@debian:/home/toybrick# 
root@debian:/home/toybrick# shutdown -h now
bash: shutdown: command not found
root@debian:/home/toybrick# 
root@debian:/home/toybrick# reboot -p
bash: reboot: command not found
root@debian:/home/toybrick# su
root@debian:/home/toybrick# su toybrick
toybrick@debian:~$ 
toybrick@debian:~$ reboot -p
bash: reboot: command not found
toybrick@debian:~$ busybox reboot -p
reboot: invalid option -- 'p'
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) multi-call binary.

Usage: reboot [-d DELAY] [-n] [-f]

Reboot the system

    -d SEC    Delay interval
    -n    Do not sync
    -f    Force (don't go through init)
toybrick@debian:~$ 
toybrick@debian:~$ busybox reboot -d 1
reboot: Operation not permitted
toybrick@debian:~$ 
toybrick@debian:~$ sudo busybox reboot -d 1
toybrick@debian:~$ [  143.922115] systemd[1]: systemd 247.3-7+deb11u4 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[  143.923213] systemd[1]: Detected architecture arm64.
[  144.036302] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.

toybrick@debian:~$ 

https://t.rock-chips.com/forum.php?mod=viewthread&tid=744&highlight=%E5%85%B3%E6%9C%BA
遇到不能关机的情况

toybrick 不能关机  
shutdown now  终端不能关机   关机之后又会重新启动  

只能把电源线了

好像这个板子设计就是这样的，不然每次开机大家插完线还要按power开机，又会有人问为啥不能自动上电开机

https://t.rock-chips.com/forum.php?mod=viewthread&tid=1978&highlight=%E5%85%B3%E6%9C%BA
自己编译安卓源码固件后，关机重启问题

我的TB-RK3399PRODS开发板，用你们的固件烧写后关机和重启正常的。我自己在你们网站下载的源码编译成固件后烧写进开发板后在按关机按钮在安卓桌面显示“Power off”和“Restart”,能正常关机，但是选择“Power off”后开发板会关机，电源灯也不灭，一会后自动启动。不知道什么原因。

https://t.rock-chips.com/forum.php?mod=viewthread&tid=4568&highlight=%E5%85%B3%E6%9C%BA
TB-RK3588X buildroot系统，长按power键关机后自动重启

TB-RK3588X buildroot系统，长按power键，系统进入关机流程，但关机后，又会自动重启，以下是日志。请帮忙分析下原因，谢谢
key_event:
  code     : POWER
  source   : /dev/input/event0
  exec     : "/etc/power-key.sh press"

Requesting system poweroff
[   29.445013] rk860-regulator 2-0042: rk860..... reset
[   29.450497] rk860-regulator 2-0042: force rk860x_reset ok!
[   29.456017] rk860-regulator 0-0043: rk860..... reset
[   29.462076] rk860-regulator 0-0043: force rk860x_reset ok!
[   29.467579] rk860-regulator 0-0042: rk860..... reset
[   29.473635] rk860-regulator 0-0042: force rk860x_reset ok!
[   29.532932] mpp_av1dec av1d-master: shutdown device
[   29.537829] mpp_av1dec av1d-master: shutdown success
[   29.542872] [WLAN_RFKILL]: Enter rfkill_wlan_shutdown
[   29.547917] [WLAN_RFKILL]: rockchip_wifi_power: 0
[   29.552613] [WLAN_RFKILL]: rockchip_wifi_power: toggle = false
[   29.558439] wifi power off
[   29.665582] [WLAN_RFKILL]: wifi shut off power [GPIO105-0]
[   29.671071] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 0
[   29.676305] xhci-hcd xhci-hcd.7.auto: remove, state 4
[   29.681356] usb usb6: USB disconnect, device number 1
[   29.686866] xhci-hcd xhci-hcd.7.auto: USB bus 6 deregistered
[   29.692769] xhci-hcd xhci-hcd.7.auto: remove, state 4
[   29.697845] usb usb5: USB disconnect, device number 1
[   29.703409] xhci-hcd xhci-hcd.7.auto: USB bus 5 deregistered
[   29.709760] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown device
[   29.715556] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown success
[   29.721443] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown device
[   29.727193] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown success
[   29.733045] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown device
[   29.738791] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown success
[   29.744635] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown device
[   29.750379] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown success
[   29.756221] mpp-iep2 fdbb0000.iep: shutdown device
[   29.761002] mpp-iep2 fdbb0000.iep: shutdown success
[   29.765878] mpp_vepu2 fdbac000.jpege-core: shutdown device
[   29.771361] mpp_vepu2 fdbac000.jpege-core: shutdown success
[   29.776939] mpp_vepu2 fdba8000.jpege-core: shutdown device
[   29.782414] mpp_vepu2 fdba8000.jpege-core: shutdown success
[   29.787989] mpp_vepu2 fdba4000.jpege-core: shutdown device
[   29.793470] mpp_vepu2 fdba4000.jpege-core: shutdown success
[   29.799046] mpp_vepu2 fdba0000.jpege-core: shutdown device
[   29.804528] mpp_vepu2 fdba0000.jpege-core: shutdown success
[   29.810098] mpp_jpgdec fdb90000.jpegd: shutdown device
[   29.815233] mpp_jpgdec fdb90000.jpegd: shutdown success
[   29.820477] mpp_vdpu2 fdb50400.vdpu: shutdown device
[   29.825431] mpp_vdpu2 fdb50400.vdpu: shutdown success
[   29.830560] dwc3 fc000000.usb: Wakeup sysfs attributes not added
[   29.842467] reboot: Power down
DDR Version V1.07 20220412
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz

https://t.rock-chips.com/forum.php?mod=viewthread&tid=4570&highlight=%E5%85%B3%E6%9C%BA
TB-RK3588X debian系统，长按power键关机后自动重启

使用TB-RK3588X0-Release_V1.0.1_20230203固件包或者sdk制作的images，在开发板上都出现长按关机后系统自动重启的情况，请帮忙分析下原因。
以下是部分日志

[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Load/Save Screen B…htness of backlight:backlight.
[  OK  ] Removed slice system-systemd\x2dbacklight.slice.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Finished Power-Off.
[  OK  ] Reached target Power-Off.
[  338.020724] systemd-shutdown[1]: Syncing filesystems and block devices.
[  338.037838] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[  338.053411] systemd-journald[281]: Received SIGTERM from PID 1 (systemd-shutdow).
[  338.076645] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  338.094310] systemd-shutdown[1]: Unmounting file systems.
[  338.096609] [20222]: Remounting '/' read-only in with options '(null)'.
[  338.118306] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
[  338.138866] systemd-shutdown[1]: All filesystems unmounted.
[  338.138910] systemd-shutdown[1]: Deactivating swaps.
[  338.139037] systemd-shutdown[1]: All swaps deactivated.
[  338.139049] systemd-shutdown[1]: Detaching loop devices.
[  338.141422] systemd-shutdown[1]: All loop devices detached.
[  338.141449] systemd-shutdown[1]: Stopping MD devices.
[  338.141632] systemd-shutdown[1]: All MD devices stopped.
[  338.141645] systemd-shutdown[1]: Detaching DM devices.
[  338.141804] systemd-shutdown[1]: All DM devices detached.
[  338.141816] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[  338.160178] systemd-shutdown[1]: Syncing filesystems and block devices.
[  338.161406] systemd-shutdown[1]: Powering off.
[  338.339761] rk860-regulator 2-0042: rk860..... reset
[  338.340612] rk860-regulator 2-0042: force rk860x_reset ok!
[  338.341109] rk860-regulator 0-0043: rk860..... reset
[  338.342508] rk860-regulator 0-0043: force rk860x_reset ok!
[  338.343004] rk860-regulator 0-0042: rk860..... reset
[  338.344407] rk860-regulator 0-0042: force rk860x_reset ok!
[  338.390014] mpp_av1dec av1d-master: shutdown device
[  338.390442] mpp_av1dec av1d-master: shutdown success
[  338.390945] [WLAN_RFKILL]: Enter rfkill_wlan_shutdown
[  338.391393] [WLAN_RFKILL]: rockchip_wifi_power: 0
[  338.391808] [WLAN_RFKILL]: rockchip_wifi_power: toggle = false
[  338.392320] wifi power off
[  338.499248] [WLAN_RFKILL]: wifi shut off power [GPIO105-0]
[  338.499729] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 0
[  338.500469] rockchip-i2s-tdm fddf8000.i2s: failed to clear 1
[  338.501076] rockchip-i2s-tdm fddf8000.i2s: failed to clear on slave mode 1
[  338.501933] rockchip-i2s-tdm fddf8000.i2s: failed to clear 2
[  338.502499] xhci-hcd xhci-hcd.6.auto: remove, state 4
[  338.502951] usb usb6: USB disconnect, device number 1
[  338.503724] xhci-hcd xhci-hcd.6.auto: USB bus 6 deregistered
[  338.504398] xhci-hcd xhci-hcd.6.auto: remove, state 4
[  338.504847] usb usb5: USB disconnect, device number 1
[  338.505829] xhci-hcd xhci-hcd.6.auto: USB bus 5 deregistered
[  338.507264] rkisp_hw fdcc0000.rkisp: rkisp_hw_shutdown
[  338.507732] rkisp_hw fdcb0000.rkisp: rkisp_hw_shutdown
[  338.508212] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown device
[  338.508715] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown success
[  338.509261] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown device
[  338.509764] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown success
[  338.510298] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown device
[  338.510800] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown success
[  338.511338] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown device
[  338.511841] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown success
[  338.512377] mpp-iep2 fdbb0000.iep: shutdown device
[  338.512811] mpp-iep2 fdbb0000.iep: shutdown success
[  338.513257] mpp_vepu2 fdbac000.jpege-core: shutdown device
[  338.513738] mpp_vepu2 fdbac000.jpege-core: shutdown success
[  338.514245] mpp_vepu2 fdba8000.jpege-core: shutdown device
[  338.514726] mpp_vepu2 fdba8000.jpege-core: shutdown success
[  338.515233] mpp_vepu2 fdba4000.jpege-core: shutdown device
[  338.515714] mpp_vepu2 fdba4000.jpege-core: shutdown success
[  338.516228] mpp_vepu2 fdba0000.jpege-core: shutdown device
[  338.516709] mpp_vepu2 fdba0000.jpege-core: shutdown success
[  338.517217] mpp_jpgdec fdb90000.jpegd: shutdown device
[  338.517665] mpp_jpgdec fdb90000.jpegd: shutdown success
[  338.518172] mpp_vepu2 fdb50000.vepu: shutdown device
[  338.518609] mpp_vepu2 fdb50000.vepu: shutdown success
[  338.519058] mpp_vdpu2 fdb50400.vdpu: shutdown device
[  338.519501] mpp_vdpu2 fdb50400.vdpu: shutdown success
[  338.520084] dwc3 fc000000.usb: Wakeup sysfs attributes not added
[  338.527444] reboot: Power down
DDR V1.09 a930779e06 typ 22/11/21-17:50:56
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:30.7%, TX Vref:21.8%,20.8%
CH1 RX Vref:29.7%, TX Vref:21.8%,20.8%
CH2 RX Vref:32.7%, TX Vref:19.8%,20.8%
CH3 RX Vref:30.7%, TX Vref:19.8%,21.8%

toybrick 板子默认不支持关机功能，需要改硬件才能支持

请问是改哪里？是跳线或者更改电阻呢？方便提供一下sch的差异部分吗？

请问改动的地方多吗？麻烦帮忙提供需要修改的地方，我这边修改一下看看，谢谢。

【逮着你购买的淘宝商家的客服使劲问吧！】
修改的地方：感觉原理图部分的差异不是一般的大。
反正做驱动的我是没有看懂，淘宝客服让找自己公司的硬件去看看！

【对于这种设计缺陷，如果Toybrick的服务周到的话，对于购买的用户，全部免费赠送就是了！】
【对于这种设计缺陷，如果Toybrick的服务周到的话，对于购买开发板的用户，全部免费赠送所需要的修改转接板就是了！或者快递回去，免费返工！】