PIC32 MZ2048 EFM144怎么快速开始开发

如果你习惯于把你的整个应用程序放在一个文件中，那么你将面临一个重大的范式转变。我建议从微芯片中获得一个初学者工具箱，并为该板运行一个现成的演示。然后，您可以看到工作代码并使用调试器或只是读取文件进行拨号。这些项目组织得很好。在HythRelial.CHM文件中有很多帮助，你可以在LoTydir & Gt//DOC.I＆Lt:Dealdir & Gt//App/Exp/外围设备和系统中找到，有很多单用途示例项目。



      以下为原文

    If you are used to having your entire application in just one file you will be in for a major paradigm shift.
 
I would recommend getting a starter kit board from Microchip and running an off-the-shelf demo for that board.  You can then see working code and poke about using the debugger or just read the files.  The projects are well organized.  There is a lot of help for beginners in the Harmony Help .chm file, which you can find in /doc.
 
In /apps/examples/peripheral & system there are lots of single-purpose example projects.

米夏埃尔.沃尔什，有没有什么好的训练材料？它有时会知道如何攻击它。



      以下为原文

    Micheal, is there any good training materials for Harmony... Its  such a struggle at times to know how to attack it.

你好，米迦勒，非常感谢你的迅速回复。它的真的习惯于在一个文件中拥有整个应用程序，我有一个Explorer 16板，我真的需要把我的头包裹在和谐的概念上，并构建一个引导程序，它通过RN4020蓝牙模块将程序数据带到UART上。



      以下为原文

    Hi Michael, 
 
Thank you very much for your swift reply. Its true am used to having entire applications in one file, I have an Explorer 16 Board and I really need to get my head wrapped around the the concepts of Harmony and build a bootloader that that takes program data over UART via RN4020 bluetooth module.

嗨，你可以找到很多培训材料，一步一步的教程在这里和谐：http://MyCHIPIPDeals.com /培训自我：星际争霸



      以下为原文

    Hi,
you can find a lot of training material, step by step tutorials on Harmony here :
http://microchipdeveloper.com/training-self:start
Regards
 

支持和谐的文档有8500多个PDF页面，但在这一点上大部分都不感兴趣。大多数都在第4卷中找到。第1卷开始于MPLAB和声-在PDF卷2页580页中，MPLAB和谐配置器- PDF卷3页183页，MPLAB和谐发展- PDFLATH 4页98页，MPLAB和谐框架参考文献5第三方产品- 74页PDF卷6实用程序PDF卷1—3中的PDF- 24页是您应该开始的地方。在应用程序中或在演示中使用的外围设备中找到一个接近您预期的最终项目的演示。得到一个应用程序将运行并尝试它的板。可以使用调试器跟随应用程序的流程。您可以使用MPLAB和谐配置器（MHC）来修改演示所做的操作，然后进行代码再生、生成、加载和运行。这将给您一个关于和谐和MHC如何协同工作的感觉。我建议您在代码配置套件（如Git、SuthCaseFe、Svn或等效）的保护伞下工作。这样，如果你的项目是因为MHC的错误，你可以恢复。



      以下为原文

    There are over 8500 PDF pages of documentation supporting Harmony, but most of it isn't of interest to you at this point.  Most of this is found in Volume 4.
 
Volume 1 Getting Started with MPLAB Harmony - 580 pages in the PDF
Volume 2 MPLAB Harmony Configurator - 183 pages in the PDF
Volume 3 MPLAB Harmony Development - 98 pages in the PDF
Volume 4 MPLAB Harmony Framework Reference
Volume 5 Third-Party Products - 74 pages in the PDF
Volume 6 Utilities.pdf - 24 pages in the PDF
 
Volumes 1 - 3 are where you should start.  Find a demo that is close to your intended end project, either in the application or perhaps in the peripherals that are used in the demo.  Get a board that the app will run on and try it out.  You can use the debugger to follow the flow of the application.  You can modify what the demo does using MPLAB Harmony Configurator (MHC) followed by a code regeneration, build, load, and run.  This will give you a feeling as to how Harmony and MHC work together.
 
I would recommend you work under the umbrella of a code configuration suite such as GIT, SourceSafe, SVN or equivalent.  That way if your bork your project because of a mistake in MHC you can recover.

卷1开始与MPLAB和谐- 580页在PDFAMAMED如何从ASM到和谐是如此繁琐。奇怪的是，它在装配过程中更容易和更快地发展。



      以下为原文

    Volume 1 Getting Started with MPLAB Harmony - 580 pages in the PDF
 
