1.1 GDB server start-up options
--ext-memory-loaders
Provides the list of the available external memory loaders.
-el <file_path>, --extload <file_path>
Selects a custom external memory-loader.
--external-init
Runs Init() from external memory loader after reset to make external memory accessible without need for
application software to set up the access to memory-mapped external memory.
[This option requires that option -el <file_path>, --extload <file_path> is used also.]
2.3.1 Loading program to external memory
When a program must be loaded to an external memory, the option --extload <file_path> must be used.
External memory loader files are delivered for most available STM32 Evaluation and Discovery boards containing
external memory. To list the available loader files, use the --ext-memory-loaders option.
The STM32CubeProgrammer software description user manual (UM2237) contains detailed information on how
to use external Flash loader programs and develop customized loaders for external memory. The user manual is
available from the STM32CubeProg webpage on www.st.com.
2.3.2 Memory read/write to external memory
To make external memory accessible for read and write by the debugger, use the --external-init option
together with external memory loader --extload <file_path> option. When --external-init is used the
Init() function in the external memory loader is run by the ST-LINK GDB server after reset. This makes
external memory accessible without any need for application software to set up the device for external memory
access. The external memory must be memory mapped and directly accessed because normal memory read/
write is used by gdb.
Note: When using the --external-init option with the ST-LINK GDB server, the stack required by the Init()
function is limited to 1024 bytes of stack instead of 400 bytes in ST-LINK GDB server v5.4.0. |
[링크 : https://www.st.com/resource/en/user_manual/dm00613038-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf]
