riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

cpu/esp32: remove SDK crypto dependency from doc

Browse Source
This commit is contained in:
Gunar Schorcht 2019-08-16 16:01:49 +02:00
parent 5f01d0a88f
commit d55225eb29
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
cpu/esp32/doc.txt
View File

@ -192,7 +192,6 @@ The RIOT-OS for ESP32 SoCs supports the following features at the moment:
The implementation of RIOT-OS for ESP32 SOCs has the following limitations at the moment: The implementation of RIOT-OS for ESP32 SOCs has the following limitations at the moment:
- Only <b>one core</b> (the PRO CPU) is used because RIOT does not support running multiple threads simultaneously. - Only <b>one core</b> (the PRO CPU) is used because RIOT does not support running multiple threads simultaneously.
- RIOT modules <b>crypto</b> and <b>hashes</b> cannot be used together with modules <b>esp_now</b> and <b>esp_wifi</b>
- <b>Bluetooth</b> cannot be used at the moment. - <b>Bluetooth</b> cannot be used at the moment.
- <b>Flash encryption</b> is not yet supported. - <b>Flash encryption</b> is not yet supported.
@ -942,12 +941,9 @@ The board has to have one of the supported PHY modules to be able to use the Eth
The RIOT port for ESP32 implements in module `esp_wifi` a `netdev` driver for The RIOT port for ESP32 implements in module `esp_wifi` a `netdev` driver for
the built-in WiFi interface. the built-in WiFi interface.
@note Due to symbol conflicts with the `crypto` and `hash` modules of RIOT @note Module `esp_wifi` is not enabled automatically when the `netdev_default`
in module `esp_idf_wpa_supplicant_crypto`, which is required by module module is used. Instead, if necessary, the application has to add the
`esp_wifi`, `esp_wifi` cannot be used for applications that use these modules. `esp_wifi` module in the Makefile.
Therefore, module `esp_wifi` is not automatically enabled when module
`netdev_default` is used. Instead, if necessary, the application has to add
the module `esp_wifi` in the Makefile.
``` ```
USEMODULE += esp_wifi USEMODULE += esp_wifi
@ -987,7 +983,9 @@ With ESP-NOW, the ESP32 provides a connectionless communication technology, feat
The RIOT port for ESP32 implements in module ```esp_now``` a ```netdev``` driver which uses ESP-NOW to provide a link layer interface to a meshed network of ESP32 nodes. In this network, each node can send short packets with up to 250 data bytes to all other nodes that are visible in its range. The RIOT port for ESP32 implements in module ```esp_now``` a ```netdev``` driver which uses ESP-NOW to provide a link layer interface to a meshed network of ESP32 nodes. In this network, each node can send short packets with up to 250 data bytes to all other nodes that are visible in its range.
@note Due to symbol conflicts in the ```esp_idf_wpa_supplicant_crypto``` module used by the ```esp_now``` with RIOT's ```crypto``` and ```hashes``` modules, ESP-NOW cannot be used for application that use these modules. Therefore, the module ```esp_now``` is not enabled automatically if the ```netdev_default``` module is used. Instead, the application has to add the ```esp_now``` module in its makefile when needed.<br> @note Module `esp_now`module is not enabled automatically if the
`netdev_default` module is used. Instead, the application has to add the
`esp_now` module in its makefile when needed.<br>
``` ```
USEMODULE += esp_now USEMODULE += esp_now
``` ```