From e176f1d3384464631661c74082dd61f105590042 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=2E=20David=20Ib=C3=A1=C3=B1ez?= Date: Thu, 19 Jan 2023 10:42:50 +0100 Subject: [PATCH] tests/periph_spi clearly say when init succeeds The way it's now it's easy to interpret that there was an error, when really there was not. As seen in issue #19025 quite some time can be spent following a wrong clue. --- tests/periph_spi/main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/periph_spi/main.c b/tests/periph_spi/main.c index 557fef2334..b390239ea3 100644 --- a/tests/periph_spi/main.c +++ b/tests/periph_spi/main.c @@ -217,9 +217,11 @@ int cmd_init(int argc, char **argv) else { printf("Trying to initialize SPI_DEV(%i): mode: %i, clk: %i, cs_port: %i, cs_pin: %i\n", dev, mode, clk, port, pin); - puts("Note: Failed assertion (crash) means configuration not supported"); + puts("(if below the program crashes with a failed assertion, then it means the" + " configuration is not supported)"); spi_acquire(spiconf.dev, spiconf.cs, spiconf.mode, spiconf.clk); spi_release(spiconf.dev); + puts("Success."); } return 0;