https://devzone.nordicsemi.com/f/nordic-q-a/58362/is-ble-connectivity-fw-pre-installed-in-pca10059To the kind attention of Nordic support team, reading this https://devzone.nordicsemi.com/f/nordic-q-a/39630/windows-command-line-dfu-over-ble-with-pca10059 thread, I understood that PCA10059 comes pre programmed with USB bootloader and connectivityen-USTelligent Community 13Thu, 27 Feb 2020 02:03:04 GMThttps://devzone.nordicsemi.com/thread/236673?ContentTypeID=1Thu, 27 Feb 2020 02:03:04 GMT137ad170-7792-4731-bb38-c0d22fbe4515:19c10ac6-3150-492a-b8b1-f1fa4708401fdemcanulty<p>Hi astella, we just spent the last month figuring a lot of this out. &nbsp;The easiest place to find the compiled connectivity firmware is here in the pc ble driver releases: &nbsp;<a href="https://github.com/NordicSemiconductor/pc-ble-driver/releases">https://github.com/NordicSemiconductor/pc-ble-driver/releases</a><br /><br />Look in the share folder for hex files that are labeled with the soft device number. &nbsp;The files ending in pkg.zip are the PCA10059 packages and you need to use nrfutil to load them onto the dongle. &nbsp;<br /><br />nrfConnect (and the javascript library) uses sd_api_3, the python wrapper uses sd_api_5, and the pc ble driver C library is compatible with all of them that are available, but you have to make sure that you link the right soft device library in when you compile. &nbsp;<br /><br />If you want to find the actual code that is compiled to make the connectivity firmware for the pc-ble-driver, there are diff files in the pc-ble-driver repo, in the hex folder. &nbsp;The cmake script downloads the SDKs, saves them to a temp folder on your drive, then applies the diff file to the whole SDK. &nbsp;Then it compiles the to the hex and pkg.zip files that you see there in the release. &nbsp;<br /><br />It&#39;s all quite nifty when it works, but it can take a while to figure it when it doesn&#39;t. &nbsp;</p><div style="clear:both;"></div>