eren-terzioglu opened a new pull request, #18656:
URL: https://github.com/apache/nuttx/pull/18656

   ## Summary
   
   <!-- This field should contain a summary of the changes. It will be 
pre-filled with the commit's message and descriptions. Adjust it accordingly -->
   
   * Docs/risc-v/esp32p4: Add LPI2C docs
   
   Add LPI2C docs for esp32p4
   
   * boards/risc-v/esp32p4: Add LPI2C board support
   
   Add LPI2C board support for esp32p4
   
   * arch/risc-v/espressif: Add LPI2C support for esp32p4
   
   Add LPI2C support for esp32p4
   
   * Docs/risc-v/esp32p4: Add LPUART docs for esp32p4
   
   Add LPUART docs for esp32p4
   
   * arch/risc-v/espressif: Add LPUART support for esp32p4
   
   Add LPUART support for esp32p4
   
   ## Impact
   <!-- Please fill the following sections with YES/NO and provide a brief 
explanation -->
   
   Impact on user: Yes, users can use LPI2C and LPUART for esp32p4
   <!-- Does it impact user's applications? How? -->
   
   Impact on build: No
   <!-- Does it impact on building NuttX? How? (please describe the required 
changes on the build system) -->
   
   Impact on hardware: LPUART and LPI2C supported by esp32p4
   <!-- Does it impact a specific hardware supported by NuttX? -->
   
   Impact on documentation: Yes, related docs added
   <!-- Does it impact the existing documentation? Please provide additional 
documentation to reflect that -->
   
   Impact on security: No
   <!-- Does it impact NuttX's security? -->
   
   Impact on compatibility: No
   <!-- Does it impact compatibility between previous and current versions? Is 
this a breaking change? -->
   
   ## Testing
   <!-- Please provide all the testing procedure. Consider that upstream 
reviewers should be able to reproduce the same testing performed internally -->
   
   ### For LPUART
   
   `esp32p4-function-ev-board:nsh` used with `CONFIG_ESPRESSIF_LP_UART0=y` 
option used
   
   
   ### For LPI2C
   `esp32p4-function-ev-board:i2c` defconfig used with these options:
   
   ```
   CONFIG_I2CTOOL_MAXBUS=3
   CONFIG_ESPRESSIF_LP_I2C0=y
   ```
   
   ### Building
   <!-- Provide how to build the test for each SoC being tested -->
   
   ### For LPUART
   
   Command to build:
   
   ```
   make distclean && ./tools/configure.sh esp32p4-function-ev-board:nsh && 
kconfig-tweak -e CONFIG_ESPRESSIF_LP_UART0 && make olddefconfig && make -j && 
make download ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BAUD=921600 ESPTOOL_BINDIR=./
   ```
   
   ### For LPI2C
   
   Command to build:
   
   ```
   make distclean && ./tools/configure.sh esp32p4-function-ev-board:i2c && 
kconfig-tweak -e  CONFIG_ESPRESSIF_LP_I2C0 && kconfig-tweak set-value 
CONFIG_I2CTOOL_MAXBUS 3 && make olddefconfig && make -j && make download 
ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BAUD=921600 ESPTOOL_BINDIR=./
   ```
   
   ### Running
   <!-- Provide how to run the test for each SoC being tested -->
   
   ### For LPUART
   
   `echo 1 > /dev/ttyS1` command used to test with using a logic analyzer. Here 
are the pins
   
   |Pin Name|Pin Number|
   |:-----:|:---------:|
   | TX | 14 |
   |RX | 15 |
   
   ### For LPI2C
   Firstly `ls /dev` command used to test is it initialized. `i2c2` should 
appear on output. After that these pins connected to logic analyzer:
   
   | Pin Name | Pin value |
   |:--:|:--:|
   | SCL | 4 |
   | SDA | 5 |
   
   After the connection `i2c dev -b 2 0x70 0x77` command used and output 
checked with logic analyzer
   
   ### Results
   <!-- Provide tests' results and runtime logs -->
   
   ### For LPUART
   
   ```
   nsh> echo 1 > /dev/ttyS1
   nsh> 
   ```
   
   ### For LPI2C
   
   Output should look like this:
   
   ```
   nsh> 
   nsh> ls /dev
   /dev:
    console
    i2c0
    i2c2
    null
    random
    ttyS0
    zero
   nsh> 
   nsh> i2c dev -b 2 0x70 0x77
   NOTE: Some devices may not appear with this scan.
   You may also try a scan with the -z flag to discover more devices using a 
zero-byte write request.
        0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
   00:                                                 
   10:                                                 
   20:                                                 
   30:                                    Elapsed time: 0
    1. STATUS: 00000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000070 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000071 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000072 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000073 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000074 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000075 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000076 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
   Elapsed time: 0
    1. STATUS: 66000000 COUNT:   1 EVENT: SENDADDR  ( 1) PARM: 00000077 TIME: 0
    2. STATUS: 36000010 COUNT:   1 EVENT: ERROR     ( 6) PARM: 00000400 TIME: 0
                
   40:                                                 
   50:                                                 
   60:                                                 
   70: -- -- -- -- -- -- -- --                         
   nsh>
   ```


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