-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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_basic_api failed on mec15xxevb_assy6853 board. #25272
Comments
@franciscomunoz @dcpleung Could you take a look of this? |
Because GPIO_050 has set to be used for TACH, so this is supposed to fail. A new GPIO line is needed. |
@chen-png could you please label test failures with the "Tests" label? |
@dcpleung |
I am going to look for another GPIO line today. |
GPIO 050/051 are being used for tachometer sensor as CONFIG_TACH_XEC is enabled by default. So for the gpio_basic_api test, another set of GPIOs are needed. GPIO 156/157 are chosen as they are (more or less) dedicated for two LEDs on board and not being used for other functions (pinmux-wise). Fixes zephyrproject-rtos#25272 Signed-off-by: Daniel Leung <[email protected]>
yes,i will. |
GPIO 050/051 are being used for tachometer sensor as CONFIG_TACH_XEC is enabled by default. So for the gpio_basic_api test, another set of GPIOs are needed. GPIO 156/157 are chosen as they are (more or less) dedicated for two LEDs on board and not being used for other functions (pinmux-wise). Fixes #25272 Signed-off-by: Daniel Leung <[email protected]>
GPIO 050/051 are being used for tachometer sensor as CONFIG_TACH_XEC is enabled by default. So for the gpio_basic_api test, another set of GPIOs are needed. GPIO 156/157 are chosen as they are (more or less) dedicated for two LEDs on board and not being used for other functions (pinmux-wise). Fixes zephyrproject-rtos#25272 Signed-off-by: Daniel Leung <[email protected]>
Describe the bug
running tests/drivers/gpio/gpio_basic_api on mec board, i connected Pin11 and Pin 13 on JP27, and removed jumper on JP15, but it still failed with "Check GPIO040_076 output 8 connected to input 9".
i read the related issue #22931 and git bisect, found the first bad commit is e11da05.
To Reproduce
Steps to reproduce the behavior:
-T tests/drivers/gpio/gpio_basic_api/ -vv
Screenshots or console output
DEBUG - DEVICE: *** Booting Zephyr OS build zephyr-v2.2.0-322-ge11da0582d85 ***
DEBUG - DEVICE: Running test suite gpio_basic_test
DEBUG - DEVICE:
DEBUG - DEVICE: starting test - test_gpio_port
DEBUG - DEVICE: Validate device GPIO040_076
DEBUG - DEVICE: Check GPIO040_076 output 8 connected to input 9
DEBUG - DEVICE: FATAL output pin not wired to input pin? (out high => in low)
DEBUG - Timed out while monitoring serial output on mec15xxevb_assy6853
INFO - 1/1 mec15xxevb_assy6853 tests/drivers/gpio/gpio_basic_api/drivers.gpio.2pin FAILED Timeout (device 113.219s)
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: