mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-28 22:49:47 +01:00
treewide: replace occurrences of tests/periph_ with new path
This commit is contained in:
parent
c51d5357e6
commit
da95d2c56c
6
.github/workflows/test-on-iotlab.yml
vendored
6
.github/workflows/test-on-iotlab.yml
vendored
@ -77,12 +77,12 @@ jobs:
|
||||
COMPILE_AND_TEST_FOR_BOARD: ./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py
|
||||
COMPILE_AND_TEST_ARGS: --with-test-only --jobs=2 --report-xml
|
||||
# Exclude applications that are expected to fail or cannot run on iotlab
|
||||
# - tests/periph_timer_short_relative_set is expected to fail
|
||||
# - tests/periph/timer_short_relative_set is expected to fail
|
||||
# - tests/riotboot requires the riotboot feature and provides a test
|
||||
# but flashing at a specific offset is not (yet) supported on IoT-LAB
|
||||
# so it will always fail because of that limitation
|
||||
APPLICATIONS_EXCLUDE: tests/periph_timer_short_relative_set tests/riotboot
|
||||
# Increase tolerance error with `tests/periph_timer_periodic` because
|
||||
APPLICATIONS_EXCLUDE: tests/periph/timer_short_relative_set tests/riotboot
|
||||
# Increase tolerance error with `tests/periph/timer_periodic` because
|
||||
# of timing issues with the test script when running in the github
|
||||
# actions environment
|
||||
TEST_PERIPH_TIMER_PERIODIC_PRECISION: 0.30
|
||||
|
4
.github/workflows/test-on-ryot.yml
vendored
4
.github/workflows/test-on-ryot.yml
vendored
@ -80,9 +80,9 @@ jobs:
|
||||
# DOCKER_ENVIRONMENT_CMDLINE=\'-e CFLAGS=-D<flag>\'
|
||||
COMPILE_AND_TEST_VARS: ''
|
||||
APPLICATIONS: ''
|
||||
# Exclude 'tests/periph_timer_short_relative_set' since its expected
|
||||
# Exclude 'tests/periph/timer_short_relative_set' since its expected
|
||||
# to fail on most BOARDs
|
||||
APPLICATIONS_EXCLUDE: 'tests/periph_timer_short_relative_set'
|
||||
APPLICATIONS_EXCLUDE: 'tests/periph/timer_short_relative_set'
|
||||
steps:
|
||||
- name: Checkout RIOT
|
||||
uses: actions/checkout@main
|
||||
|
2
.murdock
2
.murdock
@ -129,7 +129,7 @@ tests/driver_t*
|
||||
tests/driver_u*
|
||||
tests/driver_v*
|
||||
tests/external_board_dirs
|
||||
tests/periph_*
|
||||
tests/periph/*
|
||||
tests/pkg/elk
|
||||
tests/pkg/uzlib
|
||||
tests/prng_*
|
||||
|
@ -77,7 +77,7 @@ SERCOM non-secure mode. To do so, a fuse bit must be set in User ROW
|
||||
flash memory. Such action can be done with the following EDBG command:
|
||||
'edbg -t saml11 -F w0,194,1'
|
||||
or pass it as argument when calling make:
|
||||
EDBG_ARGS="-F w0,194,1" BOARD=saml11-xpro make flash term -C tests/periph_uart
|
||||
EDBG_ARGS="-F w0,194,1" BOARD=saml11-xpro make flash term -C tests/periph/uart
|
||||
|
||||
## Supported Toolchains
|
||||
|
||||
|
@ -1387,7 +1387,7 @@ interrupt or if the RxD signal of UART0 goes HIGH at least 4 times
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
CFLAGS='-DESP_PM_WUP_PINS=GPIO25 -DESP_PM_WUP_LEVEL=ESP_PM_WUP_PINS_ALL_LOW \
|
||||
-DESP_PM_WUP_UART0=6 -DESP_PM_GPIO_HOLD' \
|
||||
make BOARD=esp32-wroom-32 -C tests/periph_pm
|
||||
make BOARD=esp32-wroom-32 -C tests/periph/pm
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
[Back to table of contents](#esp32_toc)
|
||||
|
@ -89,7 +89,7 @@ int uart_mode(uart_t uart, uart_data_bits_t data_bits, uart_parity_t uart_parity
|
||||
* transferred with a single 32 bit write (updating both parity and number of data bits at the
|
||||
* same time), the configuration change of the parity bits will not take place until after the
|
||||
* next char send out. If the configuration is updated in multiple bus accesses, it will apply
|
||||
* directly to the next char. So: Double check e.g. with tests/periph_uart_mode after touching
|
||||
* directly to the next char. So: Double check e.g. with tests/periph/uart_mode after touching
|
||||
* the initialization code here */
|
||||
dev->UARTLCR_H = (uint32_t)data_bits << UART0_UARTLCR_H_WLEN_Pos;
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
# Arduino peripheral GPIO Test
|
||||
|
||||
This test is designed for testing the Arduino to RIOT pin mapping
|
||||
on boards with Arduino support. It is much like tests/periph_gpio
|
||||
on boards with Arduino support. It is much like tests/periph/gpio
|
||||
but for Arduino pin numbers.
|
||||
|
||||
In this test, pins are specified by integer pin numbers.
|
||||
|
@ -20,5 +20,5 @@ LEN - The length to read or write.</br>
|
||||
FLAG - Flags set for the I2C, more information is available in driver/include/periph/i2c.h
|
||||
|
||||
_note: Automated tests can be found in the
|
||||
[RobotFW-tests](https://github.com/RIOT-OS/RobotFW-tests/tree/master/tests/periph_i2c)
|
||||
[RobotFW-tests](https://github.com/RIOT-OS/RobotFW-tests/tree/master/tests/periph/i2c)
|
||||
repository_
|
||||
|
@ -16,7 +16,7 @@ set RTT_MIN_OFFSET to the value found out with this test + 1tick.
|
||||
|
||||
## Usage
|
||||
|
||||
Run `BOARD=<board> make -C tests/periph_rtt_min/ flash test` the value will
|
||||
Run `BOARD=<board> make -C tests/periph/rtt_min/ flash test` the value will
|
||||
be printed as:
|
||||
|
||||
```
|
||||
|
@ -1,3 +1,3 @@
|
||||
_note Automated tests can be found in the
|
||||
[RobotFW-tests](https://github.com/RIOT-OS/RobotFW-tests/tree/master/tests/periph_uart)
|
||||
[RobotFW-tests](https://github.com/RIOT-OS/RobotFW-tests/tree/master/tests/periph/uart)
|
||||
repository_
|
||||
|
Loading…
Reference in New Issue
Block a user