@@ -65,13 +65,14 @@ This table summarizes the STM32Cube versions currently used in Mbed OS master br
65
65
| F1 | 1.8.0 | https://github.com/STMicroelectronics/STM32CubeF1 |
66
66
| F2 | 1.6.0 | https://github.com/STMicroelectronics/STM32CubeF2 |
67
67
| F3 | 1.9.0 | https://github.com/STMicroelectronics/STM32CubeF3 |
68
- | F4 | 1.19 .0 | https://github.com/STMicroelectronics/STM32CubeF4 |
68
+ | F4 | 1.25 .0 | https://github.com/STMicroelectronics/STM32CubeF4 |
69
69
| F7 | 1.16.0 | https://github.com/STMicroelectronics/STM32CubeF7 |
70
70
| G0 | 1.3.0 | https://github.com/STMicroelectronics/STM32CubeG0 |
71
+ | G4 | 1.1.0 | https://github.com/STMicroelectronics/STM32CubeG4 |
71
72
| H7 | 1.7.0 | https://github.com/STMicroelectronics/STM32CubeH7 |
72
73
| L0 | 1.10.0 | https://github.com/STMicroelectronics/STM32CubeL0 |
73
74
| L1 | 1.8.1 | https://github.com/STMicroelectronics/STM32CubeL1 |
74
- | L4 | 1.11 .0 | https://github.com/STMicroelectronics/STM32CubeL4 |
75
+ | L4 | 1.14 .0 | https://github.com/STMicroelectronics/STM32CubeL4 |
75
76
| L5 | 1.1.0 | https://github.com/STMicroelectronics/STM32CubeL5 |
76
77
| WB | 1.7.0 | https://github.com/STMicroelectronics/STM32CubeWB |
77
78
@@ -269,6 +270,42 @@ $ mv STM32H745ZITx TARGET_H745ZI_BOARD
269
270
270
271
## ST specific implementation
271
272
273
+ ### Pin configuration
274
+
275
+ It can be useful to have a look on files that describes pin configuration for your board:
276
+ - targets/TARGET_STM/TARGET_STM32** XX** /TARGET_STM32** XXXXX** /TARGET_ ** XXXXX** /PeripheralPins.c
277
+ - targets/TARGET_STM/TARGET_STM32** XX** /TARGET_STM32** XXXXX** /TARGET_ ** XXXXX** /PinNames.h
278
+
279
+ #### Alternate feature
280
+
281
+ You can easily see the alternate functions for each pin.
282
+
283
+ Ex:
284
+ ```
285
+ {PC_10, UART_3, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART3)},
286
+ {PC_10_ALT0, UART_4, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF5_UART4)},
287
+ ```
288
+ - If your application is using PC_10 pin for UART, drivers will configure UART3 instance.
289
+ - If your application is using PC_10_ALT0 pin for UART, drivers will configure UART4 instance.
290
+
291
+ The same alternate choice feature is also used for PWM, ADC, SPI, etc...
292
+
293
+ #### Conflict pins
294
+
295
+ Sometimes there are some conflicts in pin use.
296
+
297
+ Ex:
298
+ ```
299
+ {PA_5, SPI_1, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_NOPULL, GPIO_AF5_SPI1)}, // Connected to LD2 [green led]
300
+ ```
301
+ ==> You can use PA_5 pin as SPI, ** only** if your application is not using LED...
302
+
303
+ Sometimes, pin is explicitly removed by default to avoid issues (but you can uncomment the line for your custom board)
304
+ ```
305
+ // {PB_4, UART_2, STM_PIN_DATA(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF7_USART2)}, // Connected to same instance as STDIO
306
+ ```
307
+
308
+
272
309
### WiFi configuration
273
310
274
311
https://github.com/ARMmbed/wifi-ism43362
@@ -303,6 +340,8 @@ you then have to add **USE_USER_DEFINED_HAL_ETH_MSPINIT** macro.
303
340
304
341
https://os.mbed.com/teams/ST/wiki/
305
342
343
+ https://os.mbed.com/teams/ST/wiki/STDIO
344
+
306
345
https://os.mbed.com/teams/ST/wiki/How-to-enable-flash-dual-bank
307
346
308
347
https://os.mbed.com/teams/ST/wiki/Nucleo-144pins-ethernet-spi-conflict
0 commit comments