Debugging custom thingy FW with J-link edu mini using SES but execution does not reach main()

RE: Debugging custom thingy FW with J-link edu mini using SES but execution does not reach main()

Kartik — Thu, 04 Jul 2019 09:36:44 GMT

Thanks awneil for the quick reply !!!

I will try out this mechanism and verify the answer on success.

RE: Debugging custom thingy FW with J-link edu mini using SES but execution does not reach main()

awneil — Thu, 04 Jul 2019 08:47:15 GMT

[quote userid="80855" url="~/f/nordic-q-a/49350/debugging-custom-thingy-fw-with-j-link-edu-mini-using-ses-but-execution-does-not-reach-main/196429"]can I flash the softDevice Hex and application Hex file one after the other[/quote]

Yes - just make sure you don't do an 'Erase All' between!

[quote userid="80855" url="~/f/nordic-q-a/49350/debugging-custom-thingy-fw-with-j-link-edu-mini-using-ses-but-execution-does-not-reach-main/196429"]is there a mechanism to flash both the hex files in one go?[/quote]

You can merge the 2 hexfiles into one:

https://infocenter.nordicsemi.com/topic/ug_nrf5x_cltools/UG/cltools/nrf5x_mergehex.html

However, once programmed, there is really no reason to keep re-programming the SoftDevice - it just wastes time.

RE: Debugging custom thingy FW with J-link edu mini using SES but execution does not reach main()

Kartik — Thu, 04 Jul 2019 08:41:27 GMT

Thanks Andre for the vital comment. Oh Yes, it would require a soft device too !!

So, can I flash the softDevice Hex and application Hex file one after the other using J-Flash tool to make it work?

Or is there a mechanism to flash both the hex files in one go? What is the recommended procedure to achieve this?

RE: Debugging custom thingy FW with J-link edu mini using SES but execution does not reach main()

Andre — Thu, 04 Jul 2019 07:53:36 GMT

Does your custom firmware require a SoftDevice? If so, verify the correct version of the SoftDevice has been flashed