RE: What is sd-id 0xCAFE?

Collin — Mon, 03 Jun 2019 21:47:37 GMT

Thanks for the answer, makes sense about the scripts.

Another note, I found that the DFU bootloader will not accept a softDevice package with sd-req 0xFFFE, since it is not running a softDevice. So, the first time I run a board, the UART DFU needs sd-req of the softDevice package to be 0.

RE: What is sd-id 0xCAFE?

bjorn-spockeli — Mon, 03 Jun 2019 13:34:36 GMT

HI Collin,

0xCAFE is the FWID used for alpha versions of the SoftDevice.

If you set the sd-req to 0xFFFE, then the bootloader will accept any SoftDevice.

/** @brief SD_REQ_ANY_VERSION field value which indicates that any SoftDevice version is valid. 
 *
 * @note This is used by external application in case SoftDevice version compatibility isn't needed.
 */
#define SD_REQ_ANY_VERSION (0xFFFE)

I also checked the softdevice and application test images in nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_dfu_test_images\ble\nrf52832 and they do indeed set 0xAF as the sd-req. This is incorrect and should have been 0xB7 as you have correctly pointed out. My guess is that this is due to the scripts creating the images not being updated from SDK v15.2.0 ( which used S132 v6.1.0) to SDK v15.3.0.

I will report this internally.

Best regards

Bjørn