请问加载程序试图写入引导区的原因是什么？

亲爱的成员，我的Bootloader项目（XC32），基于“USB拇指驱动引导加载程序（beta 1）”，总是在前面有效的加载步骤之后生成错误“Max闪存地址”。错误意味着，写入Flash的应用程序的下一个地址超出有效范围。当这个错误发生时，地址是0x1fc00 800，这是我的PIC32 MX230F256B的引导闪存区域中的一个地址。在这个论坛中学习了很多关于Bootloader问题的线程之后，我仍然不知道如何解决这个问题：（有人能告诉我什么是这个吗？）加载程序试图写入引导区的原因是什么？这里是我的应用程序的链接器脚本：欢迎任何帮助！亲切关怀



      以下为原文

    Dear members,

my bootloader-project (XC32), based on "USB Thumbdrive Bootloader (BETA 1)", always generates the error "MAX_FLASH_ADDRESS" after previous valid load steps. The error means, that the next address of the application to write into flash exeeds the valid range. When this error occurs, the address is 0x1FC00800, which is an address in the boot flash area of my PIC32MX230F256B.

After a long time of studying a lot of threads regarding bootloader issues in this forum, I still don't know how to solve that problem :-(

Can anybody please tell me what could be the reason for the loader tries to write into the boot-area?

Here is the linker script of my application:


/*************************************************************************
* Processor-specific peripheral libraries are optional
*************************************************************************/
OPTIONAL("libmchp_peripheral.a")
OPTIONAL("libmchp_peripheral_32MX230F256B.a")

/*************************************************************************
* Processor-specific object file. Contains SFR definitions.
*************************************************************************/
INPUT("processor.o")

/*************************************************************************
* http://www.microchip.com/forums/m773400.aspx
*************************************************************************/
SECTIONS
{
  /DISCARD/ : { *(._debug_exception) }
}

/*************************************************************************
* For interrupt vector handling
*************************************************************************/
PROVIDE(_vector_spacing = 0x00000001);
_ebase_address = 0x9D018000;

/*************************************************************************
* Memory Address Equates
* _RESET_ADDR -- Reset Vector
* _BEV_EXCPT_ADDR -- Boot exception Vector
* _DBG_EXCPT_ADDR -- In-circuit Debugging Exception Vector
* _DBG_CODE_ADDR -- In-circuit Debug Executive address
* _DBG_CODE_SIZE -- In-circuit Debug Executive size
* _GEN_EXCPT_ADDR -- General Exception Vector
*************************************************************************/
_RESET_ADDR = (0x9D018000 + 0x1000);
_BEV_EXCPT_ADDR = (0x9D018000 + 0x1000 + 0x380);
_DBG_EXCPT_ADDR = (0x9D018000 + 0x1000 + 0x480);
_DBG_CODE_ADDR = 0x9FC00490;
_DBG_CODE_SIZE = 0x760;
_GEN_EXCPT_ADDR = _ebase_address + 0x180;


/*************************************************************************
* Memory Regions
*
* Memory regions without attributes cannot be used for orphaned sections.
* Only sections specifically assigned to these regions can be allocated
* into these regions.
*************************************************************************/
MEMORY
{
  kseg0_program_mem (rx) : ORIGIN = (0x9D018000 + 0x1000 + 0x490), LENGTH = 0x40000 - (0x18000 + 0x1000 + 0x490)
  kseg0_boot_mem : ORIGIN = 0x9D018000, LENGTH = 0x0
  exception_mem : ORIGIN = 0x9D018000, LENGTH = 0x1000
  kseg1_boot_mem : ORIGIN = (0x9D018000 + 0x1000), LENGTH = 0x490
  debug_exec_mem : ORIGIN = 0x9FC00490, LENGTH = 0x760
  config3 : ORIGIN = 0xBFC00BF0, LENGTH = 0x4
  config2 : ORIGIN = 0xBFC00BF4, LENGTH = 0x4
  config1 : ORIGIN = 0xBFC00BF8, LENGTH = 0x4
  config0 : ORIGIN = 0xBFC00BFC, LENGTH = 0x4*/
  kseg1_data_mem (w!x) : ORIGIN = 0xA0000000, LENGTH = 0x4000
  sfrs : ORIGIN = 0xBF800000, LENGTH = 0x100000
  configsfrs : ORIGIN = 0xBFC00BF0, LENGTH = 0x10
}


Any help is welcome!

kind regards
rom