patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 7 Packages Projects Releases Wiki Activity
zephyr/samples/net/sockets/can/sample.yaml

38 lines
1.1 KiB
YAML
Raw Normal View History

samples: can: filter out tests if zephyr,canbus not enabled - Filter out the remaining CAN tests if no zephyr,canbus chosen node is enabled in the devicetree. - Rename the tests to shorten the name a bit. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-23 16:31:28 +01:00
sample:
name: SocketCAN sample
samples: net: can: Add socket CAN sample Simple socket CAN application that sends data periodically and receives the data back. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-01-23 12:41:44 +01:00
common:
samples, tests: convert string-based twister lists to YAML lists Twister now supports using YAML lists for all fields that were written as space-separated lists. Used twister_to_list.py script. Some artifacts on string length are due to how ruamel dumps content. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2023-05-08 13:37:42 +02:00
tags:
- net
- socket
- can
drivers: can: skip all CAN loopback mode tests for kvaser,pcican Skip all CAN controller tests utilizing CAN loopback mode for the kvaser,pcican CAN controller card as emulated in QEMU. QEMU emulation of the SJA1000 CAN controller backend does not yet support the SJA1000 Self Reception Request command which is required for proper loopback operation. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2022-10-28 13:28:31 +02:00
filter: dt_chosen_enabled("zephyr,canbus") and not dt_compat_enabled("kvaser,pcican")
samples: net: can: Add socket CAN sample Simple socket CAN application that sends data periodically and receives the data back. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-01-23 12:41:44 +01:00
depends_on: can
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
harness: console
samples: net: Disable native_posix target in more samples The native_posix compilations fail with various socket errors like this: samples/net/sockets/can/src/main.c:65:9: error: implicit \ declaration of function ‘send’ [-Werror=implicit-function-declaration] 65 | ret = send(fd, &sframe, sizeof(sframe), 0); | ^~~~ So disable the native_posix board from networking samples as native_posix board is not compatible with CONFIG_POSIX_API This is related to commit b8fc1c4c3e ("samples: net: Disable native_posix target in samples") but disables more network samples for native_posix board. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-04-15 10:02:41 +02:00
# native_posix does not work with CONFIG_POSIX_API
platform_exclude:
- native_posix
- native_posix/native/64
samples: net: can: Add socket CAN sample Simple socket CAN application that sends data periodically and receives the data back. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-01-23 12:41:44 +01:00
tests:
samples: can: filter out tests if zephyr,canbus not enabled - Filter out the remaining CAN tests if no zephyr,canbus chosen node is enabled in the devicetree. - Rename the tests to shorten the name a bit. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-23 16:31:28 +01:00
sample.net.sockets.can.one_socket:
samples: net: can: Add second RX socket receiver This is done so that we can test socket CAN dispatcher. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-02-13 16:11:51 +01:00
extra_configs:
- CONFIG_NET_SOCKETS_CAN_RECEIVERS=1
samples: net: sockets: can: Fix the test termination criteria If enabling CONFIG_POSIX_API, we get three file descriptors open before any socket descriptors. The sample exit criteria checks socket 0 and 1 which is no longer a valid one, so change the check to be either 0 or 3, and 1 or 4 so that the test can be run in both when POSIX API is enabled or disabled. Also disable color printing for the test run so that it is easier to read the output log. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-03-10 09:40:10 +01:00
- CONFIG_LOG_BACKEND_SHOW_COLOR=n
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
harness_config:
type: multi_line
yamllint: fix all yamllint truthy errors Fix all thruthy errors detected by yamllint: yamllint -f parsable -c .yamllint $( find -regex '.*\.y[a]*ml' ) | \ grep '(truthy)' This only accepts true/false for boolean properties. Seems like python takes all sort of formats: https://github.com/yaml/pyyaml/blob/master/lib/yaml/constructor.py#L224-L235 But the current specs only mention "true" or "false" https://yaml.org/spec/1.2.2/#10212-boolean Which is the standard yamllint config. Excluding codeconv and workflow files, as some are using yes/no instead in the respective documentation. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-01-03 12:23:56 +01:00
ordered: true
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
regex:
samples: net: sockets: can: Fix the test termination criteria If enabling CONFIG_POSIX_API, we get three file descriptors open before any socket descriptors. The sample exit criteria checks socket 0 and 1 which is no longer a valid one, so change the check to be either 0 or 3, and 1 or 4 so that the test can be run in both when POSIX API is enabled or disabled. Also disable color printing for the test run so that it is easier to read the output log. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-03-10 09:40:10 +01:00
- "(.*)\\[0|3\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
- "(.*)f0 f1 f2 f3 f4 f5 f6 f7"
samples: can: filter out tests if zephyr,canbus not enabled - Filter out the remaining CAN tests if no zephyr,canbus chosen node is enabled in the devicetree. - Rename the tests to shorten the name a bit. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-02-23 16:31:28 +01:00
sample.net.sockets.can.two_sockets:
samples: net: can: Add second RX socket receiver This is done so that we can test socket CAN dispatcher. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2019-02-13 16:11:51 +01:00
extra_configs:
- CONFIG_NET_SOCKETS_CAN_RECEIVERS=2
samples: net: sockets: can: Fix the test termination criteria If enabling CONFIG_POSIX_API, we get three file descriptors open before any socket descriptors. The sample exit criteria checks socket 0 and 1 which is no longer a valid one, so change the check to be either 0 or 3, and 1 or 4 so that the test can be run in both when POSIX API is enabled or disabled. Also disable color printing for the test run so that it is easier to read the output log. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-03-10 09:40:10 +01:00
- CONFIG_LOG_BACKEND_SHOW_COLOR=n
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
harness_config:
type: multi_line
yamllint: fix all yamllint truthy errors Fix all thruthy errors detected by yamllint: yamllint -f parsable -c .yamllint $( find -regex '.*\.y[a]*ml' ) | \ grep '(truthy)' This only accepts true/false for boolean properties. Seems like python takes all sort of formats: https://github.com/yaml/pyyaml/blob/master/lib/yaml/constructor.py#L224-L235 But the current specs only mention "true" or "false" https://yaml.org/spec/1.2.2/#10212-boolean Which is the standard yamllint config. Excluding codeconv and workflow files, as some are using yes/no instead in the respective documentation. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-01-03 12:23:56 +01:00
ordered: true
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
regex:
samples: net: sockets: can: Fix the test termination criteria If enabling CONFIG_POSIX_API, we get three file descriptors open before any socket descriptors. The sample exit criteria checks socket 0 and 1 which is no longer a valid one, so change the check to be either 0 or 3, and 1 or 4 so that the test can be run in both when POSIX API is enabled or disabled. Also disable color printing for the test run so that it is easier to read the output log. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-03-10 09:40:10 +01:00
- "(.*)\\[0|3\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
- "(.*)f0 f1 f2 f3 f4 f5 f6 f7"
samples: net: sockets: can: Fix the test termination criteria If enabling CONFIG_POSIX_API, we get three file descriptors open before any socket descriptors. The sample exit criteria checks socket 0 and 1 which is no longer a valid one, so change the check to be either 0 or 3, and 1 or 4 so that the test can be run in both when POSIX API is enabled or disabled. Also disable color printing for the test run so that it is easier to read the output log. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-03-10 09:40:10 +01:00
- "(.*)\\[1|4\\] CAN frame: IDE 0x0 RTR 0x0 ID 0x1 DLC 0x8"
samples: net: sockets: can: add console harness configuration Add a console harness for validating the output from the SocketCAN sample. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2022-07-18 10:23:18 +02:00
- "(.*)f0 f1 f2 f3 f4 f5 f6 f7"
Reference in a new issue Copy permalink