使用SPWF04S SPI接口无法让模块响应我发送的任何命令

我正在尝试使用SPWF04S模块的SPI接口，但成功非常有限
通过在复位脉冲结束时将中断引脚拉高，我可以通过启用SPI接口将模块从RESET中取出。该模块发送一些完全有意义的WIND消息。我得到'控制台处于活动状态''wifi硬件启动'等等，最终它会安静下来每隔几秒进行一次扫描（我得到'扫描有效'然后反复'扫描完成'）这一切都很好。
我无法让模块响应我发送的任何命令。让我们说我想发送最简单的命令（AT）来确定控制台是否还活着......这是我到目前为止所尝试的
1- SET CS low ...发送0x02,0x00,0x02,0x01,0x00 ...将CS置高......等待INT变低...读取响应
2- SET CS低...发送0x02,0x00,0x02,0x01,0x00 ...保持CS低电平...等待INT变低...读取响应
3-
SET CS low ...发送0x02,0x00,0x02,0x01,0x00 ...继续计时
......等待INT变低......阅读回复
4-
SET CS low ...发送0x02,0x00,0x02,0x01,0x00 ...继续计时
...等待同步（0x02）...读取响应
“长度”字节按照TCP堆栈手册（高字节优先）中的示例进行排序，但我也尝试了以上所有这两个字节的反转（低字节优先，接收事务的字节顺序）但无济于事。
在这两种情况下，如果INT最终变低，那不是我期望的那种响应，只是另一个WIND（通常是下一个'扫描开始'或'扫描完成'）
我已经阅读了手册，关于SPI的非常简短的部分没有多大帮助（看起来我应该像上面的1-一样（因为它显示CS在事务结束时变高）但是它的描述是多次接收不是我所看到的（我看到INT在每次交易后都变高，而不是像手册中那样保持低位）并且SPI交易的破碎英文描述也不匹配。我不知道如何我应该相信这些图表。所有的代码示例都有与SPI相关的部分，但仔细观察后，它们都使用了UART。
有人可以通过准确的传输描述或时序图或实际使用SPI接口的示例代码向我指出正确的方向。在过去的3天里，我一直在与此作斗争，所以任何帮助都将不胜感激。
非常感谢
伊恩



以下为原文




I am attempting to use the SPI interface of the SPWF04S module but with very limited success
I can get the module out of RESET with the SPI interface enabled by simply pulling the interrupt pin high as the reset pulse ends. The module sends some WIND messages that all make perfect sense. I get 'console active' 'wifi hardware started' etc etc and eventually it settles down to doing scans every few seconds ( I get 'scan active' followed by 'scan complete' repeatedly) That's all good.
I can't get the module to respond to any commands I send it. Lets say I want to send the simplest command (AT) just to determine if the console is alive... Here is what I've tried so far
1- SET CS low ... Send 0x02, 0x00, 0x02, 0x01, 0x00 ... Set CS high ... Wait for INT to go low ... Read response
2- SET CS low ... Send 0x02, 0x00, 0x02, 0x01, 0x00 ... Leave CS low ... Wait for INT to go low ... Read response
3-
SET CS low ... Send 0x02, 0x00, 0x02, 0x01, 0x00 ... continue clocking
... Wait for INT to go low ... Read response

4-
SET CS low ... Send 0x02, 0x00, 0x02, 0x01, 0x00 ... continue clocking
... Wait for sync (0x02) ... Read response

The 'length' bytes are ordered as in the examples in the TCP stack manual (high byte first) but I have also tried all of the above with the two bytes reversed (low byte first, as is the byte order of the receive transactions) but to no avail.
In both cases, if INT does eventually go low, it is not the kind of response I am expecting, just another WIND (usually the next 'scan started' or 'scan complete')
I've been through the manual, the very short section on SPI isn't much help (looks like I should be doing as 1- above (since it shows CS going high at the end of the transaction) but then it's description of the multiple receive isn't what I'm seeing (I see INT go high after every transaction, not staying low as in the manual) and the broken-english description of the SPI transactions don't match either. I'm not sure how far I should trust these diagrams. All of the code examples have sections relating to SPI but on closer inspection, they all use the UART.
Can someone point me in the right direction here with either an accurate description of the transfers or timing diagrams or some example code that actually uses the SPI interface. I've been battling with this for the last 3 days so any help would be greatly appreciated.
Many thanks
Ian