Amazing how a shift from ASM to harmony is so cumbersome. Wonder its its much easier and faster to keep developing in Assembly.
 
 

一个汇编语言的页面和一个完整的、基于和谐的应用程序在复杂度上是光年相隔的。您不打算在组装中编写TCP/IP栈或USB驱动程序。一个拥有5“800×480像素触摸界面图形显示的家庭自动化站”也不是在汇编程序中编写的。关键是要仔细管理项目的复杂性，并使用尽可能多的已知代码，从其他地方请求/借用/窃取。这样你就可以在孙子大学毕业之前完成。



      以下为原文

    A page of assembly language and a full-up, Harmony-based, application are light years apart in complexity.  You aren't going to write a TCP/IP stack or USB driver in assembly.  A home automation station with a 5" 800x480 pixel graphics display with touch interface isn't written in assembly either.
 
The key is to carefully manage the complexity of the project and use as much known-good-code as you can beg/borrow/steal from someplace else.  That way you can finish before your grandchildren graduate from college.

我看到自己真的快要失去我的工作了。哈哈：我现在也不能用PLIB了。现在完全糊涂了。



      以下为原文

    Well I see myself getting really close to losing my employment here. LoL:
Cannot use PLIB as well now can I? Consummately confused now.

你可以继续写点C和汇编，永远不会接近和谐。如果你不打算使用和声，那么我不建议尝试只使用外围语言（PLIB）。只需敲击控制外部设备的特殊功能寄存器（SFRS）就更容易了。



      以下为原文

    You can continue to write bit-banged C and assembly and never get close to Harmony.   If you aren't going to use Harmony then I don't recommend trying to use just the Peripheral Libararies (PLIBs).  It is simply easier to bit-bang the Special Function Registers (SFRs) that control the peripherals.

谢谢，我会尝试阅读5K页的PDF文档，希望在另一个软件包到来之前获得和谐。



      以下为原文

    Thank you, 
 
I will try read the 5K pages of pdf documents and hopefully get hang of harmony before another package comes 

你的和谐计划是什么？TCP/IP？USB？触摸屏？取决于你计划什么，它会影响建议。你可以使用和声PLIB完成一些任务。引导加载程序本身是一个项目。你需要修改它的UART版本的蓝牙。它创建一个链接器文件，您将需要用于主项目。你做了PIC24吗？PIC32外设相似。



      以下为原文

    What are you plans for Harmony?
TCP/IP? USB? A touch screen?
Depending on what you are planing it will affect the advice. You can use the harmony PLIB for some tasks.
The bootloader itself is a project. You will need to modify the UARTversion of it for blue tooth. It creates a linker file that you will need to use for the main project.
Have you done PIC24? The PIC32 peripherials are similar.

酷，谢谢，NKurzman。我打算使用蓝牙（MLDP模式中的RN4020），并使用蓝牙作为我的Bootloader UART。我也有MRF24J40MAF收发器模块和一些其他SPI和UART模块和芯片。我们的想法是让蓝牙引导装载机工作，然后把产品拿到那里，并提供我们的更新。NKurZAN我看到你的“和谐地狱在一个篮子篮咆哮”。你对和谐的不满消退了吗？



      以下为原文

    Cool, Thanks NKurzman. I intend to use Bluetooth (RN4020 in MLDP mode), and use Bluetooth as my Bootloader UART. I also have the MRF24J40MA RF Transceiver Module and a couple other SPI and UART modules and chips. The Idea is to get the Bluetooth bootloader working then get the product out there and provide updates as we go along.
 
NKurzan I saw your "Harmony Hell in a Hand Basket Rant." Has your displeasure with Harmony subsided? 

它并没有消退，但我也没有使用V2.xx。问题不是和谐是不可用的，它是很难使用的，有一步学习曲线，文档和支持差。所有的销售资料都夸耀着和谐会拯救你多少时间。最近有更多的和谐团队成员张贴在这里，这是一个进步。UART与PIC24相同。如果你有这个代码，你可以使用它。我个人认为和谐驱动程序过于复杂，有很多开销。我没有理由再去拜访他们。矿井工作精细。他们仍然不提供环形缓冲区。SPI驱动程序似乎更好，但我也在使用我自己的。WiFi模块驱动程序有一些问题。或打算修复。您可能需要使用RTOS作为工作。此外，微芯片购买了Atmel，并迷上了他们的无线电模块。它似乎更便宜更好。并有当前的和谐支持。WiFi可能需要一个堆栈，这取决于你在做什么。如果是这种情况，那么你将需要使用与MZ CPU的和谐。TCP/IP协议栈赢得了较好的协调部分。你有操作蓝牙的代码吗？如果是的话，你可以在EVE板上试试。我不知道和谐蓝牙驱动程序给了你什么。我们没有在我们的项目中使用它。



      以下为原文

    It has not subsided, but I am not using v2.xx either.
