PIC32MX Bootloader混淆

我正在尝试让HootBootloader加载我的其他应用程序。我使用的是产品版本：MPLAB X IDE V4.15Java:1.8 0144；Java热点（TM）64位服务器VM 25.144-B01Runtime:Java（TM）SE运行时环境1.80y144-B01Stase:Windows 10版本10在AMD64上运行；CP1252；EnUUS（MPLAB）和和声版本V2Y05Y01I，用PIC32 MX795F512L PI运行。M在ExpReab16BoADI已经使用Orthor生成了Bootloader。我使用GPIO交换机（交换机3）PIN来检测引导加载程序的改变，并且LED闪烁显示我在Bootloader中，这里都很好。生成的BTLYMX.LD文件有以下的值SyrSeTeEdAdDR＝0xBFC000；EVA ExpPTIAdDR＝（0xbfc00+0x380）；不可用于孤儿节。*仅分配给这些区域的部分可以分配到这些区域中。************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************C01000，长度＝0x100/*中断向量表*/CONT3：Orth= 0xBFC02FF0，长度＝0xBFC02FF4，长度＝0x4配置1：Orthe= 0xBFC02FF8，长度＝0x4配置0：Orth= 0xBFC02FFC，长度＝0x4KSSE1B-BooToMeM:原点＝0xbfc000，长度＝0x300／*c启动代码*/KSEG1XDATAYMEM（W）！X）：Oracle＝0xA000 000，长度＝0x2万SFRS：Orthe= 0xBF8000，长度＝0x100000 Debug gExpReMeM:原点＝0xBFC02000，长度＝0xFF0配置FRS：Orthe= 0xBFC02FF0，长度＝0x10}，现在我将通过OrthyOpHelpHyVuluMyV.PDF文件（以下）中找到的指令。这似乎我需要改变长度= 0x2AF0-gt；0x3000以上的KSG00Sudio MyMeMe，但在步骤4）我真的很困惑。Bootloader SypLyFig .h（下）对于APPYFLASH BaseX地址（0x9d00）具有以下值。这是否意味着我将AppHFLASH BASEXY地址从0x9900MAMP改为（0x9FC00 500 +0x3000）？我该怎么办？那么，在步骤5中，我应该如何为我的应用程序做EBASE值呢？Bootloader Stuly.CONFIG.H.*定义APPYFLASH BaseX地址（0x9d00），定义应用程序开始执行*//*规则的AppHyFLASH Endox地址（0x9dMAM+0x8000 - 1）/*地址：将APPYFLASH BASEXY地址设置为应用程序链接器脚本*/y*定义的AppReStayADDR值TyAdvor（AppMyFraseBaseX地址）定义了BooTouleSerialPixy定义BTLYwitter BSPwitwits3，定义BooLoad Server Flash OrthPrigelyAddioOrthyApHelpHyMulnEnv.PDF.这部分描述了将用户应用程序放入所需程序闪存区域的过程。必须确保用户应用程序的内存区域与为引导加载程序保留的内存区域不重叠。MHC生成的引导加载程序应被视为您的产品引导程序的起点。因此，添加新的特性可能会导致引导加载程序超过引导加载程序链接器脚本中所需的大小。此外，在Apps/Bootloader /Basic文件夹中提供的引导加载程序被配置为-O1编译器优化。它不是Bootloader的最小可能大小，打开O-ORMIPs16/MyMIPS代码选项将减少引导加载程序的大小。如果引导加载程序的大小发生变化，则应执行以下步骤来调整引导加载程序和应用程序，以便使两者都适合并充分利用设备内存。1。为引导加载程序在程序Flash中确定新的结束地址。这可以通过使用MPLAB XIDE生成的.map文件和相应的编译器，或者使用MPLAB X IDE。2的ELFVIEWER插件来完成。把地址转到最近的页面边界。对于具有1K页面大小的设备，地址必须在0x400边界上结束。对于具有4K页面大小的设备，地址必须在0x1000边界上结束。3。在Bootloader中，更改以下文件：在PIC32 MX设备的BTXYMX.LD中，将KSeG0x程序Mem的长度更改为PIC32 C设备的BTLYCZ.LD中的新边界，将闪存区域长度值更改为新边界。在StasySCOFIG.h中，更改APPYFLASH BASEXY地址的值，以匹配预先确定的虚拟地址。在应用程序中，更改链接器脚本AppYMX.LD如下：将更改的AbaseX地址更改为新的边界，再加上足够的页以获得在4K（0x1000）边界上的地址开始的异常。这是为了将其对齐在MIPS核心所需的边界上。新的边界预先确定：将KSG00SUPLE程序MEM的起始值更改为新边界。重新编译Bootloader和应用程序以及测试操作。



      以下为原文

    I am in the process of trying to get the HARMony bootloader to load my other application. I am using

Product Version: MPLAB X IDE v4.15
Java: 1.8.0_144; Java HotSpot(TM) 64-Bit Server VM 25.144-b01
Runtime: Java(TM) SE Runtime Environment 1.8.0_144-b01
System: Windows 10 version 10.0 running on amd64; Cp1252; en_US (mplab)
And Harmony version v2_05_01

