自定义启动固件，elf2img和中断向量表

在用最新的SDK调试我们的定制引导固件时，我发现最新版本的ELF2IMG使用程序头数据而不是区段数据来生成图像。
这使得它生成一个IMG文件，其中包括写入0x00到0xFF的地址，这是为中断向量表保留的，并在固件初始化中自动填充。
这将是很好的，除了使用自定义启动固件时，引导固件不会避免通过0xFF写入0x00，因此当写入该部分的命令进入时，它会损坏地址表中的向量表。然后迅速崩溃和失败。
要么生成一个避免写入0x00—0xFF的图像，要么修改USB启动代码以避免写入那些地址，从而修复了这个问题，但我很惊讶，这个问题在您的测试中没有被击中。



     以下为原文
  In debugging our custom boot firmware with the latest SDK, I found that the latest version of elf2img uses the program header data instead of the section data to generate the image.
    This causes it to generate an img file that includes writes to address 0x00 through 0xFF, which is reserved for the interrupt vector table and is automatically populated in the firmware initialization.
    This would be fine, except when using a custom boot firmware, the boot firmware doesn't avoid writing to 0x00 through 0xFF, and so when the command to write to that section comes in, it proceeds to clobber the vector table with bad addresses.  It then promptly crashes andfails.
    Either generating an image that avoids writing to 0x00-0xFF or modifying the USB boot code to avoid writing to those addresses fixes the issue, but I'm surprised that this issue has not been hit in your testing.