Setup — Preparing the STM32F7XX-EVAL Board for eCos Development
Typically, since the STM32F7XX-EVAL motherboard has a built-in ST-LINK/V2 interface providing hardware debug support, eCos applications are loaded and run via the debugger arm-eabi-gdb or via the Eclipse IDE. The debugger then communicates with the “GDB server” provided by the relevant host ST-LINK/V2 support tool being used (e.g. OpenOCD).
Normally for release applications the
type would be used, with the application programmed into the on-chip
flash for execution when the board boots. It is still possible to use
the hardware debugging support to debug such flash-based ROM
applications, and this may be the desired approach if the application
is too large for execution from on-chip SRAM, or where all of the SRAM
and SDRAM is required for application run-time use.
If off-chip non-volatile memory (NVM) is used to hold the main application then the board can boot from the internal flash using the BootUP ROM loader. This BootUp code will then start the main application (after an optional update sequence).
If required, it is still possible to program a GDB stub or
ROM image into on-chip Flash and download
and debug via the serial UART (CN8). In that case, eCos applications
are configured for
RAM startup and then downloaded
and run on the board via the debugger arm-eabi-gdb,
or via the Eclipse IDE. By default for serial communications, all
versions run with 8 bits, no parity, and 1 stop bit at 115200
baud. This rate can be changed in the eCos configuration used for
Programming ROM images
Since the STM32F7XX-EVAL board has a built-in ST-LINK/V2 SWD interface, the micro USB host connection (CN21) and suitable host software (e.g. The OpenOCD package openocd tool) can be used to program the flash.
The openocd GDB server can directly program flash based applications from the GDB load command.
The openocd command being used should have been configured and built to support the ST-LINK/V2 interface. This is achieved by specifying the --enable-stlink when configuring the OpenOCD build. Additional information on running openocd may be found in the OpenOCD notes.
For example, assuming that openocd is running on the same host as GDB, and is connected to the target board the following will program the “bootup.elf” application into the on-chip flash:
arm-eabi-gdb install/bin/bootup.elfGNU gdb (eCosCentric GNU tools 4.7.3c) 7.6.1 [ … GDB output elided … ] (gdb) target remote localhost:3333 hal_reset_vsr () at
loadLoading section .rom_vectors, size 0x14 lma 0x8000000 Loading section .text, size 0x3adc lma 0x8000018 Loading section .rodata, size 0x6c0 lma 0x8003af8 Loading section .data, size 0x6dc lma 0x80041b8 Start address 0x8000018, load size 18572 Transfer rate: 14 KB/sec, 4643 bytes/write. (gdb)
Alternatively, the openocd telnet interface can be
used to manually program the flash. By default
the openocd session provides a command-line via
4444. Consult the OpenOCD documentation for
more details if a non-default openocd configuration
is being used.
With a telnet connection established to the openocd any binary data can easily be written to the on-chip flash. e.g.
telnet localhost 4444Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger >
flash write_image test.bin 0x08000000wrote 32518 bytes from file test.bin in 1.073942s (29.569 KiB/s)
To create a binary for flash programming the arm-eabi-objcopy command is used. This converts the, ELF format, linked application into a raw binary. For example:
arm-eabi-objcopy -O binary
|2022-03-29||eCosPro Non-Commercial Public License|