Project export

Question

I've modified an example project. 
 How do I go about exporting it, so that I can share it with other devs and they can then flash the same program onto their Development Kit?

Einar Thorsrud · Accepted Answer

Hi, If you just want to share them firmware you have built, then you must get the hex file of the application you built, and any dependencies (such as SoftDevice). For instance building the ble_app_hrs example from the nRF5 SDK for the nRF52 DK and using the S132 SoftDevice, you must get the application from your build folder (for instance if you are using SES: \examples\ble_peripheral\ble_app_hrs\pca10040\s132\ses\Output\Release\Exe\) and find the application ble_app_hrs_pca10040_s132.hex. You would also need to share the SoftDevice hex in this case, which you find under \components\softdevice\s132\hex\ (adjust path if using something other than S132). You can then give the other person these two files and ask him/her to program using for instance nRF Connect Programmer . (You can also merge them first with mergehex if you only want to provide a single file). If you want to share the project and not just the hex file it depends a bit on SDK version and toolchain. If you are using the nRF5 SDK and your projects are similar to the SDK examples, then exporting would simply be to remove build files from your project folder, and share the rest of the files in that folder. So, just referring to an example, if your project was the ble_app_hrs example for the nRF52 DK (PCA10040) and you are using SES, then you would copy the \examples\ble_peripheral\ble_app_hrs\ folder and remove other irrelevant files, so you would essentially have this layout ( 3482.ble_app_hrs.zip ): └───ble_app_hrs │ main.c │ └───pca10040 └───s132 ├───config │ sdk_config.h │ └───ses ble_app_hrs_pca10040_s132.emProject flash_placement.xml Anny additional files you get when building etc. is not needed.

Project export

Top Replies