Espressif ESP32-C6 Series SoC Errata User Manual

June 16, 2024
ESPRESSIF

Espressif ESP32-C6 Series SoC Errata User Manual

Espressif ESP32-C6 Series SoC Errata User Manual

Introduction
This document describes known errata in ESP32-C6 series of SoCs.

www.espressif.com

Chip Identification

Note :
Check the link or the QR code to make sure that you use the latest version of this document:
https://espressif.com/sites/default/files/documentation/esp32-c6_errata_en.pdf

1 Chip Revision

Espressif is introducing vM.X numbering scheme to indicate chip revisions.

M – Major number, indicating the major revision of the chip product. If this number changes, it means the software used for the previous version of the product is incompatible with the new product, and the software version shall be upgraded for the use of the new product.

X – Minor number, indicating the minor revision of the chip product. If this number changes, it means the
software used for the previous version of the product is compatible with the new product, and there is no need to upgrade the software.

The vM.X scheme replaces previously used chip revision schemes, including ECOx numbers, Vxxx, and other formats if any.

The chip revision is identified by:

  • eFuse field EFUSE_RD_MAC_SPI_SYS_3_REG[23:22] and EFUSE_RD_MAC_SPI_SYS_3_REG[21:18]

Table 1: Chip Revision Identification by eFuse Bits

Espressif ESP32-C6 Series SoC Errata - Table 1 Chip Revision Identification
by eFuse Bits

  • Espressif Tracking Information line in chip marking

Espressif ESP32-C6 Series SoC Errata - Figure 1

Figure 1: Chip Marking Diagram

Table 2: Chip Revision Identification by Chip Marking

  • Specification Identifier line in module marking

Espressif ESP32-C6 Series SoC Errata - Figure 2

Figure 2: Module Marking Diagram

Table 3: Chip Revision Identification by Module Marking

Note:

2 Additional Methods

Some errors in the chip product don’t need to be fixed at the silicon level, or in other words in a new chip revision.

In this case, the chip may be identified by Date Code in chip marking (see Figure 1). For more information,
please refer to Espressif Chip Packaging Information.

Modules built around the chip may be identified by PW Number in product label (see Figure 3). For more information, please refer to Espressif Module Packaging Information.

Espressif ESP32-C6 Series SoC Errata - Figure 3

Figure 3: Module Product Label

Note :
Please note that PW Number is only provided for reels packaged in aluminum moisture barrier bags (MBB).

Errata Description

Table 4: Errata Summary

Espressif ESP32-C6 Series SoC Errata - Table 4 Errata
Summary

3 RISC-V CPU

3.1 Possible deadlock due to out-of-order execution of instructions when writing to LP SRAM is involved

Description

When HP CPU executes instructions (instruction A and instruction B successively) in LP SRAM, and instruction A and instruction B happen to follow the following patterns:

  • Instruction A involves writing to memory. Examples: sw/sh/sb
  • Instruction B involves only accessing the instruction bus. Examples: nop/jal/jalr/lui/auipc
  • The address of instruction B is not 4-byte aligned

The data written by instruction A to memory is only committed after instruction B has completed execution. This introduces a risk where, after instruction A writing to memory, if an infinite loop is executed in instruction B, the writing of instruction A will never complete.

Workarounds

When you experience this problem, or when you check the assembly code and see the above mentioned pattern,

  • Add a fence instruction between instruction A and the infinite loop. This can be achieved by using the rv_utils_memory_barrier interface in ESP-IDF.
  • Replace the infinite loop with instruction wfi. This can be achieved by using the rv_utils_wait_for_intr interface in ESP-IDF.
  • Disable the RV32C (compressed) extension when compiling code that to be executed in LP SRAM to avoid instructions with not 4-byte aligned addresses.

Solution
To be fixed in the future chip revisions.

4 Clock

4.1 Inaccurate Calibration of RC_FAST_CLK Clock

Description

In the ESP32-C6 chip, the frequency of the RC_FAST_CLK clock source is too close to the reference clock (40 MHz XTAL_CLK) frequency, making it impossible to calibrate accurately. This may affect peripherals that use RC_FAST_CLK and have stringent requirements for its accurate clock frequency.

For peripherals using RC_FAST_CLK, please refer to ESP32-C6 Technical Reference Manual > Chapter Reset and Clock.

Workarounds
Use other clock sources instead of RC_FAST_CLK.

Solution
Fixed in chip revision v0.1.

5 Reset

5.1 System Reset Triggered by RTC Watchdog Timer Cannot be Correctly Reported

Description
When the RTC watchdog timer (RWDT) triggers a system reset, the reset source code can not be latched correctly. As a result, the reset cause reported is indeterminate and might be wrong.

Workarounds
No workaround.

Solution
Fixed in chip revision v0.1.

6 RMT

6.1 The idle state signal level might run into error in RMT continuous TX mode

Description
In ESP32-C6’s RMT module, if the continuous TX mode is enabled, it is expected that the data transmission stops after the data is sent for RMT_TX_LOOP_NUM_CHn rounds, and after that, the signal level in idle state should be controlled by the “level” field of the end-marker.

However, in real situation, after the data transmission stops, the channel’s idle state signal level is not controlled by the “level” field of the end- marker, but by the level in the data wrapped back, which is indeterminate.

Workarounds
Users are suggested to set RMT_IDLE_OUT_EN_CHn to 1 to only use registers to control the idle level.
This issue has been bypassed since the first ESP-IDF version that supports continuous TX mode (v5.1). In these versions of ESP-IDF, it is configured that the idle level can only be controlled by registers.

Solution
No fix scheduled.

7 Wi-Fi

7.1 ESP32-C6 Cannot be 802.11mc FTM Initiator

Description
The time of T3 (i.e. time of departure of ACK from Initiator) used in 802.11mc Fine Time Measurement (FTM) cannot be acquired correctly, and as a result ESP32-C6 cannot be the FTM Initiator.

Workarounds
No workaround.

Solution
To be fixed in the future chip revisions.

Related Documentation and Resources

Related Documentation

Developer Zone

Products

Contact Us

Revision History

Espressif ESP32-C6 Series SoC Errata - Revision
History

www.espressif.com

Disclaimer and Copyright Notice
Information in this document, including URL references, is subject to change without notice.
ALL THIRD PARTY’S INFORMATION IN THIS DOCUMENT IS PROVIDED AS IS WITH NO WARRANTIES TO ITS AUTHENTICITY AND ACCURACY.
NO WARRANTY IS PROVIDED TO THIS DOCUMENT FOR ITS MERCHANTABILITY, NON- INFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, NOR DOES ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION OR SAMPLE.
All liability, including liability for infringement of any proprietary rights, relating to use of information in this document is disclaimed. No licenses express or implied, by estoppel or otherwise, to any intellectual property rights are granted herein.
The Wi-Fi Alliance Member logo is a trademark of the Wi-Fi Alliance. The Bluetooth logo is a registered trademark of Bluetooth SIG.
All trade names, trademarks and registered trademarks mentioned in this document are property of their respective owners, and are hereby acknowledged.
Copyright © 2023 Espressif Systems (Shanghai) Co., Ltd. All rights reserved.

Documents / Resources

| Espressif ESP32-C6 Series SoC Errata [pdf] User Manual
ESP32-C6 Series SoC Errata, ESP32-C6 Series, SoC Errata, Errata
---|---

References

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

Related Manuals