- type in comment
- no space after `switch`
- overlong line
- `else` when the `if`-branch ends with a `return`
statement anyway
- drop of unused `#include`
- drop of unused function
- `int8_t` for RSSI in dBm when the API expects
`int16_t`
- This might actually fix an issue if the `int8_t` range could
overflow
The RMT driver module `esp_idf_rmt` uses GDMA on ESP32-S3, which in turn requires the activation and deactivation of flash encryption. Therefore, when the RMT driver module `esp_idf_rmt` is used, the function `gdma_disconnect` is used, which in turn requires the function `esp_flash_encryption_enabled`. However, if the NVS flash module `esp_idf_nvs_flash` is also used for some reason, e.g. because WiFi or BLE is used, the function `esp_flash_encryption_enabled` is already compiled in the module `esp_idf_nvs_flash` and must not be compiled again in the module `esp_idf_rmt`.
This makes use of the new bug modeling to declare all platforms that
can use newlib and have no reentrancy hooks as affected by the
non-thread-safe stdio bug. (Which is every platform but ESP* and AVR,
the former because the reentrancy hooks are provided, the latter because
we do not and never will support newlib on them.)
Building on that, the mpaland-printf package is used when newlib is
used and the bug is present. This way we can rely on the stdio being
thread-safe on every platform and not causing random crashes at run
time.
Co-authored-by: mguetschow <mikolai.guetschow@tu-dresden.de>
The esptools/export.sh script has to be sourced, otherwise
the exported variables are not persistent in the environment,
rendering the script useless. The commit adds a check to the
script that it runs in the correct environment and enhances the
documentation to make it clearer that the "source" prefix command
is important.
The PR also introduces a version check for the PATH variable
to notify the user if an old version is present.
