boards/risc-v: GPIO support on esp32p4-tab5

[fdcavalcanti]

Summary

• Documentation: add gpio defconfig to esp32p4-tab5 board

Adds documentation for the GPIO defconfig on esp32p4-tab5 board.

• boards/risc-v: GPIO support on esp32p4-tab5

Adds GPIO defconfig on M5Stack Tab5. The example has one GPIO output
and one GPIO interrupt.

This PR adds GPIO support for the M5Stack Tab5 board.
The GPIOs available on the M5-Bus on the backside of the device are defined for easier reference.

Impact

Impact on user: New defconfig added for GPIO control.

Impact on build: No.

Impact on hardware: Only affects esp32p4-tab5 board.

Impact on documentation: Adds documentation for the new defconfig.

Impact on security: No.

Impact on compatibility: No.

Testing

Building

• ./tools/configure.sh -S esp32p4-tab5:gpio
• make and flash

Running

GPIO output test:

nsh> gpio -o 1 /dev/gpio0
Driver: /dev/gpio0
  Output pin:    Value=0
  Writing:       Value=1
  Verify:        Value=1
nsh> gpio -o 0 /dev/gpio0
Driver: /dev/gpio0
  Output pin:    Value=1
  Writing:       Value=0
  Verify:        Value=0
nsh> 

GPIO interrupt test:

nsh> gpio -w 1 /dev/gpio1
Driver: /dev/gpio1
  Interrupt pin: Value=0
  Verify:        Value=0
nsh> 

Results

GPIO operates as expected both output and interrupt modes (visual/manual inspection).

[github-actions]

MemBrowse Memory Report

No memory changes detected for:

• arduino-mega2560
• esp32-devkitc
• hifive1-revb
• mirtoo
• qemu-armv8a
• qemu-intel64
• rx65n-rsk2mb
• s698pm-dkit
• stm32-nucleo-f103rb

[acassis]

@fdcavalcanti have you tried ESP32-P4 running on Protected Mode?

There is a guy facing issues to get it working:

[fdcavalcanti]

@fdcavalcanti have you tried ESP32-P4 running on Protected Mode?

There is a guy facing issues to get it working:

No I have not

[acassis]

@fdcavalcanti have you tried ESP32-P4 running on Protected Mode?
There is a guy facing issues to get it working:

No I have not

Ok, I will buy an ESP32-P4 board on Aliexpress to try to help. Thank you!