[问答]

协调和ATWINC1500

问答对人有帮助，内容完整，我也想知道答案 0 我买了一个MCHP好奇PICMZ EF开发板，它包含一个100引脚PIC32 MZ2048 EFM100芯片，一个LAN820以太网连接，一个MikROBUS板与WiC1510 WiFi芯片（加上其他连接器，LED和开关）。我已经能够执行我的BK中的所有例子来理解好奇心开发工具包和以前的PIC32 MZ启动套件是否有任何显著差异。除了在144引脚和100引脚部分之间改变了引脚的位置，我没有问题。接下来，我想把WiFi的特性添加到现有的应用程序中。这就是我开始绊倒的地方。首先，我去了和声“帮助”文件，了解Wi1500芯片是如何工作的。大约有50页重复的胡言乱语。然后我去了WiC1500数据表（125页），解释了芯片是如何工作的。我注意到大部分的和声帮助只是从数据表中复制粘贴的。当然，数据表并没有告诉我们如何在协调环境中使用WiC1500。接下来，我去了DEMOS（在V2.06）。所有的WiFi演示基本上都是相同的演示。演示需要FreeRTOS，并且有许多选项，但是每一个只能通过重新配置和重新编译基本演示来一次运行。WiC1500文档描述了2种模式——原生模式和宿主模式。本机模式使用机载TCP/IP堆栈来执行基本的TCP V4和TLS1.2功能（基本上是伯克利套接字）。主机模式绕过板上的TCP/IP固件，并将所有的东西发送到主机（即和声栈）。我还审查了和声和无线嵌入式论坛的任何相关信息。在这一点上，我必须回到源代码检查和文件比较，试图解开演示在协调环境中所做的事情。到目前为止，这里列出了从和声实现（文档和演示）中缺少的东西的列表和需要添加的IMHO：如何使用PIN管理器配置WiC1500（注释：Goovi-DeV板的MHC BSP包没有关于PIN定义的信息）。如何使用Win C1500芯片在和谐超环中——演示只显示FrRetos设计。IMHO，这属于第三方库选项卡，而不是在驱动器中。如何使用WiC1500在本机模式下如何使用Win C1500在主机模式下实现以太网（有线）和WiFi（无线）TCP/IP接口，这是我论坛的问题：有没有人在那里实现TH？Win C1500驱动程序和一个仅使用和声超循环的应用程序？如果没有，我会尝试拆开这串绳子。如果我成功了，有人会在乎吗？：）以上来自于百度翻译以下为原文 I bought a MCHP Curiosity PICMZ EF development board which contains a 100-pin PIC32MZ2048EFM100 chip, a LAN8720 Ethernet connection, a mikroBUS board with a WINC1510 WiFi chip (plus other connectors, LEDs and switches). I have been able to execute all of the examples in my b*k to understand if there were any significant differences between the Curiosity development kit and the previous PIC32MZ Starter Kit. Except for the changed pin locations between the 144-pin and 100-pin parts, I had no problems. Next, I wanted to add the wifi feature of the board to an existing application. This is where I started stumbling. First (naively) I went to the HARMony "Help" files to understand how the WIN1500 chip works. There are about 50 pages of repetitive blather. I then went to the WINC1500 datasheet (~125 pages) which explained how the chip works. I noticed that most of the Harmony help is just copied and pasted from the datasheet. Of course, the datasheet tells nothing about how to use the WINC1500 in the Harmony environment. Next, I went to the demos (in v2.06). All of the wifi demos are essentially the same demo. The demo requires FreeRTOS and has numerous options, but each one can only be run one at a time by reconfiguring and recompiling the basic demo. The WINC1500 documentation describes 2 modes -- a native mode and a host mode. The native mode uses the on-board TCP/IP stack to do basic TCP v4 and TLS1.2 functions (essentially Berkeley sockets). The host mode bypasses the on-board TCP/IP firmware and sends everything to the host (i.e. Harmony stack). I also reviewed the Harmony and wireless embedded forums for any relevant information. At this point I had to revert to source code inspections and file compares to try to unravel what the demos were doing in the Harmony environment. So far, here is a list of things that are missing from the Harmony implementation (documentation and demos) and IMHO need to be added: how to use the pin manager to configure the WINC1500 (note: the MHC bsp package for the Curiosity dev board has no information on the pin definitions). how to use the WINC1500 chip in the Harmony superloop -- the demos only show a FreeRTOS design. IMHO, this belongs in the Third-party Library tab, not in the drivers. how to use the WINC1500 in native mode how to use the WINC1500 in host mode how to implement both an Ethernet (wired) and a wifi (wireless) TCP/IP interface So, here are my questions for the forum: Has anyone out there implemented the WINC1500 drivers and an application using the Harmony superloop only? If not, I will try to unravel this ball of string. If I am successful, does anyone even care? :) 0
2018-8-23 15:29:58　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × qun333 该类别下有 57 个回答。邀请回答技术发广告该类别下有 56 个回答。邀请回答 caoguiqun 该类别下有 56 个回答。邀请回答 psw30 该类别下有 44 个回答。邀请回答伊丹姿子该类别下有 41 个回答。邀请回答 uwufwjrw 该类别下有 39 个回答。邀请回答 hetao1111 该类别下有 38 个回答。邀请回答 lc123617 该类别下有 35 个回答。邀请回答欧阳大大该类别下有 32 个回答。邀请回答作死不止该类别下有 31 个回答。邀请回答 asd010 该类别下有 31 个回答。邀请回答 wy8719 该类别下有 29 个回答。邀请回答 60user92 该类别下有 29 个回答。邀请回答 haikitty 该类别下有 28 个回答。邀请回答 ju978779 该类别下有 28 个回答。邀请回答嘻嘻爱哈哈该类别下有 28 个回答。邀请回答 xiuzhen122 该类别下有 27 个回答。邀请回答 pol666 该类别下有 27 个回答。邀请回答 ueywyrsdfs 该类别下有 26 个回答。邀请回答 lhly23 该类别下有 25 个回答。邀请回答举报叶亮相关推荐 • 怎么使用ATWINC1500进行定制设计 2386 • 怎么向ATWINC1500发送推送通知？ 1287 • ATWINC1500 GPIO有用吗？ 1188 • WiFi模块比较：ATSAMW25，ATWILC1000，ATWILC3000，ATWINC1500，ATWINC3400和MRF 3817 • ATWINC1500固件怎么升级 3178 • 选择哪种WiFi模块与PIC32配合使用？（ATWINC1500，PIC32WK，MRF24WG0M） 2010 • WIFi模块：ATWINC1500还是旧款MRF24WB0MA/MRF24WN0MB？ 1786 • PIC32MZ+ATWINC1500：经常发生Wi-Fi断开事件 1907 • 是否有必要更新ATWINC1500固件以使用AT命令？ 2992 • 如何通过电路板的ATWINC1500-MR210PB模块或者miniUSB采集数据？ 1079 2个回答

