arnavsharma990 opened a new issue, #20174: URL: https://github.com/apache/nuttx/issues/20174
### Is your feature request related to a problem? Please describe. ### Is your feature request related to a problem? Please describe. The `rv-virt:elf` and `rv-virt:libcxx64` configurations currently have no dedicated documentation sections in `Documentation/platforms/risc-v/qemu-rv/boards/rv-virt/index.rst`. Their purpose therefore has to be inferred from the defconfigs: `elf` is a 32-bit minimal `CONFIG_EXAMPLES_ELF` configuration booting into `elf_main` without NSH, while `libcxx64` is a 64-bit NSH configuration with `CONFIG_LIBCXX` and `CONFIG_TESTING_CXXTEST`. There is also no clear documentation explaining the LED/GPIO behavior of `rv-virt`. The current defconfigs do not enable `CONFIG_GPIO`, there is no GPIO driver under `arch/risc-v/src/qemu-rv/`, and `board_userled()` in `boards/risc-v/qemu-rv/rv-virt/src/qemu_rv_userleds.c` is a logging stub. Users of configurations such as `leds64` may therefore expect the LEDs to be backed by controllable GPIO hardware when they are not. ### Describe the solution you'd like Add short documentation sections for the `elf` and `libcxx64` configurations describing their intended purpose and relevant characteristics. Also add a note to the `leds64` documentation clarifying that the LEDs are virtual/log-only and are not backed by a NuttX GPIO controller in the current `rv-virt` implementation. ### Describe alternatives you've considered The behavior and configuration purpose can currently be determined by inspecting the individual defconfigs and board source files, but this requires users to inspect the source tree rather than relying on the platform documentation. No code changes to add GPIO emulation are proposed as part of this request; the goal is to document the existing behavior and configuration purposes clearly. ### Verification - [x] I have verified before submitting the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
