[Epic] - QSPI, OpenOCD, Linker & External flash

[ladislas]

Description

Documentation related to QSPI Flash, OpenOCD & Linker configuration.

The goal is to have OpenOCD flash both the main mcu and the factory QSPI flash during manufacturing.

Docs

QSPI

• https://os.mbed.com/docs/mbed-os/v5.15/apis/quadspi-qspi.html
• https://os.mbed.com/docs/mbed-os/v5.15/mbed-os-api-doxy/classmbed_1_1_q_s_p_i.html
• https://www.st.com/content/ccc/resource/technical/document/application_note/group0/b0/7e/46/a8/5e/c1/48/01/DM00227538/files/DM00227538.pdf/jcr:content/translations/en.DM00227538.pdf
• https://www.st.com/resource/en/application_note/dm00227538-quadspi-interface-quadspi-on-stm32-microcontrollers-stmicroelectronics.pdf - section 4.1

OpenOCD

• https://github.com/glegrain/STM32-with-macOS
• https://github.com/STMicroelectronics/OpenOCD
• https://github.com/STMicroelectronics/OpenOCD/blob/openocd-cubeide-r1/tcl/board/stm32f769i-disco.cfg
• https://sourceforge.net/p/openocd/code/ci/master/tree/

Linker

• http://blog.atollic.com/using-gnu-gcc-on-arm-cortex-devices-placing-code-and-data-on-special-memory-addresses-using-the-gnu-ld-linker
• https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/TARGET_STM32F7/TARGET_STM32F769xI/device/TOOLCHAIN_GCC_ARM/STM32F769xI.ld
• https://github.com/STMicroelectronics/STM32CubeF7/blob/master/Projects/STM32F769I-Discovery/Demonstrations/TouchGFX/SW4STM32/STM32F769I-Discovery/STM32F769NIHx_FLASH.ld
• https://support.touchgfx.com/docs/development/ui-development/scenarios/using-non-memory-mapped-flash/#linking-images-to-ram
• https://ftp.gnu.org/old-gnu/Manuals/ld-2.9.1/html_node/ld_16.html

[ladislas]

We must fork openocd and pull the ST's changes to work with our board before adding our custom board.

QSPI should work as we are using the same pins.

[ladislas]

For general information, the following question was asked there: STMicroelectronics/OpenOCD#1

[ladislas]

Closing as:

This will not be used in the final product.