I am running this with PIC32MX795F512L PIM on Explorer16 Board
I have generated the bootloader using harmony.

I am using a GPIO Switch (Switch 3) pin to detect the bootloader change and LED is flashing telling me that I am in the bootloader and all is well here.

The generated btl_mx.ld file has the following values

_RESET_ADDR = 0xBFC00000;
_BEV_EXCPT_ADDR = (0xBFC00000 + 0x380);
_DBG_EXCPT_ADDR = (0xBFC00000 + 0x480);
_DBG_CODE_ADDR = 0xBFC02000;
_DBG_CODE_SIZE = 0xFF0;
_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 = 0x9FC00500, LENGTH = 0x2AF0 /* All C Files will be located here */
kseg0_boot_mem : ORIGIN = 0x9FC00020, LENGTH = 0x0 /* This memory region is dummy */
exception_mem : ORIGIN = 0x9FC01000, LENGTH = 0x1000 /* Interrupt vector table */
config3 : ORIGIN = 0xBFC02FF0, LENGTH = 0x4
config2 : ORIGIN = 0xBFC02FF4, LENGTH = 0x4
config1 : ORIGIN = 0xBFC02FF8, LENGTH = 0x4
config0 : ORIGIN = 0xBFC02FFC, LENGTH = 0x4
kseg1_boot_mem : ORIGIN = 0xBFC00000, LENGTH = 0x300 /* C Startup code */
kseg1_data_mem (w!x) : ORIGIN = 0xA0000000, LENGTH = 0x20000
sfrs : ORIGIN = 0xBF800000, LENGTH = 0x100000
debug_exec_mem : ORIGIN = 0xBFC02000, LENGTH = 0xFF0
configsfrs : ORIGIN = 0xBFC02FF0, LENGTH = 0x10
}

Now I am going through the instructions found in harmony_help_volumne_V.pdf file(Below).
So from Step 3 below, this it seems that I need to change the LENGTH = 0x2AF0 ->0x3000 above for kseg0_program_mem
But in step 4) I am really confused. The bootloader system_config.h (below) has the following value for APP_FLASH_BASE_ADDRESS (0x9D000000).
Does this mean that I change APP_FLASH_BASE_ADDRESS from 0x9D000000 to (0x9FC00500+0x3000)? What should I do here?
Then what should I do for my Applications _ebase value in step 5?



bootloader system_config.h
#define APP_FLASH_BASE_ADDRESS (0x9D000000)

#define APP_FLASH_END_ADDRESS (0x9D000000 + 0x80000 - 1)
/* Address of the Flash from where the application starts executing */
/* Rule: Set APP_FLASH_BASE_ADDRESS to _RESET_ADDR value of application linker script*/
#define APP_RESET_ADDRESS (APP_FLASH_BASE_ADDRESS)
#define BOOTLOADER_LEGACY
#define BTL_SWITCH BSP_SWITCH_3
#define BOOTLOADER_FLASH_TRIGGER_ADDRESS 0

harmony_help_volumne_V.pdf

This section describes the procedure to place a user application into a desired program Flash memory region. It must be ensured that the user
application’s memory region does not overlap with the memory region reserved for the Bootloader.
The Bootloader generated by MHC should be considered a starting point for your product’s Bootloader. As such, adding new features may cause
the Bootloader to exceed the size intended in the Bootloader linker script. In addition, the Bootloaders provided in the apps/bootloader/basic
folder are configured to the –O1 compiler optimization. It is not the smallest possible size for the Bootloader, and turning on the –Os or
MIPS16/microMIPS code options will reduce the size of the Bootloader.
If the size of the Bootloader changes, the following steps should be performed to adjust both the Bootloader and the application in order to make
sure that both fit and make best use of the device memory.
1. Determine the new ending address in Program Flash for the Bootloader. This can be done by using either the .map file generated by MPLAB X
IDE with the respective Compiler, or by using the ELFViewer plug-in for MPLAB X IDE.
2. Round the address up to the nearest page boundary. For devices with 1K page sizes, the address must end on a 0x400 boundary. For devices
with 4K page sizes, the address must end on a 0x1000 boundary.
3. Within the Bootloader, change the following files:
• In btx_mx.ld for PIC32MX devices, change the length of kseg0_program_mem to the new boundary
• in btl_cz.ld for PIC32 C devices, change the Flash memory region LENGTH value to the new boundary
4. In system_config.h, change the value for APP_FLASH_BASE_ADDRESS to match the virtual address determined previously
5. Within the application, change the linker script, app_mx.ld, as follows:
• Change _ebase_address to the new boundary, plus enough pages to get the exceptions to start at an address on a 4K (0x1000) boundary.
This is to align it on the boundary required by the MIPS core.
• Change _RESET_ADDR to the new boundary previously determined
• Change the ORIGIN value for kseg0_program_mem to the new boundary
6. Recompile both the Bootloader and the application, as well as test operations.