Difference between revisions of "ST STM32L4"

From SEGGER Wiki
Jump to: navigation, search
(STM32L4Rxxx / STM32L4Sxxx (Q)SPI support)
Line 29: Line 29:
   
 
== STM32L4Rxxx / STM32L4Sxxx (Q)SPI support ==
 
== STM32L4Rxxx / STM32L4Sxxx (Q)SPI support ==
The ST STM32L4Rxxx / STM32L4Sxxx device series comes with a OCTASPI controller which allows memory mapped read accesses to any (Q)SPI flash, connected to the Octa-SPI interface of the MCU. This allows the J-Link DLL to support flash programming through the Octa-SPI interface. Unfortunately, there is no generic way how to implement flash programming because the used pins to connect the SPI flash is not defined. Different pins can be used for the same OCTASPI alternate function and therefore, for each configuration, a slightly different RAMCode (different pin initialization / flash size) is required. We have developed one flash algorithm based on a pin layout of the ST ''STM32L4R9 DISCO'' evaluation board. This flash algorithm can be used to to program any common (Q)SPI flash, connected to the Octa-SPI interface of the ST STM32L4Rxxx / STM32L4Sxxx series device. The flash algorithms are based on the SEGGER ''Open Flash Loader'' concept so they can easily be exchanged if a pin configuration, different from the one used in the example flash algorithms, is required. In such cases, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
+
The ST STM32L4Rxxx / STM32L4Sxxx device series comes with a OCTASPI controller which allows memory mapped read accesses to any (Q)SPI flash, connected to the Octa-SPI interface of the MCU. This allows the J-Link DLL to support flash programming through the Octa-SPI interface. Unfortunately, there is no generic way how to implement flash programming because the used pins to connect the SPI flash is not defined. Different pins can be used for the same OCTASPI alternate function and therefore, for each configuration, a slightly different RAMCode (different pin initialization / flash size) is required. We have developed one flash algorithm based on a pin layout of the ST ''STM32L4R9 DISCO'' evaluation board. This flash algorithm can be used to to program any common (Q)SPI flash, connected to the Octa-SPI interface of the ST STM32L4Rxxx / STM32L4Sxxx series device. The flash algorithms are based on the SEGGER ''Open Flash Loader'' concept so they can easily be exchanged if a pin configuration, different from the one used in the example flash algorithms, is required. For pin configuration, different from the one used in the example flash algorithm, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.
   
 
For further information regarding this as well as the flash algorithms, please refer to the following pages:
 
For further information regarding this as well as the flash algorithms, please refer to the following pages:

Revision as of 09:22, 5 March 2021

Flash Memory

This section is about the flash memory of STM32L4 devices

Determine dual-bank setting

To determine whether dual-bank is set or not, the corresponding bit in the Flash option register (FLASH_OPTR, 0x4002 2020) can be read:

  • For 1MB devices: DB1M (bit-pos 21)
  • For 2MB devices: DBANK (bit-pos 22)

The following lines can be used in the J-Link Commander to read FLASH_OPTR:

r
mem32 0x40022020 1

Dualbank Flash Programming

The ST STM32L4 series devices come with a dual-bank flash memory. The layout of the dual-bank flash memory can be configured by the user through the option byte DUALBANK. By default, the value of this option byte is DUALBANK == 1, which means that the flash is configured as dual bank memory while DUALBANK == 0 means that the flash is configured as single bank memory flash. In dual-bank mode, the flash boot source can be switched between bank 1 or bank 2. In single-bank mode, flash always boots from bank 1. The total flash size is exactly the same for both modes. Another advantage of using DUALBANK is that both banks can be accessed in parallel (e.g. reading bank 1 while programming bank 2).

Problem description

The flash algorithm has to behave differently, depending on the active flash bank mode configuration as the flash controller expects different page indices for the same destination address.

Solution

When using the J-Link flash loader, make sure that the flash controller is configured for dual bank flash layout (DUALBANK == 1), which is the default.

STM32L476xx (Q)SPI support

The ST STM32L476xx device series comes with a QUADSPI controller which allows memory mapped read accesses to any (Q)SPI flash, connected to the Quad-SPI interface of the MCU. This allows the J-Link DLL to support flash programming through the Quad-SPI interface. Unfortunately, there is no generic way how to implement flash programming because the used pins to connect the SPI flash is not defined. Different pins can be used for the same QUADSPI alternate function and therefore, for each configuration, a slightly different RAMCode (different pin initialization / flash size) is required. We have developed two flash algorithms based on a different pin layout. One is based on the ST STM32L476-DISCO evaluation board, the other one is based on the ST STM32L476G Eval board. These flash algorithms can be used to to program any common (Q)SPI flash, connected to the Quad-SPI interface of the ST STM32L476 device. The flash algorithms are based on the SEGGER Open Flash Loader concept so they can easily be exchanged if a pin configuration, different from the one used in the example flash algorithms, is required. In such cases, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.

For further information regarding this as well as the flash algorithms, please refer to the following pages:

STM32L4Rxxx / STM32L4Sxxx (Q)SPI support

The ST STM32L4Rxxx / STM32L4Sxxx device series comes with a OCTASPI controller which allows memory mapped read accesses to any (Q)SPI flash, connected to the Octa-SPI interface of the MCU. This allows the J-Link DLL to support flash programming through the Octa-SPI interface. Unfortunately, there is no generic way how to implement flash programming because the used pins to connect the SPI flash is not defined. Different pins can be used for the same OCTASPI alternate function and therefore, for each configuration, a slightly different RAMCode (different pin initialization / flash size) is required. We have developed one flash algorithm based on a pin layout of the ST STM32L4R9 DISCO evaluation board. This flash algorithm can be used to to program any common (Q)SPI flash, connected to the Octa-SPI interface of the ST STM32L4Rxxx / STM32L4Sxxx series device. The flash algorithms are based on the SEGGER Open Flash Loader concept so they can easily be exchanged if a pin configuration, different from the one used in the example flash algorithms, is required. For pin configuration, different from the one used in the example flash algorithm, please get in touch with SEGGER directly via our support system: https://www.segger.com/ticket/.

For further information regarding this as well as the flash algorithms, please refer to the following pages: