SPWF01：运行示例应用程序遇到麻烦

嗨，
我做了进一步的调查，看来我的示例应用程序在wifi模块初始化时陷入了无限循环：
在wifi_module.c中：
 while（IO_status_flag.WiFi_WIND_State.WiFiHWStarted！= WIFI_TRUE）
 
 {
 __NOP（）; //没事做
 我找到了这些线程
https://community.st.com/0D50X00009XkgFFSAZ
 和https://community.st.com/thread/40308-problem-with-the-stm32cubeexpansion-wifi-demo-with-the-x-cube-wifi1?commentID=155925&sharpcomment
 描述同样的问题。所以，我看了wifi模块重置后的ring_buffer内容，我得到了一些缺少字符的WIND字符串：
即：
r  n + WND：1：peron ......
在我提到的第二个帖子中，它说缺少字符意味着'关于uart管理的问题'（
见Gerardo Gallucci发表于2017年5月2日上午10:20）
但目前还不清楚如何解决这个问题。我试图切换Timer和Uart IRQ优先级但它没有效果。
你能帮我解决一下吗？
问候
西尔万巴塞特
PS：我的第一个端口包含一个错误：我的模块上的LED 4（橙色）亮起
 
 注意：原始帖子包含大量线程对话，只能迁移到第9级



以下为原文




Hi,
I did further investigations and it appears that my example applications stucks in infinite loop at wifi module initialization :
In wifi_module.c:
  while(IO_status_flag.WiFi_WIND_State.WiFiHWStarted != WIFI_TRUE)

    {
       __NOP(); //nothing to do
    }I found these threads
https://community.st.com/0D50X00009XkgFFSAZ
and https://community.st.com/thread/40308-problem-with-the-stm32cubeexpansion-wifi-demo-with-the-x-cube-wifi1?commentID=155925&sharpcomment
describing the same problem.So, I looked at ring_buffer content after wifi module reset, and I got WIND strings with some missing character :
ie:
rn+WND:1:peron ...
In the second thread I mention, it said that missing characters means 'issue on uart management' (
see Gerardo Gallucci post on May 2, 2017 10:20 AM)
But it remains unclear how to fix that problem. I tried to switch Timer and Uart IRQ priority but it has no effect.
Can you help me to resolve this.
Regards
Sylvain Basset
PS: my first port contains a mistake : LED 4 (orange) in ON on my module

Note: the original post contained a large number of threaded conversations and was only able to be migrated to the 9th level

我发现问题来自sysctick和UART中断之间的副作用。
Systick中断调用Process_WiFi（）函数（wifi_module.c）。在开始时，在pop_buffer_queue（）调用期间禁用中断（wifi_module.c，第1093行）。因此在此期间禁用UART接收。
与UART IRQ频率相比，这个关键部分似乎持续时间过长。我发现用于初始化弹出缓冲区的memset（）操作花费了太多时间。
所以，我愚蠢地减少了缓冲区初始化的大小（ring_buffer.c，第188行）：
 memset（pop_buffer，0x00，）; - ＆GT; to：memset（pop_buffer，0x00，）;
它的工作原理！我现在能够连接到我的AP并打开套接字。
请注意，这是一个肮脏的解决方法。我刚刚测试了与AP的连接。我不知道启用“数据块”时会发生什么。
我看到这个论坛不是很活跃，但我希望这会有助于谷歌的人。



以下为原文




I found that the problem comes from side effect between sysctick and UART interrupt.
The Systick interrupt calls Process_WiFi() function (wifi_module.c). At begining, interruptions are disabled during  pop_buffer_queue() call (wifi_module.c, line 1093). So UART reception is disabled during this time.
It seems that this critical section last too long compared to UART IRQ frequency. I found that memset() operation, used to initialize the poping buffer, takes too much time.
So, I silly reduced the size of buffer initialization (ring_buffer.c, line 188) :
      memset(pop_buffer, 0x00 , ); --> to : memset(pop_buffer, 0x00 , );
And it works !!!  I'm now able to connect to my AP and open socket.
Just note that this is a dirty workaround. I just tested a connection to AP . I dont know what happens when 'data chunk' is enabled.
I see this forum is not very active but i hope this will help someone who google it.