如何使用Harmony引导加载程序pic32mz

警告是存在的，因为设备ID在两个部分之间是不同的。因为RAM大小不同，所以不能只对普通的程序进行编程，因此堆栈可能无法工作。要开始将引导加载程序转换为您的部分，至少需要执行以下操作：更改UbDeVice中配置的部件号：PIC32 MZYEFSK。2。重新运行MHC。保持相同的配置文件。3。生成代码。现在，在编译时可能会得到一个错误，因为端口H（用于LED的SK BSP中的端口）不存在。对BSP进行更改，或者为硬件创建一个新的BSP。这将使引导程序适应大多数环境。



      以下为原文

    The warning is there because the DeviceID is different between the two parts. You won't be able to just program the normal one into it, because the RAM size is different, and the stack would probably not work as a result.
 
To start converting the bootloader to your part, you'll need to do at least the following:
1. Change the part number in the configuration for u***device_pic32mz_ef_sk.
2. Rerun MHC. Keep the same configuration file.
3. Generate the code.
 
Now, you'll probably get an error when compiling because port H (the one used in the SK BSP for the LEDs) doesn't exists. Make changes to the BSP, or create a new one for your hardware.
 
That should work for adapting the bootloader to most environments.

谢谢你的帮助。当我在MPLLABX的properties部分中将设备以及bsp_sys_init.cfrom端口H更改为端口E以及bsp.xml的按钮和交换机配置时，程序可以正确地编译。此外，引导加载程序应用程序也运行。以下是应用程序的输出：Device connectedBootloader固件版本：1.4Hex文件，成功加载FlashErasedProgramming completedVerification.fullCommand，用于运行applicationDevice.nected然而，我编程到的十六进制文件董事会似乎不起作用。我上传了一个简单的HEX文件，打开了其中一个LED。当我把它放到Bootloader中时，所有的LED都不亮。有什么问题吗？



      以下为原文

    Thanks for your help. When I changed the device in the properties section in MPLABX along with the bsp_sys_init.c from port H to port E and the bsp.xml's button and switch configurations, the program compiles properly. Also, the bootloader application runs too.
 
Here's the application's output:
Device connected
Bootloader Firmware Version: 1.4
Hex file loaded successfully
Flash Erased
Programming completed
Verification successfull
Command issued to run application
Device disconnected
 
However, the hex file I programmed into the board doesn't seem to work. I uploaded a simple hex file that turns on one of the LEDs. When I put it into the bootloader, none of the LEDs are on.
 
What could be the problem?

是否在应用程序中添加了一个合适的链接器文件以使其启动加载？



      以下为原文

    Did you add a suitable linker file in your applicaiton to make it boot-loadable?

如果您正在使用实际的AN1388App.，它没有覆盖PIC32MZ。和谐引导加载程序是基于App.（最初是按字面复制的）的。您可以从和谐中获得用于二者的合适的链接器脚本。它们最有可能工作。



      以下为原文

    If you are Using the Actual AN1388 Appnote it does not cover the PIC32MZ.
The Harmony Bootloader is based on the Appnote (copied literally at first).
You can get The Proper linker scripts for Both from Harmony.
They will most likely work.
 

我使用引导加载程序生成了链接器脚本，然后将app_mz.ld传输到我正在测试的应用程序项目中的链接器文件文件夹。然后，生成应用程序的HEX文件并将其用于引导程序中。即使如此，它仍然没有正确运行。我是否丢失或错误地执行了任何步骤？谢谢



      以下为原文

    I generated the linker script using the bootloader and then transferred the app_mz.ld to the linker files folder in the application project that I'm testing. Then I generated the hex file of the application and used it in the bootloader application. Even then, it still isn't running correctly.
 
Am I missing or incorrectly executing any steps?
 
Thanks

不，我不知道那是哪里。你能告诉我应用程序的设置在哪里吗？谢谢



      以下为原文

    No, I don't know where that is. Could you show me where the application settings are?
 
Thanks

不幸的是，它仍然没有发挥作用。可以确定，外部链接器脚本设置用于生成十六进制文件，该文件使用引导加载程序之外的内存，以便与引导加载程序兼容，对吧？还有，我还有什么不见的吗？



      以下为原文

    Unfortunately, it still didn't work. Just to be sure, the external linker script settings are for when you want to generate a hex file that uses memory outside of the bootloader so that it is compatible with the bootloader right?
 
Also, is there anything else that I might be missing?

你使用和声1.08吗？我已经从Microchip的支持证实今天有一个错误与Teh BooooDER在1.08。虽然我使用的是以太网引导加载程序，而不是USB，但我基本上遇到了同样的问题。在以太网SK上，按下按钮3，将把设备放回到booloader模式，然后如果你连接到PC主机应用程序，并发送一个“Run pplcation”，应用程序将运行。您可能想回滚到Harmony 1.07，bug不存在，因为在1.07中他们提供了u***示例，但没有udp版本。



      以下为原文

    Are you using Harmony 1.08?    I have had it confirmed from Microchip support today that there is a bug with teh booloader in 1.08.  I am having the same issues essentially that you are,  though i'm using the ethernet bootloader, rather than USB.      


On the ethernet SK, pusing button 3, will put the device back into booloader mode, and then if you connect to it with the PC host appl, and send it a "Run pplcation", the app will run..   

You might want to roll back to Harmony 1.07,  the bug is not there, you are forutante they provided a u*** example in 1.07, but no udp version.. 
 
As soon as i know what the fix is, i'll let you nw.
 
 
 

详细信息：Hyp.//www. McCHIP.COM/FUMMS/M94066ASPX



      以下为原文

   

Details here.
http://www.microchip.com/forums/m940668.aspx

它不会影响我，因为我可以多次擦除和重新编程。请注意，EC链接器文件可能无法与EF一起工作，因为EF具有浮点寄存器，以便在中断时保存/恢复，除非它们被禁用。



      以下为原文

    It does not affect me since I can erase and reprogram multiple times.
Note the EC Linker file may not work with the EF, since the EF has the Floating Point register to save/ restore on an interrupt unless they are disabled.

我尝试了Harmony1.07的引导加载器示例，遇到了来自三个或四个不同文件的多个问题。NKER文件。应用程序是一个简单的和谐项目，打开一个单一的LED板上。根据每个应用程序显示图像，这是正常的吗？应用程序链接器ELF文件似乎在大量的数据中进行争夺，同时也占用了比以前更多的内存。



      以下为原文

     
I tried Harmony 1.07's bootloader example and I ran into multiple issues that were coming from three or four different files.
 
Afterwards, I decided use elf viewer to look into 1.08's code again and compared my original application elf file with the elf file of the application using the application linker file. The application is a simple Harmony project that turns on a single LED on the board. The images are labeled according to each application being displayed.
 
Is this normal? The application linker elf file seems to scramble around a lot of the data, while also taking more memory than it used to.
 
Thanks
   Attached Image(s)