在MPFS2文件之前预留内存空间的最佳方法是什么？

我不知道这是否会有帮助，但是这里是我管理这个的方法。在MPFSIMIMG2.C中，我在Link中转换文件，然后在HEX文件中导出。我的Bootloader使用这个地址范围来加载SST26。顺便说一下，如果我想使用XIP，这些地址映射到相同的SQI空间。



      以下为原文

    I don't know if this will help, but here is how I am managing this.
 
In mpfs_img2.c I change
const uint8_t __attribute__((section ("flash_mem.media_data"),space(prog))) NVM_MEDIA_DATA[DRV_NVM_MEDIA_SIZE*1024] = {
 
In the linker
MEMORY
{
    kseg1_boot_mem : ORIGIN = 0x9D000000, LENGTH = 0x480
    kseg0_program_mem (rx) : ORIGIN = 0x9D000000 + 0x480, LENGTH = 0x200000 - 0x480 /* All C files will be located here */
    kseg0_boot_mem : ORIGIN = 0x9D000000, LENGTH = 0x0
  kseg0_data_mem (w!x) : ORIGIN = 0x80000000, LENGTH = 0xa0000
  sfrs : ORIGIN = 0xBF800000, LENGTH = 0x100000
  kseg2_ebi_data_mem : ORIGIN = 0xC0000000, LENGTH = 0x4000000
  kseg2_sqi_data_mem : ORIGIN = 0xD0000000, LENGTH = 0x4000000
  kseg3_ebi_data_mem : ORIGIN = 0xE0000000, LENGTH = 0x4000000
  kseg3_sqi_data_mem : ORIGIN = 0xF0000000, LENGTH = 0x4000000
  flash_mem (ra) : ORIGIN = 0xF0000000, LENGTH = 0x200000
}

/*************************************************************************
 * Configuration-word sections. Map the config-pragma input sections to
 * absolute-address output sections.
 *************************************************************************/
SECTIONS
{
  .flash_mem :
  {
    KEEP(*(flash_mem.media_data))
 KEEP(*(flash_mem))
  } >flash_mem
  /* Boot Sections */
  .reset _RESET_ADDR :
  {
 
Then the files get exported in the hex file.  My bootloader uses that address range to load the SST26.  Incidentally, those addresses map to the same SQI space if I ever want to use XIP.

我不明白：你的链接器和外部闪存之间的关系是什么？=外部闪存使用MPFSXIMG2.BIN，而不是MPFSXIMG2.C.I不知道我需要干预哪一个和谐层来引入偏移。我认为：对于文件系统服务库地址0x90000必须对应于我的偏移地址：文件系统服务库不能允许访问R。备用内存区。对于MPFS库，它是一样的。但是我不知道对于文件系统媒体管理器，地址0x00亿必须对应于我的偏移地址或地址0x90000在SST26闪存中。



      以下为原文

    I don't understand : what is the relationship between your linker and an external flash ?
=> external flash use mpfs_img2.bin and not mpfs_img2.c.
 
I do not know which Harmony layer I need to intervene to introduce the offset.
I think :
- For File System Service library address 0x00000000 must be correspond to my offset address : File System Service library must not allow access to the reserved memory zone. For MPFS library, it is the same thing.
=> Am I right ?
=> But I don't know if for File System Media Manager, address 0x00000000 must to correspond to my offset address or address 0x00000000 in SST26 flash memory
 

在我的例子中，我想让链接器分配并将对象放置在外部内存中，所以我用这种方式在C文件中使用数组。这样，我的引导装载器处理一个十六进制文件。MPFS层是完全相同的。你可以做你想要的与和声修改。在DrviStx26In初始化中，您必须将BosikStestRoad更改为基地址，我想。我可能会在SysCyf.g中创建一个定义来完成这个操作。



      以下为原文

    The relationship in my case is that I want to have the linker allocate and place objects in external memory, so I am using it this way with the array in a C file.  That way my bootloader handles one hex file.  The MPFS layer is exactly the same though.
 
You can do what you want with a harmony modification.  In DRV_SST26_Initialize
    dObj->blockStartAddress = 0;
You'll have to change the blockStartAddress to your base address, I think. I'd probably create a define in my SystemConfig.h to do this.

程序在MPFS中修改了“GSIMPsfsObj.BaseAdvices”。C文件系统Media Manager库可以访问Flash的所有地址。-文件系统服务库和MPFS2库只能访问非保留的内存地址：地址0x000点到偏移量。为了我



      以下为原文

    Programm operate with my modification of "gSysMpfsObj.baseAddress" in mpfs.c
- File System Media Manager Library can access  to all address of the flash.
- File System Service library and MPFS2 Library can access only to non-reserved memory address : Address 0x0000 point to the offset.
=> It is good for me