Update to S310 V2.0.1 can't debugg

RE: Update to S310 V2.0.1 can't debugg

Frederic — Fri, 23 Jan 2015 14:54:30 GMT

I can debug now after I read the following pages: devzone.nordicsemi.com/.../ devzone.nordicsemi.com/.../ devzone.nordicsemi.com/.../

With the debugg setting "Set program counter at (hex)" 0x0006D1 for S310 V2.0.1, i can debugg now (description of the first link). Not perfect but works for the moment.

Thanks to all who have helped me :-)

RE: Update to S310 V2.0.1 can't debugg

Frederic — Fri, 23 Jan 2015 12:14:14 GMT

Without -flto -fno-builtin, same behavior as before. If i start a debugg session the main function is never reached. If i suspend the debugg session, the application is in HardFault Handler. After a power on cycle (without debugging) the program starts normal.

Very strange, perhaps something in Softdevice has changed and i have to adjust my debugging settings but i don't know which settings I must adjust.

RE: Update to S310 V2.0.1 can't debugg

Vidar Berg — Fri, 23 Jan 2015 11:16:00 GMT

Try to comment out the -flto optimization as well. Otherwise the debug symbols will be removed from the compile: #CFLAGS += -flto -fno-builtin

RE: Update to S310 V2.0.1 can't debugg

Frederic — Fri, 23 Jan 2015 11:08:06 GMT

If i flash the S310 V2.0.1 and my application with nRFgo Studio the application start normal and BLE/ANT advertising normal. But debugging with Eclipse doesn't work. If i use S310 V1.0.0 with the same debugging settings all works fine.

RE: Update to S310 V2.0.1 can't debugg

Vidar Berg — Thu, 15 Jan 2015 13:29:13 GMT

I suggest you try the ble_ant_app_hrm and see if it works on your end with the same changes in order to narrow down the problem.

RE: Update to S310 V2.0.1 can't debugg

Frederic — Thu, 15 Jan 2015 12:45:20 GMT

Hi Vidar, yes i already use compiler option -g3 -O0 to debug my software. If i program the S310 V1.0.0 with the corresponding header files and RAM/ROM areas all works fine. If i program the S310 V2.0.1 with the corresponding header files and RAM/ROM areas the application don't run at all. I don't now what i'm doing wrong.

RE: Update to S310 V2.0.1 can't debugg

Vidar Berg — Thu, 15 Jan 2015 09:50:37 GMT

The new S310 can be used in SDK 6.1 by following the migration guide you mentioned, and from you description it sounds like you have done all the necessary steps.

I tried here on my end with the ble_ant_app_hrm from SDK 6.1 compiled with gcc for s310 v.2.0.1. It worked after replacing the API headers, adjusted flash size, and added the sd_ble_enable call().

For debugging part, did you remember to set compiler option -g3, and also remove -O3? This is something at least I've missed before as I'm used to the makefile.common used in most of the SDK 6 examples.

RE: Update to S310 V2.0.1 can't debugg

Matt Barr — Wed, 14 Jan 2015 17:28:41 GMT

Hi Frederic, I don't use that tool chain so I can't help you with the loader output. Your question about the new s310 and 6.1 SDK is a good one. I moved to the v7.0.1 SDK and v2.0.0 s310 at the same time and never attempted to use the new s310 with the old SDK. Perhaps you have a solid reason for sticking with the old SDK, but the v7.1.0 SDK does contain some example s310 projects. It may be time to take the plunge!

RE: Update to S310 V2.0.1 can't debugg

Frederic — Wed, 14 Jan 2015 16:53:03 GMT

yes, i call sd_ble_enable() after SOFDEVICE_HANDLER_INIT(). The application does not run, i can't reach my breakpoint at the beginning from the main function.

GDB Server output: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.

Downloading 16080 bytes @ address 0x0001D000

Downloading 16080 bytes @ address 0x00020ED0

Downloading 10792 bytes @ address 0x00024DA0

Downloading 8 bytes @ address 0x000277C8

Downloading 136 bytes @ address 0x000277D0

Writing register (PC = 0x00021c05)

Read 4 bytes @ address 0x00021C04 (Data = 0x480A2103)

Read 2 bytes @ address 0x0001D460 (Data = 0xF7FF)

Setting breakpoint @ address 0x0001D460, Size = 2, BPHandle = 0x0001

Starting target CPU...

...Target halted (PC = 0xFFFFFFFE)

Reading all registers

Removing breakpoint @ address 0x0001D460, Size = 2

Read 4 bytes @ address 0xFFFFFFFE (Data = 0x5F8ACD5B)

Read 4 bytes @ address 0x000007BC (Data = 0x00001000)

Reading 64 bytes @ address 0x00000780

Read 4 bytes @ address 0x00000C00 (Data = 0xFFFFFFFF)

Read 4 bytes @ address 0xFFFFFFFF (Data = 0xFFFFFFFF)

Read 4 bytes @ address 0xE7F8461C (Data = 0x00000000)

RE: Update to S310 V2.0.1 can't debugg

Matt Barr — Wed, 14 Jan 2015 16:37:30 GMT

Are you calling sd_ble_enable() after SOFDEVICE_HANDLER_INIT()? As I recall this wasn't necessary with the v1.x S310, but with v2.x this initialization is the same as the S110. This section of code was typically surrounded by "#ifdef S110 ... #endif" in the v6.1 SDK example S310 projects, e.g. main.c in ble_app_hrs.