The issue is not Harmony is unusable, it is it is hard to use, has a step learning curve, poor documentation and support.
All While the sales material brags about how much time Harmony will save you.
Lately there are more harmony team members posting here, it is an improvement.
The uart is the same as the pic24. You can use that code if you have it. I personally think the harmony driver was over complicated and had a lot of overhead. There is no reason for me to revisit them. Mine work fine. They still do not offer a ring buffer.
The SPI driver appears to be better, but I am using my own ther too.
That wifi modules driver has some issues that they apperently do. Or intend to fix. You may need to use an RTOS as a work around. Additionally microchip bought Atmel and is enamored with their radio module. It appears to be cheaper and better. And has current support in harmony.
The wifi may require a stack depending on what you are doing. If that is the case then you will need to be using Harmony with the MZ CPU. The tcp/ip stack is won of the better parts of Harmony.

Do you have code to operate the Bluetooth already? If so you can try it on an eval board. I am not sure what the harmony Bluetooth driver gives you. We did not use it on our project.

FYY，Atmel“WiC”WiFi驱动程序的和声当前实现采用了“哑”模式，并与微芯片TCP/IP协议栈进行了对话。WiC芯片也有一个“智能”模式，整个TCP/IP栈都在WiFi芯片上。如果你使用这个模式，那么你需要在CPU上实现的就是SPI接口。我们在我们的产品中使用了“智能”模式的芯片，内置的TCP/IP协议栈看起来非常可靠，不知道为什么Microchip做出了这个决定。可能是因为它更容易保持与旧WiFi模块的兼容性。缺点是TCP/IP协议栈使用了大量CPU内存，如果你想要安全性和制作商业产品，你需要为第三方“狼SSL”TLS包付费。



      以下为原文

    FYI, The Harmony current implementation of the Atmel "WINC" WiFi driver uses the part in "dumb" mode and has it talk to the Microchip TCP/IP stack.  The WINC chip also has a "smart" mode where the whole TCP/IP stack is on the WiFi chip.  If you use this mode then all you need to implement on the CPU is the SPI interface.  We use this chip in "smart" mode on our products and the built in TCP/IP stack seems very reliable.
 
Not sure why MIcrochip made this decision.  Probably because it is easier to maintain compatibility with the older WiFi modules. The downside is the TCP/IP stack uses a lot of CPU memory, and if you want security and make commercial products you need to pay for a third party "Wolf SSL" TLS package. 

有趣的关于Atmel部分的注释。在哑模式下使用和声栈的其他优点是在同一个项目中具有有线和无线的能力，而其他集成服务和谐提供了能力。Wolf SSL并不是唯一的选择。MSB-SSL是一种积极性，但和睦不能提供整合。



      以下为原文

    Interesting note about the Atmel part.
The other advantages of using it in dumb mode with the harmony stack is the ability to have wired and wireless in the same project and the other integrated service Harmony provides.
Wolf SSL is not the only choice. Mbed SSL is a posiblity, but Harmony does not provide the integration.

OHK，这里看起来有点热，不是吗？我想也许我使用PLIB并构建自己的库来构建蓝牙引导程序和RF链接与MRF芯片。然后在现场建立机器的更新，包括WiFi和以后所有的。你认为那会飞吗？



      以下为原文

    Ohk, 
 
Looks am in some hot water here am I not? Well I was thinking that maybe I use PLIB and construct my own libraries to build the bluetooth bootloader and RF-link with the MRF chip. Then build updates for the machine whilst in the field to include WIFI and all later. Do you reckon that will fly?

不管你的和声决定，我都不推荐MRF芯片。“B”和“G”模块不推荐用于新的设计，他们推荐WiC芯片作为替代品。我个人认为他们可能会淘汰MRF范围，包括“n”部分，以支持Atmel“WiC”范围。



      以下为原文

    Regardless of your Harmony decision, I would not recommend the MRF chip.  The "B" and "G" modules are not recommended for new designs and they are recommending the WINC chip as the replacement. 
 
My personal opinion is they may obsolete the MRF range, including the "N" part, in favor of the Atmel "WINC" range

蓝牙只不过是UART引导加载程序的一个扩展。



      以下为原文

    The blue tooth will just be an extension to the uart bootloader.