https://devzone.nordicsemi.com/f/nordic-q-a/69663/bug-in-ble_dtm-for-packet-lengths-0x3f-sdk-17-0-2Hi, We are in the middle of product certification, right now with BT SIG testing. Unfortunately we got stuck right away since the test house cant configure the device to use 255 bytes payload. We are using SDK 17.0.2. In ble_dtm.c:1305: en-USTelligent Community 13Mon, 22 Mar 2021 10:50:41 GMThttps://devzone.nordicsemi.com/thread/301164?ContentTypeID=1Mon, 22 Mar 2021 10:50:41 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3f5b8026-d21c-4c5c-8ed2-bd7298a4b284tesc<p>Hi,</p> <p>I can confirm the bug was exactly as reported, and it has since been fixed in our internal code base to be released on next nRF5 SDK release. (The boolean <code>&amp;&amp;</code> changed to a bitwise <code>&amp;</code>.)</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/285878?ContentTypeID=1Fri, 18 Dec 2020 15:02:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:18d7d0d0-e4d4-41a6-aef8-8fca4d0265actesc<p>Hi,</p> <p>Thank you for reporting this bug. It is highly appreciated!</p> <p>Yes. This indeed looks like a bug. I do not have in-depth knowledge of DTM nor the protocol used, but from variable naming, structure of the code, and overall appearance, this looks like a classical example of erroneously using &quot;boolean and&quot; instead of &quot;bitwise and&quot;. I have filed an internal bug report.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>