It looks like as a part of optimization for inlined functions like 'mmu_ll_vaddr_to_laddr' Clang aligns constant value
used for bitwise AND operation with the pointer to external symbol passed to the function as parameter.
That led to assertion failures because boundaries can be unaligned to 4 bytes.
fix(ws_transport): Fix incorrect packet-len on linux due to int promotions of char (GitHub PR)
Closes IDFGH-13642 and IDFGH-13657
See merge request espressif/esp-idf!33595
fix(pm): fix the issue of regdma wait node to immediately return to done caused by regdma wait mode comparator for esp32c6, esp32h2 and esp32p4
Closes PM-202
See merge request espressif/esp-idf!33547
This commit fixes a bug in the no-split buffer which could receive an
item prematurely if the space on the buffer is acquired until the buffer
is full. The commit also adds a unit test for this scenario.
Closes https://github.com/espressif/esp-idf/issues/14568
Explicitly set shell type in export.sh for bash and zsh
-Most of the issues reported with the updated export scripts are related
to shell detection. Since we already know the shell type for commonly
used ones like bash or zsh, we can pass the shell type directly to the
activate script. This should hopefully resolve the shell detection
problems for most users.
This update also modifies the shell type detection to rely solely on
psutil.Process().cmdline() rather than psutil.Process().exe(). This
change aims to resolve permission issues that may occur if, for example,
the Python binary has certain capabilities assigned.
Move shell completion to the init script
- Currently we are expanding the autocompletion in the activate script and
adding the expanded commands into the init script. To avoid
concerns about shell versions, move the entire expansion to the init
script.
The rc scripts should be included only when a new shell is started. At
present, for bash and zsh, we are also including them in the export
scripts, which is incorrect and may cause recursion.
Closes https://github.com/espressif/esp-idf/issues/14584
Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
feat(advanced_console): Add ESP32-P4 ESP32-C5 model support in 'version' command output (GitHub PR)
Closes IDFGH-13722
See merge request espressif/esp-idf!33565
fix(bt/bluedroid): Fixed access fault when reading BLE controller information fails
Closes BLERP-1019 and BLERP-1020
See merge request espressif/esp-idf!33406
refactor(bt/bluedroid): Refactor the print for BLE examples
Closes BLERP-904, BLERP-910, BLERP-1026, and BLERP-1031
See merge request espressif/esp-idf!33296
The model ESP32P4 and ESP32C5 was unknown on version command in iperf example
add model ESP32P4 and ESP32C5
which prints out model names now by the knowed model
ESP32P4 = "ESP32-P4"
ESP32C5 = "ESP32-C5"
example app: iperf
before:
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
model:Unknown
cores:1
feature:/802.11bgn/BLE/External-Flash:8 MB
revision number:0
iperf>
after this add model is knowed now
iperf> version
IDF Version:v5.4-dev-2744-g59e1838270-dirty
Chip info:
model:ESP32-C5
cores:1
feature:/802.11bgn/BLE/External-Flash:8 MB
revision number:0
iperf>
Merges https://github.com/espressif/esp-idf/pull/14593
