You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/contributing/target/QuadSPI.md
+33-4Lines changed: 33 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,6 @@ Implementing QSPI enables Mbed OS to communicate with external memories much fas
4
4
5
5
The most common use case is an external memory to use as additional data storage.
6
6
7
-
<spanclass="warnings">**Warning:** We are changing the QSPI HAL API in an upcoming release of Mbed OS. This page documents code that exists on a feature branch of Mbed OS. You can find details on how it may affect you in the [Implementing the QSPI API](#implementing-quadspi) section.</span>
8
-
9
7
### Assumptions
10
8
11
9
#### Defined behavior
@@ -29,6 +27,29 @@ To make sure your platform is ready for the upcoming changes, you need to implem
29
27
30
28
The target needs to define the `qspi_s` structure - target specific QSPI object.
31
29
30
+
The target needs to define the QSPI interface pin names:
31
+
32
+
-`QSPI_FLASHn_XXX` for pins connected to onboard flash memory.
33
+
-`QSPIn_XXX` for pins routed out to external connector.
34
+
35
+
`n` is the interface index, typically `1` if single QSPI interface available.
0 commit comments