主要是在配置linux内核时,未使能看门狗,而在系统restart的时候,主要是利用取消喂狗,来触发看门狗超时,从而引发复位。
选择 → Device Drivers → Watchdog Timer Support → WatchDog Timer Driver Core 和 Allwinner SoCs watchdog support
离线
这样命令行执行 reboot 就可以重启了吗?
离线
这样命令行执行 reboot 就可以重启了吗?
是的
离线
谢谢,正需要,晚点就测试。
离线
谢谢,正需要,晚点就测试。
测试了没?
离线
感谢楼主,之前这个问题一直没解决。刚刚测试过,可以重启了!
离线
感谢楼主分享,另外根据经验常规做法不会是利用不喂狗重启的,因为看门狗重启是热启动,reboot一般设计成cold boot
离线
感谢楼主分享,另外根据经验常规做法不会是利用不喂狗重启的,因为看门狗重启是热启动,reboot一般设计成cold boot
命令reboot重启本来就是热启动。冷启动是断电的吧。或者有电源芯片控制的话,可以通过IO或者发送命令进行冷启动
离线
及时雨啊,等会试一下。
离线
果真可以软件重启了。谢谢楼主分享
离线
使用WG,已经搞定了
离线
我也碰到这个问题,开始一直以为是我的板问题,真多谢楼主
离线
感谢楼主,之前这个问题一直没解决。刚刚测试过,可以重启了!
离线
好高大上,对于刚刚接触的小白我而言好难,公司又催
离线
thanks a lot for the tip!
离线
感谢楼主,这个问题尝试了很多次一直没解决。这去测试一下
成功了!!!
allwinner F1C100S使用看门狗进行热启动的原因是: 没有PMU去支持冷启动
最近编辑记录 jerryzheng (2020-05-27 11:45:29)
离线
# reboot
# Stopping network: OK
Saving random seed... done.
Stopping logging: OK
umount: devtmpfs busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to 20.550344 reboot: Restarting system
21.549981 Reboot failed -- System halted
修改设备树: (DockerLicheepi下面)
/work/c600/2.kernel/linux-f1c100s-480272lcd-test/arch/arm/boot/dts/suniv.dtsi
wdt: watchdog@1c20ca0 {
compatible = "allwinner,sun6i-a31-wdt";
reg = <0x01c20ca0 0x20>;
};
修改为:
wdt: watchdog@1c20ca0 {
compatible = "allwinner,sun6i-a31-wdt";
reg = <0x01c20ca0 0x20>;
status = "okay";
};
修改之后编译内核dts:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j4 dtbs
上面不能解决问题!!!
==============================================================================
要是在配置linux内核时,未使能看门狗,而在系统restart的时候,主要是利用取消喂狗,来触发看门狗超时,从而引发复位。
选择 → Device Drivers → Watchdog Timer Support → WatchDog Timer Driver Core 和 Allwinner SoCs watchdog support
root@daeadcd74263:/work/c600/2.kernel/linux-f1c100s-480272lcd-test# make ARCH=arm menuconfig
---> Device Drivers
* Watchdog Timer Support --->
---> * WatchDog Timer Driver Core
...
---> <*> Allwinner SoCs watchdog support
保存退出再编译内核
root@daeadcd74263:/work/c600/2.kernel/linux-f1c100s-480272lcd-test# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j4
问题解决了:
#
# reboot
# Stopping network: OK
Saving random seed... done.
Stopping logging: OK
umount: devtmpfs busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to[ 21.795427] reboot: Restarting system
U-Boot SPL 2018.01 (Jul 08 2020 - 03:26:27)
DRAM: 32 MiB
Trying to boot from MMC1
Card did not respond to voltage select!
mmc_init: -95, time 22
spl: mmc init failed with error: -95
Trying to boot from sunxi SPI
U-Boot 2018.01 (Jul 08 2020 - 03:26:27 +0000) Allwinner Technology
CPU: Allwinner F Series (SUNIV)
Model: Lichee Pi Nano
DRAM: 32 MiB
MMC: SUNXI SD/MMC: 0
SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@1c25000
Out: serial@1c25000
Err: serial@1c25000
Net: No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot: 0
SF: Detected w25q128bv with page size 256 Bytes, erase size 4 KiB, total 16 MiB
device 0 offset 0x100000, size 0x4000
SF: 16384 bytes @ 0x100000 Read: OK
device 0 offset 0x110000, size 0x400000
SF: 4194304 bytes @ 0x110000 Read: OK
## Flattened Device Tree blob at 80c00000
Booting using the fdt blob at 0x80c00000
Loading Device Tree to 816fa000, end 816ff144 ... OK
Starting kernel ...
离线