New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests/drivers/gpio/gpio_api_1pin failed on reel_board. #25051
Comments
On mec15xxevb_assy6853, are there jumpers on |
@dcpleung i removed the JP31 13-14 and JP41 1-2, the test_gpio_pin_configure_push_pull passed, but it failed at test_gpio_int_edge_falling. starting test - test_gpio_int_edge_falling |
The interrupt tests should be fixed by #25155 |
this test also failed on sam_e70_xplained and up_squared. |
@chen-png Are you sure this test failed on
|
for this test tests/drivers/gpio/gpio_api_1pin, do i need to do any gpio connections for sam_e70_xplained? this is the test result with no gpio connections. *** Booting Zephyr OS build v2.3.0-rc1-20-g9a37154151d5 *** starting test - test_gpio_pin_configure_push_pull |
@chen-png No GPIO connection necessary; this test passes for me on
|
the test is passed on sam_e70_xplained, maybe it's caused by my testing environment before. |
for up_squared, this test is passed now due to #25384 |
this test is passed on mec15xxevb_assy6853 now |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
To Reproduce
Steps to reproduce the behavior:
Screenshots or console output
*** Booting Zephyr OS build zephyr-v2.2.0-2414-gcbd9c86b5ce2 ***
Running test suite gpio_api_1pin_test
starting test - test_gpio_pin_configure_push_pull
Running test on port=GPIO_0, pin=11
Assertion failed at WEST_TOPDIR/zephyr/tests/drivers/gpio/gpio_api_1pin/src/test_config.c:31: pin_get_raw_and_verify: (val_expected not equal to val_actual)
Test point 10: invalid pin get value
FAIL - test_gpio_pin_configure_push_pull
starting test - test_gpio_pin_configure_single_ended
Running test on port=GPIO_0, pin=11
When configured as input test pin value is high
PASS - test_gpio_pin_configure_single_ended
starting test - test_gpio_pin_set_get_raw
Running test on port=GPIO_0, pin=11
PASS - test_gpio_pin_set_get_raw
starting test - test_gpio_pin_set_get
....
starting test - test_gpio_int_edge_both
Running test on port=GPIO_0, pin=11
Pin interrupt is not supported.
SKIP - test_gpio_int_edge_both
starting test - test_gpio_int_edge_to_active
Step 1: Configure pin as active high
Running test on port=GPIO_0, pin=11
Pin interrupt is not supported.
SKIP - test_gpio_int_edge_to_active
starting test - test_gpio_int_edge_to_inactive
Step 1: Configure pin as active high
Running test on port=GPIO_0, pin=11
Pin interrupt is not supported.
SKIP - test_gpio_int_edge_to_inactive
starting test - test_gpio_int_level_high
Running test on port=GPIO_0, pin=11
PASS - test_gpio_int_level_high
starting test - test_gpio_int_level_low
Running test on port=GPIO_0, pin=11
PASS - test_gpio_int_level_low
starting test - test_gpio_int_level_active
Step 1: Configure pin as active high
Running test on port=GPIO_0, pin=11
Step 2: Configure pin as active low
Running test on port=GPIO_0, pin=11
PASS - test_gpio_int_level_active
starting test - test_gpio_int_level_inactive
Step 1: Configure pin as active high
Running test on port=GPIO_0, pin=11
Step 2: Configure pin as active low
Running test on port=GPIO_0, pin=11
PASS - test_gpio_int_level_inactive
starting test - test_gpio_pin_toggle_visual
Running test on port=GPIO_0, pin=11
LED ON
LED OFF
LED ON
LED OFF
PASS - test_gpio_pin_toggle_visual
Test suite gpio_api_1pin_test failed.
PROJECT EXECUTION FAILED
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: