Oh! I somehow missed that. Thanks, that's good enough for me. -- Björn

Hi, A couple things I find confusing: - There's only the ("beautified") output but not the commands that produced them as is typical in CI, so no obvious indication of what to do to test the next

Status is actually available as a comment in the PR. We are planning at some point to use the Checks API from GH which would make things more clear. The scripts now provide the output so you do not

The actual output is always available in a comment posted by zephyrbot in the same PR. The comment is updated for every run. Is this what you are looking for? Anas From:<devel@...> on behalf of

Hi Björn, I asked this question on Slack some time back and Anas answered it's not possible (yet?) for various reasons, one of them related to github accounts and security. Fortunately

Hi Aaron, This is indeed the expected way to do it. Don't forget to also add "arduino_i2c" in boards' yaml files. Cheers Erwan

Can we please make the "Details" links for these checks show the actual output of the check command, rather than the current generic information about why the check exists? -- Björn

Hi, Recently we enabled a new CI check that verifies if newly added files are covered in the CODEOWNERS file. For more information about the CODEOWNERS file please check

Hi, When I try to compile "samples\shields\x_nucleo_iks01a1\" for my Nordic dev. kits(pca10040 and pca10056), occurred this error: I noticed that the Arduino interface, like default i2c and so on, not

Hi Aaron, Thanks so much for reaching out regarding PR #13658. A comment has been added directly to the PR. Please feel free to reach out if you have any questions. Thank you for your contribution to

Hello, Please help me check this PR: https://github.com/zephyrproject-rtos/zephyr/pull/13658 I am not quite understanding those coverage item meaning, but I believe this patch will solve issue #13658,

Hi, Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.10.0-rc3 Please download and try things out and report any issues. Changes

Hi Johan, thanks - that's good to know for sure. No luck unfortunately, my device is still not responding after some time. I have set CONFIG_DEBUG=y and from my understanding the application seems to

255:bug 137:priority: medium 110:priority: low 8:priority: high 25:Coverity 20:area: Networking 17:area: Bluetooth 15:area: MISRA-C 14:platform: nRF 13:area: Logging 12:area: Kernel 11:platform:

Hello Tommy, You can look at the Bluetooth specification to learn more about DTM mode. I do not have any code or documents to share. You will have to dig into the zephyr source code to see how

Hi Ryan, The UART driver itself uses the GPIO driver internally so I don’t think there should be any issues with your usecase. Regards, Carles From:<devel@...> on behalf of Ryan

Hi Ryan Erickson, We would greatly appreciate it if you kindly give me some suggestions on the case. For example , What documents we can reference?Where can we find some relevant code?

Hello, I am using the NRF52840, UART1 with hardware flow control turned on. I want to be able to detect transitions on the CTS pin (input). Currently I tried using the GPIO driver to configure

Hi, Great! That should be enough. I had a couple of issues with openocd on an RV32M1 earlier on. The issue was related to selecting the boot mode and then flashing an application, , but I cannot

I pulled in some patches for