[ESP] Add ESP32C3 DevKitM support to all-clusters-app

[wqx6]

Problem

Need to add ESP32C3 support to the all-clusters-app.

Summary of Changes

1. Update the ESP-IDF to release/v4.3 branch, which supports ESP32C3 module.
2. Add ESP32C3 module support to all-clusters-app.
3. Fix wrong TLVWriter::Put function The wrong TLVWriter::Put function will be called with a unsigned 8-bits(or 16-bits) value passed in #7784

Testing

1. Compiling success with all-clusters-app,lock-app, shell, persistent-storage, temperature-measurement-app and pigweed-app for ESP32 with idf-v4.3.
2. Tested locally with chip-device-ctrl with all-clusters-app for ESP32C3-DevKitM and ESP32-DevKitC

[CLAassistant]

All committers have signed the CLA.

[woody-apple]

@NoyceOne0630 Thanks for the contribution! Can you please sign the CLI, and also restyle the PR per the instructions in:
#6346

[todo]

Not supported

connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp

Lines 584 to 594 in 6318fa7

	// TODO: Not supported
	}
	exit:
	if (err != CHIP_NO_ERROR)
	{
	ChipLogError(DeviceLayer, "Disabling CHIPoBLE service due to error: %s", ErrorStr(err));
	mServiceMode = ConnectivityManager::kCHIPoBLEServiceMode_Disabled;
	}
	}

---

This comment was generated by todo based on a TODO comment in 6318fa7 in #6345. cc @wqx6.

[todo]

fail connection???

connectedhomeip/src/platform/ESP32/nimble/BLEManagerImpl.cpp

Lines 819 to 829 in 6318fa7

	// TODO: fail connection???
	}
	return;
	}
	CHIP_ERROR BLEManagerImpl::HandleTXComplete(struct ble_gap_event * gapEvent)
	{
	ChipLogProgress(DeviceLayer, "Confirm received for CHIPoBLE TX characteristic indication (con %" PRIu16 ") status= %d ",
	gapEvent->notify_tx.conn_handle, gapEvent->notify_tx.status);

---

This comment was generated by todo based on a TODO comment in 6318fa7 in #6345. cc @wqx6.

[wqx6]

the riscv legacy __sync APIs will be added to esp-idf release/v4.3 soon.

[woody-apple]

/rebase

[woody-apple]

Per the updated template, can you update the PR here?

#### Problem
What is being fixed?  Examples:
* Fix crash on startup
* Fixes #12345 12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

#### Change overview
What's in this PR

#### Testing
How was this tested? (at least one bullet point required)
    • If unit tests were added, how do they cover this issue?
    • If unit tests existed, how were they fixed/modified to prevent this in future?
    • If integration tests were added, how do they verify this change?
    • If manually tested, what platforms controller and device platforms were manually tested, and how?
    • If no testing is required, why not?

[wqx6]

esp32c3 support needs idf version v4.3 or later, but pigweed app build fail with idf v4.3, error log shows

portGET_ARGUMENT_COUNT() result does not match for 0 arguments

will update after this PR merged

[dhrishi]

@mspang Can you please review the scripts related changes?

[mspang]

What's the problem with version 5?

[dhrishi]

Hey @mspang I was just referring to the generic changes in requirements.txt for ESP32. Nothing specific :-)

[mspang]

If there is nothing specific then please do not use a less-than requirement.

[chshu]

As documented there: https://github.com/espressif/esp-idf/blob/v4.3/requirements.txt#L20, there was some compatible issue. We will check with our tools team, and update upstream if the issue has been fixed.

[mspang]

Thanks for bug link.

[dhrishi]

Current PR only supports ESP32C3 for all-clusters-app now, the other apps' support will be added in a separate PR

Sure! Please raise a Github issue to track this

[woody-apple]

/rebase

[woody-apple]

@Damian-Nordic @jepenven-silabs ?

[dhrishi]

@wqx6 Please rebase and resolve conflicts.

[mspang]

Can it be >= ?

[wqx6]

This is the same as the file requirements.txt in our ESP-IDF Release v4.3.

[mspang]

Ok, can you fix it upstream?

[chshu]

Hi @mspang, we will double check with our tools team on this specific requirement. Meantime, could we merge it as is, since it's located in requirements.esp32.txt, and we will update after our upsteam change is ready.

[mspang]

I'll hold you to that.

[mspang]

Can it be >= ?

[wqx6]

same as above

[github-actions]

Size increase report for "esp32-example-build" from 8a53528

File	Section	File	VM
chip-all-clusters-app.elf	.dram0.data	-8	-8
chip-all-clusters-app.elf	.flash.rodata	-8	-8
chip-all-clusters-app.elf	.flash.text	-396	-396

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize
.debug_loc,0,8
.debug_str,0,-4

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize
.debug_info,0,3633
.debug_loc,0,1803
.debug_str,0,538
.debug_line,0,454
.debug_abbrev,0,112
.debug_ranges,0,80
[Unmapped],0,16
.dram0.data,-8,-8
.flash.rodata,-8,-8
.symtab,0,-48
.strtab,0,-76
.flash.text,-396,-396

[wqx6]

@andy31415 Can you update the chip-build-esp32 Dockerfile? We have updated the dockerfile using ESP-IDF release tag v4.3 in this PR.