Harmony docs错误

初学者工具包中的EC意味着嵌入式连接。不一定是EC芯片。好混乱，我不是100%肯定它是错误的。是的，他们似乎在电子商务芯片上得到了保释。因为他们有很多勘误表，这是可以理解的。如果您正在启动一个真正的项目，那么您应该得到新的启动工具包。



      以下为原文

    EC in the starter kit name means embedded connectivity. Not not necessarily the EC chips. Well confusing I'm not 100% sure it's wrong. And Yes they seemed to have bailed on the EC chips. Understandable since they have so much errata. If you are starting a real project, then you should get the new starter kit.

同意NKurzman。他们把EC系列揽给了EF。我最终也用EF芯片购买了新的DEV设备。



      以下为原文

    Agreed with NKurzman. They bailed out EC series to EF. I ended up buying the new dev set with EF chip too.

只需更改其中一个EF配置即可使用您的设备。除非项目出于某种原因使用ADC（这是EF与EC的不同模块），否则它仍然应该建立。就像其他人所说的，你可能想用EF来制作生产板，但是这种方法至少可以让你试用当前的硬件进行演示。



      以下为原文

    Just change one of the EF configurations to use your device.  It should still build unless the project uses the ADC for some reason (this is a different module on the EF vs EC).  Like others have said, you'll probably want to use the EF for production boards, but this way would let you at least try out the demo with your current hardware.

还要注意的是，涉及加密的示例应用程序意味着使用嵌入加密模块，该加密模块仅在EF芯片上可用，其中M的部件号为M。你可以在没有加密模块的情况下得到DEV板。所有用于EC或EFH芯片的应用将在EFM上运行。专门针对EFM的项目仍然可以在EC上工作，但不会有硬件加密的好处。这是相当多以太网的东西，比如WOLFSSL演示。正如上面所说的，EF芯片的ADC示例在EC芯片上根本不起作用，实际上它们完全取代了EF芯片中的不同硅的ADC，因为EC芯片中的一个是非常可怕的。ER项目的选择芯片的事项。John Vickers



      以下为原文

    Also note that the sample applications that involve encryption are meant to use the embedded encryption module that is only available on the EF chips with the M in the part number. You can get the dev board with and without the encryption module. All the application meant for EC or EFH chips will run on the EFM. Projects specifically for the EFM can still work on the EC, but will not have the benifit of the hardware encryption. This is pretty much Ethernet stuff, like the WolfSSL demo.
 
Also as said above, the ADC examples for the EF chip will not work at all on the EC chip, they actually completely replaced the ADC with different silicon in the EF chip because the one in the EC chip was so horrible.
 
I can't think of any other projects where the selected chip matters.
 
John Vickers

这是一个现有的项目。升级它从和谐1.09到2.02B不顺利，所以我想我会去熟悉的路线，使原始样本工作，然后重新导入我的所有文件和变化。我真的不想买另一个启动套件-我很恼火，我必须购买一个新的' G ' MRF模块，当和声不支持早期固件，没有升级工具可用。我有PIC32 MZ嵌入式连接（EC）启动器套件（密码），部分编号为D3366C与PIC32 MZ2048 ECM14。4、我选择了PIC32 MZYEFSKSKIOIOXEXFIOL FRIERTOS的配置，将设备设置为PIC32 MZ2048 ECM144，BSP为“PIC32 MZ EC启动工具包BSP”。ECM和EFM硅只是勘误表之间的区别吗？



      以下为原文

    It's for an existing project. Upgrading it from Harmony 1.09 to 2.02b didn't go well so I thought I'd go the familiar route of getting the original sample working and then re-importing all my files and changes.  
 
I don't really want to buy another Starter Kit - I'm annoyed I had to buy a new 'G' MRF module when Harmony didn't support the earlier firmware and there were no upgrade tools available.
 
I have the PIC32MZ Embedded Connectivity (EC) Starter Kit (Crypto), part number DM320006-C with a PIC32MZ2048ECM144.
 
I've selected the 'pic32mz_ef_sk__ioexp__freertos' configuration, set the Device to 'PIC32MZ2048ECM144' and the BSP to 'PIC32MZ EC Starter Kit BSP'.
 
Are the differences between the ECM and EFM silicon just errata fixes?

对WOLFSSL的加密应该在EFH PICS上工作，只比EFM慢（假设Hyn/WOLSFSSL使用加密硬件）。



      以下为原文

    The Encryption for WolfSSL should work on the EFH PICs, just slower than the EFM ones (assuming Harmony/WolfSSL uses the encryption Hardware.)

