Merging HEX file with Softdevice

[Nicholas_Nuti]

Hello,

I can't get the hex file to come out correctly in segger studio. What happens is, I build the solution and create the hex file but when I go to program my device with it.... well the device doesn't work correctly. I added an output file in the linker to create a hex file, I added the softdevice s140 in the loader, and I even used the command line tools to try and merge the created hex file with the softdevice.... but the device does not function when programmed in this way. I can get the device to work perfectly when using "Build and run" on SES but when I try to manually download a created HEX file nothing works.

Thanks,

Nick

[Simonr]

Hi Nick

Please confirm that your output .hex file is found in this path in your computer: \SDK_FOLDER\examples\ble_peripheral\ble_app_uart\pca10056\s140\ses\Output\Release\Exe and that the SoftDevice is found in this path: \SDK_FOLDER\components\softdevice\s140\hex. 

Can you try using the nRFConnect for desktop Programmer app and drag the .hex files into the file memory layout there to see that everything looks okay visually? Can you also explain what exactly isn't going as expected when flashing the application and SoftDevice .hex files onto your chip?

Best regards,

Simon

[Nicholas_Nuti]

Both of those paths are exactly correct. I tried the nrfconnect programmer and it still didn't work.

What isn't going as expected is operation at all. I open up tera term to see if I get print outs and I don't. It also does not advertise.

The device works perfectly fine while programmed in SES but otherwise it does not.

For the "Set Additional Load File[0] -> ../../../../../../components/softdevice/s140/hex/s140_nrf52_7.0.1_softdevice.hex " as stated directly in the video. For some reason it doesn't have a MACRO for SDK directory.