Conversation
xuchang-vivo
force-pushed
the
xc/seeed_xiao_esp32c3_support
branch
from
cdc5420 to
b17327c
Compare
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/22472583951. |
|
build_prs #334 vivoblueos/build#60 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/22472627070. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/22472583951. |
|
❌ Job failed. Failed jobs: build_and_check_boards (failure), see https://github.com/vivoblueos/kernel/actions/runs/22472627070. |
|
build_prs #334 vivoblueos/build#60 |
|
Job is started, see https://github.com/vivoblueos/kernel/actions/runs/22472977078. |
|
✅ All jobs completed successfully, see https://github.com/vivoblueos/kernel/actions/runs/22472977078. |
| // See the License for the specific language governing permissions and | ||
| // limitations under the License. | ||
|
|
||
| #[cfg(target_chip = "esp32c3")] |
There was a problem hiding this comment.
What's the diff between target_board and target_chip?
There was a problem hiding this comment.
Different boards may use the same chip and therefore share the same driver code. However, boards can have different configurations: for example, some boards use UART2 as the console, while others use UART1; some boards have a temperature sensor, and others do not.
Co-authored-by: Kai Law <lawkai@vivo.com>
Co-authored-by: Kai Law <lawkai@vivo.com>
2 participants
How to flash
Already tested on esp32-c3-devkit-rust-1, also xiao esp32c3