EF系列有一个FPU和一个略微更新的MIPS内核（EF上的战士M5150和EC上的MyApTIV M14K），但是编译器应该处理它。我认为大多数外围设备都是ADC以外的。在配置寄存器中可能有一些不同，但是和声配置器至少应该默认为半清醒值。当更新到V2.02B时，您遇到了什么问题？我已经能够从V1.07移到V2.01b，没有太多的麻烦，只要确保在新的MHC重新生成项目之前，就可以从项目中删除“BSP”和“框架”文件夹（在源文件和头文件文件夹中）。如果你不这样做，你会得到一堆“逻辑文件系统错误”消息，项目实际上不会重新生成。



      以下为原文

    The EF series has an FPU and a slightly newer MIPS core (Warrior M-5150 on the EF vs. the MicroAptiv M14k on the EC), but the compiler should handle that.  I think most of the peripherals are the same other than the ADC.  There might be some differences in the configuration registers, but the Harmony Configurator should at least default to semi-sane values for you.
 
What issues did you run into when updating to Harmony v2.02b?  I have been able to move from v1.07 to v2.01b without too much trouble; just make sure you remove the "bsp" and "framework" folders from your project (both in the Source and Header Files folders) before re-generating the project with the new MHC.  If you don't, you'll get a bunch of "Logical file system error" messages and the project won't actually re-generate.

我不记得什么问题更新到和谐2.02B。我打算再试一次，然后张贴结果。同时，似乎文档是正确的-以PIC32 MZ2048 ECM144为特色的D336C-C PIC32 MZ嵌入式连接（EC）启动器套件（Cuto to）工作。“PIC32的EthyWiFiffWebServer”的例子。我选择了“PIC32 MZYEFSKSKIOExpIXFieltos”配置，将设备设置为“PIC32 MZ2048 ECM144”。然后我进入密码设置，关闭H/W加速，重新生成和声配置和演示工作。尽管我的工具包有H/W加速的密码，如果我打开它，我得到链接错误。我猜新的硅有更好的支持，如果我调整加速度类型，我可能会得到加速我的ECM再次。无论如何，对于这些记录，这些错误是：…//..…//..…/Cyfto/Src/PIC32 MZ哈希。C：在函数“WCHI-ITITSHA256”中：..…//….. /框架/密码/ SRC/PIC32 MZ哈希。C:375：5:错误：函数的隐式声明“ReSeTyEngEngress”[ Werror =隐式函数声明] ReSeTyEngEngy（函数256’&….. /…/…/…/框架/密码/ SRC/PIC32 MZ哈希。C：在函数“WCXHA256Up更新”中：..…//..…/Frase/Frutto/Src/PIC32 MZ哈希.C:38：5:错误：函数“UpDATE-EngEng'”的隐式声明[ Werror =隐式函数声明] UpDATEY引擎（SAM256）“…………，…，……………………………………………………………………………………/……/…/….. /…/框架/密码/ SRC/PIC32 MZ哈希。HA256-和…G.DESC）；^….. /框架/密码/ SRC/PIC32 MZ哈希。C:39∶1:5：错误：函数“WaiThEngEngEnter”的隐式声明[ Werror =隐式函数声明] WaiThEngEngor（（Sh256- & G.；DESC），（CHAR *）Sh256- &；摘要，Sh256- HasyShand）；



      以下为原文

    I don't recall what the issues were updating to Harmony 2.02b. I am going to try it again though and will post the results.
 
In the meantime, it seems the documentation is correct - the DM320006-C PIC32MZ Embedded Connectivity (EC) Starter Kit (Crypto)' featuring the PIC32MZ2048ECM144 does work with the 'pic32_eth_wifi_web_server' example. I chose the 'pic32mz_ef_sk__ioexp__freertos' configuration, set the device to 'PIC32MZ2048ECM144'. Then I went to the Crypto settings and turned OFF h/w acceleration, re-generated the Harmony configuration and the demo worked. 
 
Despite my kit having h/w acceleration for the crypto if I turn it on I get linker errors. I'm guessing the newer silicon has better support and if I tweak the acceleration type I might be able to get acceleration on my ECM going again. Anyway for the record these were the errors:
 
