Debug nRF52840-PDK with arm-none-eabi-gdb

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Sridhar Jonnavittula — Tue, 19 Jun 2018 09:13:14 GMT

Hi,

I followed the above method but when I hit CTRL+C suppose in order to keep another break point error ASM for breakpoint is showing up as below screenshot

Please help.

Thanks

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Jørgen Holmefjord — Wed, 07 Mar 2018 13:48:52 GMT

Yes, this is correct. There is no JTAG on the nRF5x devices, we use SWD interface.

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Attilio Dona' — Sat, 03 Mar 2018 14:05:40 GMT

The doubt is not about the meaning of reset ...

For what I understand the ble_stack_init has to be invoked in a well know state otherwise it throws an hard fault.

This is valid for loading from JTAG and also from firmware update from OTA.

Is it right my understanding?

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Jørgen Holmefjord — Thu, 01 Mar 2018 09:21:19 GMT

The monitor reset command will reset the chip, to make sure it is in a known state.

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Attilio Dona' — Wed, 28 Feb 2018 17:00:03 GMT

Hi Jorgen,

Yes, I've flashed with s140_nrf52840_5.0.0-2.alpha_softdevice.hex.

Meantime I have discovered that executing a monitor reset after the load command resolve the problem.

The question now is: what is the reason of this behavoir?

Many thanks

Attilio

RE: Debug nRF52840-PDK with arm-none-eabi-gdb

Jørgen Holmefjord — Wed, 28 Feb 2018 15:19:26 GMT

Hi,

It looks like you are getting hardfaults in your application. Did you flash the softdevice along the application?

Best regards,
Jørgen