内存映射的 gcc 链接文件，那是什么语法？

发布于 2024-11-09 04:04:05 字数 870 浏览 5 评论 0原文

当使用 gcc 为 MCU 进行交叉编译时，您向链接器提供链接器脚本文件，以便它知道如何创建最终的目标文件。

我想了解有关此类文件的更多信息，但找不到关于这些文件如何工作、它们使用哪种语法、最佳实践是什么以及应避免什么的好教程。

下面是一个精简链接文件的示例，该文件将通过“-Tlinkfile.ld”选项提供给链接器：

MEMORY
{
    ram    (rwx) : ORIGIN = 0x20000000, LENGTH = 20k
    rom    (rx)  : ORIGIN = 0x00000000, LENGTH = 128K
}
SECTIONS
{
    .  = 0x0;           /* From 0x00000000 */
    .text : 
    {
        *(.nvic_vector)  /* Vector table */
        *(.text.*)      /* Program code */
        *(.text)        /* Program code */
        *(.rodata)      /* Read only data */
    } >rom

    .  = 0x20000000;    /* From 0x20000000 */      
    .data : 
    {
        *(.data)        /* Data memory */
    } >ram AT > rom

    .bss : 
    {
        *(.bss)         /* Zero-filled run time allocate data memory */
    } >ram AT > rom
}

/Thanks

原文

When using gcc to cross-compile for an MCU you provide a linker script file to the linker so it knows how to create the final object file.

I would like to learn more about this type of file, but can't find a nice tutorial on how these files work, what kind of syntax they use, what are best practices, and what to avoid.

Here's an example of a stripped-down link file that would be provided to the linker with the "-Tlinkfile.ld" option:

MEMORY
{
    ram    (rwx) : ORIGIN = 0x20000000, LENGTH = 20k
    rom    (rx)  : ORIGIN = 0x00000000, LENGTH = 128K
}
SECTIONS
{
    .  = 0x0;           /* From 0x00000000 */
    .text : 
    {
        *(.nvic_vector)  /* Vector table */
        *(.text.*)      /* Program code */
        *(.text)        /* Program code */
        *(.rodata)      /* Read only data */
    } >rom

    .  = 0x20000000;    /* From 0x20000000 */      
    .data : 
    {
        *(.data)        /* Data memory */
    } >ram AT > rom

    .bss : 
    {
        *(.bss)         /* Zero-filled run time allocate data memory */
    } >ram AT > rom
}

/Thanks

分享到QQ

分享到微博