Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge branch 'bugfix/few_typos_in_docs' into 'master'

Browse source 
Fix few typos in documentation

See merge request idf/esp-idf!2519
This commit is contained in:
Angus Gratton 2018-06-07 08:24:23 +08:00
parent dff1a52722 5a9fc19f38
commit 70c6f8a803
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
components/bt/include/esp_bt.h
View file

@ -291,7 +291,7 @@ void esp_vhci_host_register_callback(const esp_vhci_host_callback_t *callback);
/** @brief esp_bt_controller_mem_release
* release the memory by mode, if never use the bluetooth mode
* it can release the .bbs, .data and other section to heap.
* it can release the .bss, .data and other section to heap.
* The total size is about 70k bytes.
*
* esp_bt_controller_mem_release(mode) should be called only before esp_bt_controller_init()

2
docs/en/security/flash-encryption.rst
View file

@ -196,7 +196,7 @@ Flash encryption keys are 32 bytes of random data. You can generate a random key
Alternatively, if you're using :doc:`secure boot <secure-boot>` and have a secure boot signing key then you can generate a deterministic SHA-256 digest of the secure boot private signing key and use this as the flash encryption key::
espsecure.py digest_private-key --keyfile secure_boot_signing_key.pem my_flash_encryption_key.bin
espsecure.py digest_private_key --keyfile secure_boot_signing_key.pem my_flash_encryption_key.bin
(The same 32 bytes is used as the secure boot digest key if you enable :ref:`reflashable mode<secure-boot-reflashable>` for secure boot.)