../../../../../framework/crypto/src/pic32mz-hash.c: In function 'wc_InitSha256':
../../../../../framework/crypto/src/pic32mz-hash.c:375:5: error: implicit declaration of function 'reset_engine' [-Werror=implicit-function-declaration]
reset_engine(&(sha256->desc), PIC32_ALGO_SHA256) ;
^
../../../../../framework/crypto/src/pic32mz-hash.c: In function 'wc_Sha256Update':
../../../../../framework/crypto/src/pic32mz-hash.c:382:5: error: implicit declaration of function 'update_engine' [-Werror=implicit-function-declaration]
update_engine(&(sha256->desc), data, len, sha256->digest) ;
^
../../../../../framework/crypto/src/pic32mz-hash.c: In function 'wc_Sha256Final':
../../../../../framework/crypto/src/pic32mz-hash.c:390:5: error: implicit declaration of function 'start_engine' [-Werror=implicit-function-declaration]
start_engine(&(sha256->desc)) ;
^
../../../../../framework/crypto/src/pic32mz-hash.c:391:5: error: implicit declaration of function 'wait_engine' [-Werror=implicit-function-declaration]
wait_engine(&(sha256->desc), (char *)sha256->digest, SHA256_HASH_SIZE) ;

所以我开始把我的项目升级到2.02b，第一个问题是MHC从我的项目中删除了FrRetos，我留下了一个构建错误，说明使用Wi-Fi的DMA SPI在裸露的金属上是不被支持的。我将FrReTOS设置更改为最新版本（“FreeRTOS”）并重新生成项目。第二个问题是，我得到了很多编译器错误，例如：./SRC/CuppHHTPYAPAP.C：在函数“TCPPIpHtppIGEXECUTE”中：…/SRC/CuppHHTPYAPAP.C:148:29：错误：“AppHyDely3”未声明（第一次使用THI）。现在，我得到了很多链接错误，例如：C//用户/安得烈/代码/项目/ Nexus／Riangon /固件/SRC/CuuthHutpApp.c：1027：未定义的“AppHywitwitx”引用。我现在不关心开关，所以我评论所有的违规线路并重建。注意所有这些错误都涉及到和谐的自己的代码——我所写的都没有！构建完成OK，我运行代码。它起作用了吗？不，我在调试器中插入程序，转到“调用堆栈”窗口，然后单击“刷新”。一个对话框显示“软件调用堆栈信息不可用”。该项目有以太网、Wi-Fi、3 UART和通过DMA驱动的SPI接口。现在我需要决定是调试这个东西还是回到原来的演示，并开始逐步添加我自己的代码。3年前，我用MAL/MLA做了同样的事情，现在我用和声做了…



      以下为原文

    So I started upgrading my project to Harmony 2.02b and the first problem is that MHC removes FreeRTOS from my project and I'm left with a build error stating that using DMA SPI with Wi-Fi is not supported on bare metal. I change the FreeRTOS setting to the latest version ("FreeRTOS") and regenerate the project.
 
Second problem then is that I get loads of compiler errors such as:
 
../src/custom_http_app.c: In function 'TCPIP_HTTP_GetExecute':
../src/custom_http_app.c:148:29: error: 'APP_LED_3' undeclared (first use in this function)
             BSP_LEDStateSet(APP_LED_3, (*ptr == '1'));
 
I don't care about the LEDs right now so I comment out the offending lines and rebuild.
 
Now I get loads of linker errors such as:
 
c:/users/andrew/code/projects/nexus/rhiannon/firmware/src/custom_http_app.c:1027: undefined reference to `APP_SWITCH_1StateGet'
 
I don't care about switches right now so I comment out all the offending lines and rebuild.
 
Note that all these errors relate to Harmony's own code - nothing I've written!
 
The build completes ok and I run the code. Does it work?
 
Nope, I break into the program in the debugger, go to the 'Call Stack' window and click 'Refresh'. A dialog appears saying 'Software Call Stack Information Unavailable'.
 
The project has Ethernet, Wi-Fi, 3 UARTS, and an SPI interface driven via DMA.
 
Now I need to decide whether to debug this thing or just go back to the original demo and start incrementally adding my own code back in. 3 years ago I used to do exactly the same thing with MAL/MLA - now I do it with Harmony...
 

当从1.xx移动到2.xx时，请确保安装了2.02.xx版本的MHC，并确保它指向你的2.02B安装。有一些关于迁移的线程（包括一个来自我），你可以看看它们。



      以下为原文

    When Moving from 1.XX to 2.XX Make sure you install the 2.02.XX Version of MHC.
And Make sure it is Pointing to you 2.02b Installation.
There are a few threads about Migrating (including one from Me) you may what to look at them.

是的，我使用的是2.0.2.4的MHC和2.02B的和谐。



      以下为原文

    Yes, I'm using 2.0.2.4 of MHC and the 2.02b Harmony.