请问有人能用U1TXRG和U1RXRG做引导加载程序吗？

好的，我想我终于发现了这个错误，所以我还是分享一下吧。首先，必须遵循“EZBL Library Documentation.pdf”中的每一行。现在，我知道了过程，该文档使senseLoL更加敏感：因此：如果要使用uart来引导加载，您需要从ex_boot_uart项目开始。所以你需要在Mplab打开这个项目，然后选择你的PIC模型。但是等等！如果你在HurdRialIpdialIsHealver文件夹中查看，那里有一些图片和它们的DeV板。如果你没有列出，你必须复制其中一个，并基本上复制它为您的硬件。确保你也把你的配置位在这个文件。如果您选择的是未在HaveRealPixalIsIsHER文件夹中列出的PIC，则默认情况下它会选择一个DSIC33。这可能与您的实际硬件不匹配，并且会引起问题。既然已经为实际硬件创建了._initializer，那么编译ex_boot_uart项目。这将创建上面原始帖子中的错误中抱怨的merge.gld和merge.s文件。从库文档.PDF执行-gt；5，将这些文件（Mel.GLD和.s）添加到您的项目中。当你编译你的项目时，它需要知道引导加载程序在哪里，所以它不会覆盖任何一个。您的项目不能定义配置字，因为它们已经在ex_boot_uart中定义，该ex_boot_uart现在通过.gld和.s文件链接。现在，您应该能够编译实际的应用程序项目，并生成一个.hex文件。现在你应该能够使用“Java-jar……”命令将你的实际应用HEX文件发送到你的实际硬件，它应该接收它，编程它，并开始执行它。如果你想编写自己的PC应用程序，请看EZBL通信。基本上，通过串行发送命令，引导加载程序响应。当程序准备就绪时，它将从.blob文件中请求一定数量的字节，然后您的PC应用程序将使用.blob文件进行响应。来回，直到整个程序被发送。



      以下为原文

    Alrighty, I think I finally figured out this error, so I might as well share it.
 
First off, every single line in "EZBL Library Documentation.pdf" must be followed.  Now that I know the process, that document makes a lot more sense LoL:
 
So:
If you want to use the uart to bootload, you need to start with the ex_boot_uart project.  So you need to open that project in Mplab, then choose your PIC model.  But wait! If you look in the Hardware_Initializers folder, there are some PICs and their dev boards there.  If yours is not listed, you'll have to copy one of them, and essentially duplicate it for your hardware.  Make sure you put your config bits in this file as well.  If you choose a PIC that is not listed in the hardware_initializers folder, it appears to choose a dspic33 by default.  This may not match your actual hardware, and will cause issues.
 
Now that you have created a hardware_initializer for your actual hardware, compile the ex_boot_uart project.  This will create the merge.gld and merge.s files complained about in the error in the original post above. 
 
Now, go to your actual application project.  From the Library Documentation.pdf Execution->#5, add those files (the merge.gld and .s) to your project.  When you compile your project, it needs to know where the bootloader is, so it doesn't overwrite any of it.  
Your project cannot have the configuration words defined, since they are already defined in the ex_boot_uart, which is now linked through the .gld and .s files.  
Now, you should be able to compile your actual application project, and generate a .hex file.
 
Finally, use your pickit3 (or whatever) to program the .hex from the ex_boot_uart project to your actual hardware.  Now you should be able to use the "java -jar ........" command to send your actual application hex file to your actual hardware, and it should receive it, program it, and start executing it. 
 
If you want to write your own PC application, look at the EZBL communications.pdf.  Basically, you send commands over serial, and the bootloader responds.  When it's ready for the program, it asks for a certain number of bytes from the .blob file, which your PC application would then respond with.  Back and forth, until the entire program is sent.