Значение оперативной памяти потеряно после сброса сторожевого таймера в контроллере SAMC21N18A
Я использую контроллер SAMC21N18A, и я столкнулся с проблемой потери содержимого ОЗУ после сброса сторожевого таймера. Я использую сценарий компоновщика контроллера SAMC21N18A с небольшой модификацией в области ПЗУ с командой "xc32-ld -T LinkerScript.ld" в mplab ide. Я загружаю здесь свой сценарий компоновщика, может ли кто-нибудь сказать мне, что нужно добавить в scirpt компоновщика, чтобы местоположение оперативной памяти не потеряло значения после сброса сторожевого таймера. Еще один момент: "если я не добавляю свой scirpt компоновщика с помощью"-T LinkerScript.ld", то расположение оперативной памяти не теряет своего значения (сценарий компоновщика по умолчанию, учитывая, что мой mplab работает нормально). Ide - компилятор mplab 5.30 - контроллер xc32 - samc21n18a
Сценарий компоновщика:
OUTPUT_FORMAT("elf32-littlearm", "elf32-littlearm", "elf32-littlearm")
OUTPUT_ARCH(arm)
SEARCH_DIR(.)
/*
* Define the __XC32_RESET_HANDLER_NAME macro on the command line when you
* want to use a different name for the Reset Handler function.
*/
#ifndef __XC32_RESET_HANDLER_NAME
#define __XC32_RESET_HANDLER_NAME Reset_Handler
#endif /* __XC32_RESET_HANDLER_NAME */
/* Set the entry point in the ELF file. Once the entry point is in the ELF
* file, you can then use the --write-sla option to xc32-bin2hex to place
* the address into the hex file using the SLA field (RECTYPE 5). This hex
* record may be useful for a bootloader that needs to determine the entry
* point to the application.
*/
ENTRY(__XC32_RESET_HANDLER_NAME)
/*************************************************************************
* Memory-Region Macro Definitions
* The XC32 linker preprocesses linker scripts. You may define these
* macros in the MPLAB X project properties or on the command line when
* calling the linker via the xc32-gcc shell.
*************************************************************************/
#ifndef ROM_ORIGIN
# define ROM_ORIGIN 0x0
#endif
#ifndef ROM_LENGTH
# define ROM_LENGTH 0x40000
#elif (ROM_LENGTH > 0x40000)
# error ROM_LENGTH is greater than the max size of 0x40000
#endif
#ifndef RAM_ORIGIN
# define RAM_ORIGIN 0x20000000
#endif
#ifndef RAM_LENGTH
# define RAM_LENGTH 0x8000
#elif (RAM_LENGTH > 0x8000)
# error RAM_LENGTH is greater than the max size of 0x8000
#endif
/*************************************************************************
* Memory-Region Definitions
* The MEMORY command describes the location and size of blocks of memory
* on the target device. The command below uses the macros defined above.
*************************************************************************/
MEMORY
{
rom (LRX) : ORIGIN = ROM_ORIGIN, LENGTH = ROM_LENGTH
ram (WX!R) : ORIGIN = RAM_ORIGIN, LENGTH = RAM_LENGTH
config_00804000 : ORIGIN = 0x00804000, LENGTH = 0x4
config_00804004 : ORIGIN = 0x00804004, LENGTH = 0x4
}
/*************************************************************************
* Output region definitions.
* CODE_REGION defines the output region for .text/.rodata.
* DATA_REGION defines the output region for .data/.bss
* VECTOR_REGION defines the output region for .vectors.
*
* CODE_REGION defaults to 'rom', if rom is present (non-zero length),
* and 'ram' otherwise.
* DATA_REGION defaults to 'ram', which must be present.
* VECTOR_REGION defaults to CODE_REGION, unless 'boot_rom' is present.
*/
#ifndef CODE_REGION
# if ROM_LENGTH > 0
# define CODE_REGION rom
# else
# define CODE_REGION ram
# endif
#endif
#ifndef DATA_REGION
# define DATA_REGION ram
#endif
#ifndef VECTOR_REGION
# define VECTOR_REGION CODE_REGION
#endif
__rom_end = ORIGIN(rom) + LENGTH(rom);
__ram_end = ORIGIN(ram) + LENGTH(ram);
/*************************************************************************
* Section Definitions - Map input sections to output sections
*************************************************************************/
SECTIONS
{
.config_00804000 : {
KEEP(*(.config_00804000))
} > config_00804000
.config_00804004 : {
KEEP(*(.config_00804004))
} > config_00804004
/*
* The linker moves the .vectors section into itcm when itcm is
* enabled via the -mitcm option, but only when this .vectors output
* section exists in the linker script.
*/
.vectors :
{
. = ALIGN(4);
_sfixed = .;
KEEP(*(.vectors .vectors.* .vectors_default .vectors_default.*))
KEEP(*(.isr_vector))
KEEP(*(.reset*))
KEEP(*(.after_vectors))
} > VECTOR_REGION
/*
* Code Sections - Note that standard input sections such as
* *(.text), *(.text.*), *(.rodata), & *(.rodata.*)
* are not mapped here. The best-fit allocator locates them,
* so that input sections may flow around absolute sections
* as needed.
*/
.text :
{
. = ALIGN(4);
*(.glue_7t) *(.glue_7)
*(.gnu.linkonce.r.*)
*(.ARM.extab* .gnu.linkonce.armextab.*)
/* Support C constructors, and C destructors in both user code
and the C library. This also provides support for C++ code. */
. = ALIGN(4);
KEEP(*(.init))
. = ALIGN(4);
__preinit_array_start = .;
KEEP (*(.preinit_array))
__preinit_array_end = .;
. = ALIGN(4);
__init_array_start = .;
KEEP (*(SORT(.init_array.*)))
KEEP (*(.init_array))
__init_array_end = .;
. = ALIGN(0x4);
KEEP (*crtbegin.o(.ctors))
KEEP (*(EXCLUDE_FILE (*crtend.o) .ctors))
KEEP (*(SORT(.ctors.*)))
KEEP (*crtend.o(.ctors))
. = ALIGN(4);
KEEP(*(.fini))
. = ALIGN(4);
__fini_array_start = .;
KEEP (*(.fini_array))
KEEP (*(SORT(.fini_array.*)))
__fini_array_end = .;
KEEP (*crtbegin.o(.dtors))
KEEP (*(EXCLUDE_FILE (*crtend.o) .dtors))
KEEP (*(SORT(.dtors.*)))
KEEP (*crtend.o(.dtors))
. = ALIGN(4);
_efixed = .; /* End of text section */
} > CODE_REGION
/* .ARM.exidx is sorted, so has to go in its own output section. */
PROVIDE_HIDDEN (__exidx_start = .);
.ARM.exidx :
{
*(.ARM.exidx* .gnu.linkonce.armexidx.*)
} > CODE_REGION
PROVIDE_HIDDEN (__exidx_end = .);
. = ALIGN(4);
_etext = .;
/*
* Align here to ensure that the .bss section occupies space up to
* _end. Align after .bss to ensure correct alignment even if the
* .bss section disappears because there are no input sections.
*
* Note that input sections named .bss* are no longer mapped here.
* The best-fit allocator locates them, so that they may flow
* around absolute sections as needed.
*/
.bss (NOLOAD) :
{
. = ALIGN(4);
__bss_start__ = .;
_sbss = . ;
_szero = .;
*(COMMON)
. = ALIGN(4);
__bss_end__ = .;
_ebss = . ;
_ezero = .;
} > DATA_REGION
. = ALIGN(4);
_end = . ;
_ram_end_ = ORIGIN(ram) + LENGTH(ram) -1 ;
}