我不知道如何帮助你使用那个微观。对不起。
典型的WIND日志包含:
+ WIND:1:上电:XXXXXX-XXXXXXX-SPWF04S
+风:13:版权所有(c)2012-2017 STMicroelectronics,Inc。保留所有权利:SPWF04Sx
+ WIND:0:控制台活动+ WIND:32:WiFi硬件启动
由于你屏蔽了0到31个WIND,你应该只收到WIND:32
复位后,闪烁的LED开始闪烁(然后停止),或从不开始闪烁?在第一种情况下,控制台LED应该打开(在WIND:0之前,即使被屏蔽)和关闭(在WIND:0时);在第二种情况下,控制台LED永远不会变高。在第一种情况下,模块将因看门狗而重启;在第二种情况下,模块永远不会启动在这两种情况下,模块都会停止,因为SPI主控制器在nHostIRQ中断后没有给出时钟,或者SPI主控制器提供的时钟少于模块SPI头所需的时钟。
注意:如果需要执行恢复出厂设置(并恢复wind_off_low值),可以通过HW进行。启动时将GPIO0置为高电平。
以上来自于谷歌翻译
以下为原文
I don't know how to help you using that micro. I'm sorry.
Typical WINDs log contains:
+WIND:1:Poweron:xxxxxx-xxxxxxx-SPWF04S
+WIND:13:Copyright (c) 2012-2017 STMicroelectronics, Inc. All rights Reserved:SPWF04Sx
+WIND:0:Console active+WIND:32:WiFi Hardware Started
Since you masked 0 to 31 WINDs, you should receive the only WIND:32
After reset, blinking LED starts blinking (and then it stops), or never starts blinking? In the first case, console LED should be on (before WIND:0, even if masked) and than off (at WIND:0 time); in the second case, console LED never goes high. In the first case module will reboot because of watchdog; in the second case module never starts. In both cases, module stops because SPI master is not giving the clock after an nHostIRQ interrupt, or SPI master gives less clocks than required by module's SPI header.
Note: if you need to perform a factory reset (and restore wind_off_low value), you can do via HW. Put GPIO0 high at startup.