Add STM32H5 architecture documentation.

[kywwilson11]

Summary

Added documentation for STM32H5 Architecture and Nucleo-H563ZI board.

There is support for a handful of peripherals right now. Adding documentation will hopefully encourage others to contribute to the STM32H5 port.

Impact

No impact to code. Only documentation will be updated for STM32H5.

Testing

Used online rst previewer to check formatting in index.rst files.

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR appears to meet the basic NuttX requirements, although it could be more thorough. While it addresses the key areas, it lacks specific details in a few sections, which could hinder review and acceptance.

Here's a breakdown:

• Summary: Adequate. Clearly states the change (documentation addition) and its purpose (encouraging contributions). It could be improved by linking to a related issue if one exists.

• Impact: Mostly adequate. While it correctly states no impact on code, it lacks specificity in the documentation update. Which documentation files are being changed? Listing the modified files directly (e.g., arch/arm/src/stm32h5/README.txt, boards/arm/stm32h5/nucleo-h563zi/README.txt) would be helpful. Explicitly stating "NO" for all other impact categories is good.

• Testing: Insufficient. While checking formatting with a previewer is a good first step, it doesn't demonstrate that the content is accurate or complete. Ideally, you should show some interaction with the hardware or at least the simulator. For example:

  • If possible, build and run a simple "Hello World" on the Nucleo-H563ZI and confirm it works as expected.
  • If hardware isn't readily available, use the simulator (sim:nsh) to demonstrate basic functionality and include a screenshot or console output.
  • Even simply stating "Built successfully for nucleo-h563zi config with no errors" is better than just formatting checks.

  The "Testing logs before change" and "Testing logs after change" sections should not be empty. Since this is documentation, the "after" logs could include relevant excerpts from the generated documentation or output related to the build process.

Recommendation: Strengthen the Testing section with concrete examples. Be specific about the documentation files changed in the Impact section. Consider creating a related issue if one doesn't exist and link it in the Summary. These small additions will significantly improve the PR's clarity and chances of acceptance.

[acassis]

@kywwilson11 you missed to include a picture of the board.

All the boards Documentation/ needs to include a picture of the board. Some are missing because they are old contribution or someone failed to ask it during the review!

[kywwilson11]

I added an image of the Nucleo-H563ZI, and included it in the board documentation. Thank you for the feedback.