1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
/**
@page QSPI_ExecuteInPlace QSPI execute in place example
@verbatim
******************************************************************************
* @file QSPI/QSPI_ExecuteInPlace/readme.txt
* @author MCD Application Team
* @brief Description of the code execution from QSPI memory example.
******************************************************************************
*
* Copyright (c) 2018 STMicroelectronics. All rights reserved.
*
* This software component is licensed by ST under BSD 3-Clause license,
* the "License"; You may not use this file except in compliance with the
* License. You may obtain a copy of the License at:
* opensource.org/licenses/BSD-3-Clause
*
******************************************************************************
@endverbatim
@par Example Description
How to execute a part of the code from the QSPI memory. To do this,
a section is created where the function is stored.
At the startup, the QSPI memory is erased, then the data are copied from the initialization
section of the flash to the QSPI memory. And finally the QSPI is configured in memory-mapped
mode and the code in executed in a forever loop.
LED1 and LED2 toggle in a forever loop.
LED3 is on as soon as an error is returned by HAL API, and no more LED toggles.
In this example, HCLK is configured at 64 MHz.
QSPI prescaler is set to 2, so QSPI frequency is = HCLK/(QSPI_Prescaler+1) = 64 MHz/(2+1)
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
@note The application need to ensure that the SysTick time base is always set to 1 millisecond
to have correct HAL operation.
@par Keywords
Memory, QSPI, Erase, Write, Execute, Mapped
@par Directory contents
- QSPI/QSPI_ExecuteInPlace/Inc/stm32wbxx_hal_conf.h HAL configuration file
- QSPI/QSPI_ExecuteInPlace/Inc/stm32wbxx_it.h Interrupt handlers header file
- QSPI/QSPI_ExecuteInPlace/Inc/main.h Header for main.c module
- QSPI/QSPI_ExecuteInPlace/Src/stm32wbxx_it.c Interrupt handlers
- QSPI/QSPI_ExecuteInPlace/Src/main.c Main program
- QSPI/QSPI_ExecuteInPlace/Src/system_stm32wbxx.c STM32WBxx system source file
- QSPI/QSPI_ExecuteInPlace/Src/stm32wbxx_hal_msp.c HAL MSP file
@par Hardware and Software environment
- This example runs on STM32WB55xx devices.
- This example has been tested with P-NUCLEO-WB55 board and can be
easily tailored to any other supported device and development board.
- P-NUCLEO-WB55 Set-up :
Tested on memory Micron N25Q064A with following connections
- Connect PA2 to S# (Chip Select)
- Connect PA3 to C (Clock)
- Connect PB9 to DQ0 (Serial Data)
- Connect PB8 to DQ1 (Serial Data)
- Connect PA7 to DQ2 (DQ2)
- Connect PA8 to DQ3 (DQ3)
- Connect NRST to RESET# (Reset)
- A specific region for the QSPI memory has been added in the scatter file
(st32wb55xx_flash_cm4.icf for IAR toolchain, P-NUCLEO-WB55.sct for Keil toolchain)
in order to map functions in this memory
- The debugger does not work when code is executed from QSPI memory.
@par How to use it ?
In order to make the program work, you must do the following :
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
