Application Hex记录和Bootloader Hex Record之间的区别？

英特尔HEX文件对于引导加载程序没有什么不同。



      以下为原文

    The Intel hex file is not different for the bootloader.

不确定你在这里问什么。如果你想要一个好的答案，你就必须弄清楚你想知道什么，你的意思是什么不同。



      以下为原文

    Not sure what you are asking here.  If you want a good answer you may have to clarify what you want to know, what you mean by difference.
 

你是在删除配置词并试图通过RTSP编程吗？我熟悉PIC32 MX，通过RTSP更新配置词是不可能的，所以很可能你这么做了，因为它失败了吗？



      以下为原文

    Are you erasing the configuration words and trying to program via RTSP?  I am familiar with PIC32MX, and updating the configuration words via RTSP was not possible, so quite possibly you are doing this and it is failing because of this? 

嗨，Friesen，谢谢你从我这里请求更多的输入。我正在尝试用主应用固件更新Bootloader HEX文件来更新引导闪存区域。为此，我使用与基本的Bootloader相同的源文件，在和谐的示例应用程序中。我是OncOK引导闪存1，然后擦除它，但是无法使用NVM.C文件中的AppHythCuxReCordReNo（）函数编写十六进制记录。我尝试通过使用AppOnnvMQueWordWrdRead（）函数编写四字，并且我能够编写它。AppHyPosixCordReordNo（）函数检查接收的数据是否是有效的十六进制记录。所以我的问题是，只有应用程序和Bootloader的HEX记录是否不同？正如Nkurzman所说，这没有什么不同。那么为什么这个函数不下载HEX文件呢？



      以下为原文

    Hi Friesen, Thanks for asking for more input from me.
I am trying to update boot Flash area with updated bootloader hex file from Main application firmware. For that I am using same source files as that of basic bootloader in Harmony sample apps. I am uplocking boot flash 1, then erased it, but unable to write the Hex records using APP_ProgramHexRecord() function in nvm.c file. I tried simply by writing Quad Word using APP_NVMQuadWordWrite() function and I am able to write it. 
APP_ProgramHexRecord() function is checking whether the received data is valid Hex record or not. So my question is regarding that only, whether the App and Bootloader Hex Records are different? 
 
As Nkurzman said, it's not different. Then why this function not downloading hex file?

还没有看到代码，但它可能包含一个检查，以确保您不会意外地覆盖引导加载程序。



      以下为原文

    Haven't seen the code, but it may contain a check to make sure you DON'T accidentally overwrite the bootloader.

由于您在引导加载程序中，因此了解HEX文件格式将是有益的。因特网上有丰富的关于它们的信息，微芯片的Pic32网站上的编程规范也详细介绍了HEX文件等等。你应该知道这一点。只有这样你才能理解你的十六进制文件的真实差异。在掌握了这一点之后，开发C或CPP的应用程序来解析HEX文件以了解内存正在被修改和大小等等，甚至更好。如果您能够做到这一点，那么论坛成员就不会有任何问题。本质上，十六进制文件是“ASKY”（人类可读文件）编译地址和数据来写入这些偏移。一旦你解码了“神秘”，你知道该丢弃什么，并在这些文件中使用，以成功地编程。编辑-显然，这篇文章中的条目不同意这个论坛的过滤或类似性质的东西。直到我改变了一些考试，我才开始努力工作。烦人的。。。



      以下为原文

    Since you are in the business of bootloaders, it would be beneficial to understand the hex file format.  There is wealth of information on internet about them and the programming specifications on Microchip's website for your PIC32 also goes into detail about hex files and such.  You should know this.  Only then can you understand the true differences of your hex files.  After you master this, it would be even better for you to develop an application via C or Cpp to parse your hex files to understand what memories are being modified and sizes, etc.  If you are able to do this, then you will have no questions for the forum members.  Essentially, the hex files are "ASKy" (human-readable files) compilations of addresses and data to write in these offsets.  Once you decode the "mystery" you know what to discard and use in these files to program successfully. 
 
EDIT - apparently there are items in this post that do not agree with this forum's filtering or something of that nature.  Had a difficult time getting this to work until I changed some of the test.  Annoying...