CCS6.2 编译出现 error #10099-D: program will not fit into available memory. 使用哪种类型定义的变量会占用.ebss空间

最新推荐文章于 2025-01-08 13:56:10 发布

爱代码的小黄人

最新推荐文章于 2025-01-08 13:56:10 发布

阅读量1.9w

点赞数 33

分类专栏： C语言学习文章标签： c语言 c++

本文链接：https://blog.youkuaiyun.com/weixin_44114030/article/details/119925302

版权

C语言学习专栏收录该内容

3 篇文章

订阅专栏

ebss段主要是存放全局变量。cinit段存放全局变量和静态变量的初始化代码。可以通过查看map文件来确定其具体的长度。ebss段放的是数据，需要分配在RAM中。cinit段放的是代码，可以分配在Flash中。两者是两块独立的存储单元，ebss段无法占用cinit的存储空间。

出现这样的报错：

“…/28335_RAM_lnk.cmd”, line 138: error #10099-D: program will not fit into available memory, or the section contains a call site that requires a trampoline that can’t be generated for this section. run placement with alignment/blocking fails for section “.ebss” size 0x1058 page 1. Available memory ranges:
RAML4 size: 0x1000 unused: 0x1000 max hole: 0x1000

我们知道 .ebss只是预先为全局变量或静态变量预留空间，然后在程序开始前会对其进行初始化，我想知道的是.ebss预留空间的信息存放在DSP的哪里，比如我为.ebss预留了0x1000的空间，DSP是把这个预留空间的相关信息保存在哪里，上电后它怎么知道当前要为全局变量或静态变量留出0x1000的空间？

答：你可以在CMD文件中为ebss段分配指定的地址空间，比如RAML1或者RAML2。CCS在编译时会在该地址空间为其分配所需要大小的存储区域。如果该地址空间不足以分配其需求，CCS就会报错，如果有富余，那么它只占用它所需要的空间。

在编译后生成的.map文件中记录有为各个section分配的起始地址和地址范围的信息

有可能是因为RAMLS和RAMGS不够，所以编译器自动将其分到了ebss。

您可以在CCS内使用View–>Memory Allocation 来查看内存使用情况
在这里插入图片描述
所以定义数组变量时，不能定义太多的变量，不然内存就会不够/(ㄒoㄒ)/~~

TI官网给出的解释：
Typical message
“./lnk.cmd”, line 48: error #10099-D: program will not fit into available
memory. placement with alignment fails for section “.text” size 0x2b12 .
Available memory ranges:
FLASH size: 0x1000 unused: 0xe56 max hole: 0xe56
What it means
The linker was unable to fit some portion of the program onto the device. The specific error message indicates what section of the program the linker failed to place, its size, and the memory range it tried to place it in. For the memory ranges listed, the size indicates the total size of the section, unused represents the amount of space remaining when trying to place the section that failed and max hole represents the largest contiguous region available.
机翻：链接器无法将程序的某些部分安装到设备上。具体的错误信息指出了链接器未能放置程序的哪个段，它的大小，以及它试图将它放入的内存范围。对于列出的内存范围，大小表示该段的总大小，未使用表示数量尝试放置失败的部分时剩余的空间，最大孔表示可用的最大连续区域。
Why is it happening
Fundamentally, this indicates that the device has insufficient physical memory (read-only or read-write) to handle the program. However, this doesn’t necessarily mean that a larger device is required. There are several things that can be changed that could resolve the problem. Also, for advanced users this error could also come from an incorrect linker command file that doesn’t accurately represent the current device. (TI devices normally come with an appropriate linker command file and don’t require user modification, so if you don’t know anything about the linker command file you shouldn’t worry about this possibility.)
机翻：从根本上说，这表明设备没有足够的物理内存（只读或读写）来处理程序。但是，这并不一定意味着需要更大的设备。有几个可以改变的东西可以解决这个问题。此外，对于高级用户，此错误也可能来自不正确的链接器命令文件，该文件不能准确代表当前设备。（TI 器件通常带有适当的链接器命令文件，不需要用户修改，因此如果您对链接器命令文件一无所知，则不必担心这种可能性。）
Remedy
This error message can occur for several reasons so there are multiple possible solutions. A few common issues to consider:
出现此错误消息的原因有多种，因此有多种可能的解决方案。需要考虑的几个常见问题：
If a section failed to place to RAM make sure that the stack and heap sizes are set appropriately for the device and your program. Consider reducing them.
如果某个部分未能放入 RAM，请确保为设备和您的程序正确设置了堆栈和堆大小。考虑减少它们。
Try enabling or increasing the optimization level used by the compiler. Unoptimized programs require far more space than optimized ones.
If you have added I/O code for debugging purposes this can be larger than expected. Specifically, printf() will not fit on many small embedded devices. Depending on the size of the device, the --printf_support=minimal option may solve the problem or printf() may not be a viable means of debugging at all.
尝试启用或提高编译器使用的优化级别。未优化的程序比优化的程序需要更多的空间。
如果您为了调试目的添加了 I/O 代码，这可能比预期的要大。具体来说， printf() 不适用于许多小型嵌入式设备。根据设备的大小，–printf_support=minimal 选项可能会解决问题，或者 printf() 可能根本不是一种可行的调试方法。
If the above suggestions don’t resolve the issue then more investigation will be required to determine if the issue is simply that the device is not large enough for the program or if space is being used unnecessarily. The best place to find more information is the map file generated by the linker. The map file provides detailed information on where sections are placed, what they consist of and how large they are. When looking at this please keep in mind that the section that failed to place is not necessarily the source of the problem. Another section previously placed in the same memory region could have been much larger than expected and introduced the issue.
如果上述建议不能解决问题，则需要进行更多调查以确定问题是否仅仅是设备对程序来说不够大，或者是否使用了不必要的空间。查找更多信息的最佳位置是链接器生成的映射文件。地图文件提供有关部分放置位置、它们的组成以及它们的大小的详细信息。在查看此内容时，请记住，未能放置的部分不一定是问题的根源。之前放置在同一内存区域中的另一部分可能比预期大得多，并引入了该问题。
参考链接：