From 8c0363c79b261b750dbf5f3cf0bdc7ee8a11c651 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Damian=20Kr=C3=B3lik?= <66667989+Damian-Nordic@users.noreply.github.com> Date: Tue, 21 Jan 2025 17:42:04 +0100 Subject: [PATCH] [diag] correct usage of "diag frame" (#11179) The example for the "diag frame" command uses an invalid 802.15.4 frame while not bypassing the header and security processing with "-s" flag. In such a case, it cannot be guaranteed that the underlying platform will send such a frame if it can't parse the frame IEs to check if any dynamic data is to be injected. Switch to using a correct ACK frame. Signed-off-by: Damian Krolik --- src/core/diags/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/diags/README.md b/src/core/diags/README.md index 0e8896865..f51008d82 100644 --- a/src/core/diags/README.md +++ b/src/core/diags/README.md @@ -93,7 +93,7 @@ Set the frame (hex encoded) to be used by `diag send` and `diag repeat`. The fra - Specify `-u` to specify the `mInfo.mTxInfo.mIsHeaderUpdated` field for this frame. ```bash -> diag frame 11223344 +> diag frame 0200ffc0ba Done ```