Merging HEX file with Softdevice

RE: Merging HEX file with Softdevice

Nicholas_Nuti — Thu, 27 Feb 2020 09:27:17 GMT

I tried it again and it worked. Something weird must have happened before. Thank you!

RE: Merging HEX file with Softdevice

Nicholas_Nuti — Thu, 27 Feb 2020 07:48:50 GMT

Hmm, that seemed to work.... I did the same exact thing and it didn't work for me. I'll try it once more.

Thank you so much Simon, I'll let you know if there are any more issues.

RE: Merging HEX file with Softdevice

Simonr — Thu, 27 Feb 2020 07:01:20 GMT

devzone.nordicsemi.com/.../ble_5F00_app_5F00_template_5F00_s140.hex
Hi

I merged the file with the s140 SoftDevice for you using the mergehex command, and it seems to be the correct size now. I don't know what the project is supposed to do, but it flashes onto the device without any errors, and the file memory layout seems to be correct.

Best regards,

Simon

RE: Merging HEX file with Softdevice

Nicholas_Nuti — Wed, 26 Feb 2020 18:13:41 GMT

Sorry, I forgot to note that I'm using SDK v16! Thank you.

RE: Merging HEX file with Softdevice

Nicholas_Nuti — Wed, 26 Feb 2020 18:10:26 GMT

Yes, I have 6 "../" s in my loader path to the softdevice hex file. I used the BLE app template and added the following: button press notification, client-side disconnect, and added the SIG battery service. My hex file is only 137 KB so I'm pretty sure the softdevice just isn't getting programmed.

RE: Merging HEX file with Softdevice

Simonr — Wed, 26 Feb 2020 06:40:04 GMT

Can you check that you have the correct number of "../" in your additional load file path? Would you mind sending me the .hex file so I could take a look here on my end? Can you also tell me what changes you've made to the original project and what SDK you are using?

Best regards,

Simon

RE: Merging HEX file with Softdevice

Nicholas_Nuti — Tue, 25 Feb 2020 20:09:25 GMT

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.

RE: Merging HEX file with Softdevice

Simonr — Tue, 25 Feb 2020 09:05:56 GMT

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