Flashing nRF52DK pass but not running , J-Link and segger embedded studio

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Wed, 28 Nov 2018 01:45:27 GMT

Afer sometime i had to downgrade my OS to WIN7, reinstall the segger and got the activation licence , build and flashed in release mode. i donnot know what went right this time and didnot make changes to code or build configs other than the paths. It got fixed

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Fri, 31 Aug 2018 13:25:45 GMT

I understand.
But it is hard for me to be able to test your project, when all the .c and .h files aren't included in the example folder i downloaded from the dropbox-link.

However, when I removed the filesnot included in the dropbox folder from the project, compiled and flashed it, it worked just as expected. I flashed the program to my DK and it started advertising.

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Tue, 28 Aug 2018 06:34:30 GMT

Hi,

Those are my project files. I need them to be included for my device. It builds clean. So the flashing should be fine. How would I be able to flash with my own modifications.

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Tue, 14 Aug 2018 06:32:16 GMT

Hi!

There seems to be more changes to the project than only the broadcasting name.

There is also files included in the project that isn't included in your folder (lamp.c, lamp.h, rdm.c).

Once I removed all the files that was not included in your folder etc. The example runs just fine. I can flash the example and it runs just as expected, no need to start the debug session.

Maybe you could try to copy the main.c file of your modified example to the stock ble_app_uart example, and then build and flash it?

Also, I would not recommend using the nrfx_coredep_delay_us() as you do in your project. This will halt the MCU and delay execution.
This means that you will not be able to connect, advertise etc. as long as the delay-function is active. I would suggest using a timer instead.

Regards.

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Wed, 08 Aug 2018 10:43:01 GMT

Hi,

attaching the drop box link here : www.dropbox.com/.../source.7z

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Tue, 07 Aug 2018 11:56:01 GMT

I actually asked you in a previous comment about any modifications to the code, where you said that no changes were made.
Changing the advertisment name is the only change from the original example?

I would assume that the issue is related to the modification you made to the code.

Maybe you could upload your project, so that I can test this myself?

Best regards,
Joakim

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Mon, 06 Aug 2018 01:38:14 GMT

Hi,

I tried to merge the ble_hex from the sample with s132_nrf52_6.1.0_softdevice.hex, it works great. But when I do the same for my application hex, the merge is happening, but the application is not running. My application is also based on ble_app_uart_sample, it was not modified much, just the broadcast name.My application works well when through IDE debugging.

Best Regards,

Nihadh

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Tue, 31 Jul 2018 11:34:47 GMT

Ah ok! Then I misunderstood you.

The ble_app_uart_pca10040_s132.hex file is the unmodified ble_app_uart application, merged with the softdevice.
Hence, you do not need to merge that with the softdevice.

When you build your application, i.e in SES, there will be generated a hex-file that contains only the application.
When using SES, this hex-file can be found in:
examples/ble_peripheral/ble_app_uart/pca10040/s132/ses/Output/Debug(or Release, depending on what configuration you are using)/Exe

You should use that hex file and merge it with the softdevice.

Let me know if you still face any issues.
Best regards,
Joakim.

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Tue, 31 Jul 2018 08:48:08 GMT

Hi,

I have built my application. But my application.hex needs to be merged with s132 hex, so i tried to merge with ble_app_uart_pca10040_s132.hex, But is this the correct way or should I use other softdevice hex.

Anywasy I tried to merge with the ble_app_uart_pca10040_s132.hex, but I get the conflict error

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Tue, 31 Jul 2018 08:01:13 GMT

Hi!

You can use the mergehex executable, which is a part of the nRF5x Command Line Tools.

Merging files with mergehex

If you have any further questions, please let me know.

Best regards,
Joakim

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Tue, 31 Jul 2018 02:36:23 GMT

Hi Joakim,

Thanks for the inuput. I tried flashig the sample application nfrjprog uility and it works. previously I was merging the ble_app_uart_pca10040_s132.hex with generated application.hex, I think my merging was wrong, when I try to flash using nrfjprog.

I am building my custom application, can you suggest a way to merge my application.hex and softdevice.hex(I think this has to be raw not including any application) and flash using nrjprog. I am getting conflicts on merge

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Mon, 30 Jul 2018 13:25:24 GMT

So the pre-compiled hex file: ble_app_uart_pca10040_s132.hex didn't work either?

Note that this hex-file contains both the softdevice and the application, so you don't need to flash the softdevice first.

SDK15 should not be "unstable". I don't know about any known issues with the the ble_app_uart example in SDK15.

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Nihadh — Mon, 30 Jul 2018 08:06:14 GMT

Hi Joakim,

Thanks for the reply. I didnot make any changes to the code. I tried flashing them. I was using this "ble_app_uart_pca10040_s132.hex". is the SDK15 unstable any problem over my interface. I am using J-Link over USB.

Best Regards,

Nihadh

RE: Flashing nRF52DK pass but not running , J-Link and segger embedded studio

Joakim Jakobsen — Mon, 30 Jul 2018 07:15:03 GMT

Hi!

I don't have any problems with the ble_app_uart example from SDK 15.

Did you make any modifications or changes at all to the code?
Could you test the pre-compiled hex file in the SDK? You should find this in the;
sdk_folder/examples/ble_peripheral/ble_app_uart/hex/ble_app_uart_pca10040_s132.hex

[quote user=""] I also checked whether I am flashing the soft_devices.hex its getting flashed.[/quote]

Which version of the softdevice are you using?

Best regards.