esp-idf/components/hal
Darian Leung 3819d22e93 twai: Add errata workaround for listen only mode
This commit adds a workaround for the TWAI listen only mode errata which is
present on the ESP32, ESP32-S2, ESP32-S3, and ESP32-C3. twai_get_status_info()
has also been updated to account for the fact that TEC/REC are frozen in
listen only mode.

Errata Description:

When the TWAI controller is put into listen only mode, it should not influence
the TWAI bus in any way (i.e., should never send a dominant bit). However,
on the targets listed above, the TWAI controller will send dominant bits in an
error frame (i.e., active error frame), even if the controller is set to listen
only mode.

Workaround:

We can force the TWAI controller into the error passive state on startup (by
setting the REC to >= 128). Since the TEC/REC are frozen in listen only mode,
the TWAI controller will remain error passive and only send recessive bits
(i.e., passive error frames), thus will not influence the TWAI bus.

Closes https://github.com/espressif/esp-idf/issues/9157
2023-02-24 20:26:53 +08:00
..
esp32 rmt: force inline LL functions 2023-02-14 15:11:35 +08:00
esp32c3 rmt: force inline LL functions 2023-02-14 15:11:35 +08:00
esp32h2 rmt: force inline LL functions 2023-02-14 15:11:35 +08:00
esp32s2 rmt: force inline LL functions 2023-02-14 15:11:35 +08:00
esp32s3 rmt: force inline LL functions 2023-02-14 15:11:35 +08:00
include/hal soc_caps: remove SOC_GPIO_SUPPORT_SLP_SWITCH 2023-02-09 17:52:49 +08:00
platform_port/include/hal
test
CMakeLists.txt
Kconfig
README.md
adc_hal.c
aes_hal.c
component.mk
cpu_hal.c
dac_hal.c
ds_hal.c
efuse_hal.c
emac_hal.c
gdma_hal.c
gpio_hal.c
i2c_hal.c
i2c_hal_iram.c
i2s_hal.c
interrupt_controller_hal.c
lcd_hal.c
ledc_hal.c
ledc_hal_iram.c
linker.lf
mcpwm_hal.c
mpu_hal.c
pcnt_hal.c
rmt_hal.c
rtc_io_hal.c
sdio_slave_hal.c
sha_hal.c
sigmadelta_hal.c
soc_hal.c
spi_flash_encrypt_hal_iram.c
spi_flash_hal.c
spi_flash_hal_common.inc
spi_flash_hal_gpspi.c
spi_flash_hal_iram.c
spi_hal.c
spi_hal_iram.c
spi_slave_hal.c
spi_slave_hal_iram.c
spi_slave_hd_hal.c
systimer_hal.c
timer_hal.c
touch_sensor_hal.c
twai_hal.c twai: Add errata workaround for listen only mode 2023-02-24 20:26:53 +08:00
twai_hal_iram.c
uart_hal.c
uart_hal_iram.c
usb_dwc_hal.c
usb_hal.c
usb_phy_hal.c
wdt_hal_iram.c
xt_wdt_hal.c

README.md

hal

The hal component provides hardware abstraction and implementation for targets supported by ESP-IDF.

include/hal

/include/hal contains header files which provides a hardware-agnostic interface to the SoC. The interface consists of function declarations and abstracted types that other, higher level components can make use of in order to have code portable to all targets ESP-IDF supports.

It contains an abstraction layer for ineracting with/driving the hardware found in the SoC such as the peripherals and 'core' hardware such as the CPU, MPU, caches, etc. It contains for the abstracted types. The abstraction design is actually two levels -- often somtimes xxx_hal.h includes a lower-level header from a xxx_ll.h, which resides in the implementation. More on this abstraction design in the hal/include/hal's Readme

target/include

Provides the implementation of the hardware-agnostic interface in the abstraction. Target-specific subdirectories exist for wildly different implementations among targets; while code that are common/very similar might be placed in the top-level of /<target>/include, using some amount of conditional preprocessors. It is up to the developers' discretion on which strategy to use. Code usually reside in source files with same names to header files whose interfaces they implement, ex. xxx_hal.c for xxx_hal.h.

As mentioned previously, the lower-level abstraction header xxx_ll.h resides in this directory, since they contain hardware-specific details. However, what these can do is provide some abstraction among implementations, so that more code can be moved to the common, non-target-specific subdirectories.

This can also contain target-specific extensions to the HAL headers. These target-specific HAL headers have the same name and include the abstraction layer HAL header via include_next. These extensions might add more function declarations or override some things using macro magic.