使用XC32（1.42）应用程序定义的内存区域

我想在PIC32MX170256B提供的闪存程序空间中定义一个应用程序定义内存区域。在帮助文档中使用MPLAB X IDE v3.45的帮助文档中的XC32工具链的MPLLABXC32C编译器部分中的内存分配和访问下，我使用“应用程序定义内存区域”跟踪文档。代码使用：#pragma区域名称=“Config”origin=0x9D03C000size=0x4000I，我试图更改上面的起源和大小。更改它们不会改变行为。区域中的每个变量都具有以下属性：u.((.("Config"))代码编译和链接良好，没有任何错误或警告。但是，C运行时初始化代码在调用main之前得到一个一般的异常。我有一个真正的冰，并且可以在执行程序时通过汇编程序。代码似乎在引导加载程序内存的某个地方出现故障，但是在没有访问实际汇编程序（或C源代码？）如果我从配置区域变量中删除“.”属性，则运行时C初始化代码执行得很好，调用main。有人成功地使用“.”属性定义CPU提供的程序空间的区域吗？可能是“区域”属性不能应用于CPU提供的程序空间。文档中的描述和示例表明了这一点，而“--.-mem”的使用显示了“Config”区域作为外部存储器。如果是这样，这是如何实现的？我意识到我可能需要编写一个定制的链接器脚本，但是region属性是用更低的支持成本实现相同目标的一种相当优雅的方式。



      以下为原文

    I would like to define an Application Defined Memory Region in the flash program space provided by the PIC32MX170256B. The core idea is to carve out a fixed area of the 256K program space for a factory defined configuration that will (possibly) be later updated by customer defined configuration information.
I followed the doc using "Application Defined Memory Regions" under Memory Allocation and Access in the MPLAB XC32 C Compiler section of the XC32 Toolchain in the Help docs using MPLAB X IDE v3.45.  The code uses:

#pragma region name="Config" origin=0x9D03C000 size=0x4000

I have tried changing the origin above and the size.  Changing them does not change the behavior.

Each of the variables in the region have the following attribute:

__attribute__((region("Config")))

The code compiles and links nicely without errors or warnings of any kind.  However, the C runtime initialization code gets a general exception before main is called.  I have a real-ice and can step through the assembler as it executes.  The code appears to be failing somewhere in the boot loader program memory but it is a bit difficult to deduce what is going on without access to the actual assembler (or C source?).  If I remove the "region" attribute from the configuration area variables the runtime C initialization code executes nicely and main is called.

Has anyone had success using the "region" attribute to define regions of CPU provided program space?  It may be that the "region" attribute cannot be applied to CPU provided program space.  The description and example in the docs suggest this and the use of "--report-mem" shows the "Config" region as external memory.

In summary, Can the "region" attribute be used to define regions of CPU provided program space?  If so, how is this accomplished?  I realize that I may have to write a custom linker script; but the region attribute is a rather elegant way to accomplish the same objective with a much lower support cost.

I would appreciate any insight or suggestions you may have on this topic.