tmedicci opened a new pull request, #17144:
URL: https://github.com/apache/nuttx/pull/17144

   ## Summary
   
   * risc-v/espressif/ledc: Update common source code functions
     - Updates the common source code for the LEDC peripheral used by 
Espressif's RISC-Vs SoCs. This enables newer SoCs to be supported in the future 
while maintaining backwards compatibility.
   
   ## Impact
   
   Impact on user: No.
   
   Impact on build: No.
   
   Impact on hardware: Not yet: newer Espressif SoCs can be supported on NuttX 
following this change.
   
   Impact on documentation: No.
   
   Impact on security: No.
   
   Impact on compatibility: No. It's totally backwards compatible.
   
   ## Testing
   
   Testing can be performed using any of the `pwm` defconfigs available for any 
of Espressif's RISC-V-based devices (ESP32-C3, ESP32-C6, or ESP32-H2). The 
behavior of the LEDC peripheral didn't change, and this PR's results are the 
same as before it. This can be verified:
   
   ### Building
   
   #### ESP32-C3
   
   ```
   make -j distclean && ./tools/configure.sh esp32c3-generic:pwm && make flash 
ESPTOOL_PORT=/dev/ttyUSB0 && picocom -b 115200 /dev/ttyUSB0
   ```
   
   #### ESP32-C6
   
   ```
   make -j distclean && ./tools/configure.sh esp32c6-devkitc:pwm && make flash 
ESPTOOL_PORT=/dev/ttyUSB0 && picocom -b 115200 /dev/ttyUSB0
   ```
   
   #### ESP32-H2
   
   ```
   make -j distclean && ./tools/configure.sh esp32h2-devkit:pwm && make flash 
ESPTOOL_PORT=/dev/ttyUSB0 && picocom -b 115200 /dev/ttyUSB0
   ```
   
   ### Running
   
   Run the `pwm` application on NSH and monitor pin's output.
   
   ### Results
   
   ```
   nsh> pwm
   pwm_main: starting output with frequency: 100 duty: 00007fff
   pwm_main: stopping output
   ```


-- 
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]

Reply via email to