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

[Kartik]

Hello fellow Nordic-ians,

I am developing a custom firmware for Nordic Thingy 52. I am using the Segger Embedded Studio as my IDE and J-link Edu Mini as the programmer / debugger for development.

When I "Build and Debug" the firmware on to thingy, I see that program execution does not reach main(). Instead it remains into some disassembly code and does not come out of it ever.

Request you to guide me on this.

Regards,

kthaore

[Andre]

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

[Kartik]

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?

[awneil]

Kartik said:

can I flash the softDevice Hex and application Hex file one after the other

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

Kartik said:

is there a mechanism to flash both the hex files in one go?

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.

[Kartik]

Thanks awneil for the quick reply !!!

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