MPLAB的PIC24EP单片机引导加载程序问题？

我在PIC24EP引导装载器上工作。我的Bootloader有自己的包格式来与Python脚本通信来更新微控制器的固件。引导加载程序驻留在中断向量表（0x000 0800）之后的第一个空闲页面中。在PIC24EP中没有替代的IVT，并且我在Bootloader中都没有使用任何中断。为了给应用程序腾出空间，我已经编辑了我的应用固件的链接器脚本，以便应用程序的HEX文件不会在0x200和0x00 5bf0之间使用任何空间。应用程序的链接器脚本在下面给出：/**内存区域*/内存{数据（A）！XOR＝0x1000，长度＝0x800 0Read：原点＝0x0，长度＝0x4IVT:原点＝0x1fcPalm（XR）：原点＝0x6000，长度＝0x23 FFEFICD：原点＝0x2FAF0，长度＝0x2FPOR：原点＝0x2FAF2，长度＝0x2FWDT：原点＝0x2AFF4，长度＝0x2FoC:Orth= 0x2AFF6，长度=0x2fOSCL:Orth= 0x2FGS：Orth= 0x2FAFA，长度＝0x2FUID0:长度＝0x2FuID1：Orth= 0x2FuFa，长度＝0x2FuID2：Orth= 0x2Fui3:长度＝0x2FuFe，长度＝0x2}，FICD= 0x2AFF0；γ-fPOR＝0x2AFF2；γ-fWdt= 0x2AFF4；FSCOSEL＝0x2AFF8；γ-Fui0= 0x800 FF8；γ-FuID1= 0x800 FFA；γ-FuID3= 0x800 FFE；γ-CydObase= 0x6000；γ-CODEL长度＝0x2FFE；γ-IVTBASBASE＝0x4；γ-DATAOBASE＝0x1000；γ-DATAAL长度＝0x8000；它看起来像我的Bootloader在某个点拒绝固件（HEX文件）。Af6在0x200和0x00 5bf0之间有地址，但是我已经编辑了应用程序链接器脚本，只修改了变量0x6000的地址：修改代码，代码长度和程序。Flash的大小是256KB，页面大小是1024个指令（1024×4字节）。HEX文件已经结束（http://PaistBi.com /xHuSjxKu）。链接器脚本已经结束（http://PaistBi.com /Gb2YimWC）。



      以下为原文

    I am working on pic24EP bootloader. My bootloader has it's own packet format to communicate with a python script to update the firmware of the microcontroller. The bootloader resides at the first free page after Interrupt Vector Table (0x000800). There is no alternative IVT in PIC24EP and neither i am using any interrupts in my bootloader. To make space for application, i have edited linker script of my application firmware so that application hex file wouldn't use any space in between 0x200 and 0x005BF0. The linker script of application project is given below:

/*
** Memory Regions
*/
MEMORY
{
  data (a!xr) : ORIGIN = 0x1000, LENGTH = 0x8000
  reset : ORIGIN = 0x0, LENGTH = 0x4
  ivt : ORIGIN = 0x4, LENGTH = 0x1FC
  program (xr) : ORIGIN = 0x6000, LENGTH = 0x23FFE
  FICD : ORIGIN = 0x2AFF0, LENGTH = 0x2
  FPOR : ORIGIN = 0x2AFF2, LENGTH = 0x2
  FWDT : ORIGIN = 0x2AFF4, LENGTH = 0x2
  FOSC : ORIGIN = 0x2AFF6, LENGTH = 0x2
  FOSCSEL : ORIGIN = 0x2AFF8, LENGTH = 0x2
  FGS : ORIGIN = 0x2AFFA, LENGTH = 0x2
  FUID0 : ORIGIN = 0x800FF8, LENGTH = 0x2
  FUID1 : ORIGIN = 0x800FFA, LENGTH = 0x2
  FUID2 : ORIGIN = 0x800FFC, LENGTH = 0x2
  FUID3 : ORIGIN = 0x800FFE, LENGTH = 0x2
}

__FICD = 0x2AFF0;
__FPOR = 0x2AFF2;
__FWDT = 0x2AFF4;
__FOSC = 0x2AFF6;
__FOSCSEL = 0x2AFF8;
__FGS = 0x2AFFA;
__FUID0 = 0x800FF8;
__FUID1 = 0x800FFA;
__FUID2 = 0x800FFC;
__FUID3 = 0x800FFE;
__CODE_BASE = 0x6000;
__CODE_LENGTH = 0x23FFE;
__IVT_BASE = 0x4;

__DATA_BASE = 0x1000;
__DATA_LENGTH = 0x8000;

It looks like my bootloader rejects firmware (hex file) at some point as it has address in between 0x200 and 0x005BF0 but i have edited the application linker script to only use addresses above 0x6000 by modifying variables: __CODE_LENGTH and program.

The size of flash is 256kB and page size is 1024 instructions (1024*4 Bytes). The Hex File is over (https://pastebin.com/XHUsjxku). And the linker script is over (https://pastebin.com/gB2YimWC).