Feature/esp efuse support

[eren-terzioglu]

Summary

efuse support added to read and write efuses through application code
virtual efuse (efuse simulation) support to test efuse operation codes without damaging the hardware.

• esp32[c3|c6|h2]: Add efuse simulation support
• esp32[c3|c6|h2]: Add efuse support

Impact

ESP32-C3, ESP32-C6, ESP32-H2

Testing

Configrations used with CONFIG_ESPRESSIF_EFUSE option and additionaly CONFIG_ESPRESSIF_EFUSE_VIRTUAL option enabled:

esp32c3-generic:nsh
esp32c6-devkitc:nsh
esp32h2-devkit:nsh

Sample app used to fetch a sample efuse.

[nuttxpr]

[Experimental Bot, please feedback here]

Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.

Yes, this PR appears to meet the basic NuttX requirements, but it's missing some crucial details. Here's a breakdown of what's good and what needs improvement:

Strengths:

• Clear Summary: The summary explains the "what" and "why" of the changes. The inclusion of related issues would strengthen this further.
• Impact Section Mostly Complete: Addresses most impact areas, although the answers are very brief and need more detail.
• Testing Information Provided: Includes target configurations and mentions a sample app.

Weaknesses:

• Missing Issue References: The summary mentions adding efuse support. Are there corresponding issues in either the NuttX or NuttX-Apps repositories? If so, link them.
• Impact Section Lacks Detail: While the impacted architectures are listed, the descriptions are insufficient. For example:
  • User Impact: How will the user interact with the new EFUSE features? New syscalls? Configuration options? This needs to be explicit.
  • Build Impact: Does enabling EFUSE support require any special build flags or dependencies?
  • Hardware Impact: This is just a list of architectures. Does this change touch any specific peripherals or drivers?
  • Documentation Impact: If documentation updates are required, has this PR included them, or is a separate PR planned? Be specific about which documentation needs updating.
  • Security Impact: EFuses often have security implications. This section requires a more thorough analysis. Even if there's no direct security impact, explicitly stating that and the reasoning behind it is important.
  • Compatibility Impact: Same as Security Impact. A more detailed analysis is needed.
• Testing Logs Missing: The template clearly asks for "Testing logs before change" and "Testing logs after change." These are absent. Provide actual log output demonstrating the functionality and the fix/improvement. Just stating that a sample app was used isn't sufficient proof.
• Build Host Information Missing: What system was used to build NuttX? This is critical for reproducibility.
• "Anything else to consider?" Unanswered: This prompts for unusual situations or potential side effects. Even if the answer is "nothing," it should be stated.

Recommendation:

Revise the PR description to provide the missing details. Focus on expanding the Impact and Testing sections to fully address the requirements. A more complete PR description will greatly expedite the review process.

[acassis]

@eren-terzioglu please update boards Documentation/ to include efuse board profile, include usage example.

Please update also the Peripheral Support table.