答案对人有帮助，有参考价值 0 谢谢你的评论。我在MLA中使用了旧的堆栈，只有有线NIC。我喜欢…您可以简单地在CONFIG.H中取消您想要的特性，它们将同时运行。似乎新规定的和谐要求听起来很稳健，但如何配置它需要通过渗透或其他东西吸收。PIC32是唯一的处理器选择，16位DSPIC已被孤立。同样，听起来像和声仍然是一个卡片的房子。因为我有一个正式的期限来实现一个使用最小特征的WiC1500系统，所以我选择了在原生模式下运行无OS的MLA路由。我希望最终使用原始堆栈的其他特性（因为本机堆栈是轻量级的），但在这一点上对我来说太冒险了。你的任何发现都会引起我的兴趣。谢谢。以上来自于百度翻译以下为原文 Thanks for the review. I've used the older stack under MLA with wired NIC only. I liked it... you could simply uncomment the features you wanted in the config .h and they would all run simultaneously. Seems like the newly mandated Harmony requirement sounds robust, but how to config it needs to be absorbed via osmosis or something. PIC32 is the only processor selection and 16-bit dsPIC's have been orphaned. Also, sounds like Harmony is still a house of cards. Since I have an official deadline to implement a WINC1500 system using minimal features, I opt'ed to go the OS-less MLA route in native mode. I'd like to eventually use other features of the original stack (since the native stack is light), but too risky for me at this point. Any findings you post will definitely interest me. Thanks.

2018-8-23 15:38:44 评论举报陈桂兰

答案对人有帮助，有参考价值 0 在使用PIC32 MZ的哑模式中使用WiC1500基本上没有意义。应该得到什么？（我不确定你指的是“原生vs主机”），我猜想和谐不是做超循环的核心原因可能是因为它们只将ASF框架转换为和声，还没有真正编写新代码。我个人认为将驱动程序转换成超循环是一种挑战。你必须重写HON/ASF来支持它。一个开始点的外观是找到所有的XTaskCube并将它们转换成超循环或ISR，同时确保每个循环不会阻塞另一个循环。我沿路学习的东西…1。WiLC1000和WiC1500都与1000驱动器一起工作，1500接受相同的固件二进制作为100.2。和声驱动程序基本上是从ASF框架复制的。3。在ASF和Microchip实现之间有一些细微差别，所以请注意亚马逊Amazros分支4中列出的修复。Atmel ASF的WiLC和WiC-Doc比和声要好得多，而且大多数项目都是适用的。以上来自于百度翻译以下为原文 There is basically no point in using the WINC1500 in dumb mode with a PIC32MZ. What is to be gained? (I'm not sure what you mean by native vs host) My guess is that the core reason that Harmony is not doing a superloop is probably because they have only converted the asf framework to harmony, and haven't really written new code. I personally see converting the driver to a superloop as a challenge, as you'll have to rewrite Harmony/ASF to support it. A starting to point look would be to find all the xTaskCreates and convert those to superloops or ISR's, while making sure each loop doesn't block the other. Things I have learned along the way.. 1. The WILC1000 and WINC1500 both work with the 1000 driver, the 1500 accepts the same firmware binary as the 100. 2. The harmony drivers are basically copied from the ASF framework. 3. There are some slight differences between the ASF and Microchip implementations, so pay attention to the fixes listed in the Amazon FreeRTOS branch. 4. The Atmel ASF WILC and WINC doc's are much better than Harmony's, and most items are applicable.

2018-8-23 15:55:03 评论举报刘涛