Problem running/debugging nRF51822 GCC example project

RE: Problem running/debugging nRF51822 GCC example project

crossd1111 — Mon, 01 Jun 2015 02:22:31 GMT

I struggled with this issue for hours. The root cause was that "Skip All Breakpoints" was enabled in the Run menu of eclipse. Either this was the default installation option or I enabled it inadvertently.

RE: Problem running/debugging nRF51822 GCC example project

Omnia — Tue, 31 Mar 2015 16:00:40 GMT

hi, "mon speed 10000" should be "mon speed 1000"

RE: Problem running/debugging nRF51822 GCC example project

Lucas — Fri, 12 Dec 2014 02:24:03 GMT

This resolved my issue. Thank you mike.

RE: Problem running/debugging nRF51822 GCC example project

Nguyen Hoan Hoang — Sat, 02 Aug 2014 02:27:44 GMT

Hi,

I have compiled all the links I found to properly setup Eclipse with hardware debugging using Jlink or OpenOCD. It's all on my page here embeddedsoftdev.blogspot.ca/.../eclipse.html These are generic setup that will work for any ARM development. Works well with Jlink and nRF51. DO NOT follow NAN-29, it will get you into a mess. I have hrs pure Eclipse project that works with SD7 (no makefiles). Let me know if you want it.

PS. works for any platform OSX, Windows, Linux

RE: Problem running/debugging nRF51822 GCC example project

Sergy — Fri, 01 Aug 2014 09:57:32 GMT

Hi,

how do I get Standard GDB debugger? I dont have it in the list of debuggers. Using Kepler Eclipse..

Also I have another warning: RMT ERROR : failed to get remote thread list.

Anybody knows what that is?

Thanks!

RE: Problem running/debugging nRF51822 GCC example project

Joe Merten — Thu, 20 Mar 2014 17:46:14 GMT

But note that the approach described in http://www.funwithelectronics.com/?id=168 uses wine. We really don't need wine to get nRF51822 debigging to get work under Linux and/or MacOS.

RE: Problem running/debugging nRF51822 GCC example project

Maik — Wed, 29 Jan 2014 17:15:54 GMT

I exaclty ran into the same mistake - do you already have a solution for that?

Symbol 'app_timer_evt_schedule' could not be resolved Symbol 'softdevice_evt_schedule' could not be resolved

RE: Problem running/debugging nRF51822 GCC example project

Arjun — Thu, 21 Nov 2013 02:29:58 GMT

I am using Evaluation kit for nRF51822. I am trying to build and run the program. But I am getting two errors APP_TIMER_INIT and BLE_STACK_HANDLER_INIT not resolved as well. I have no clue how to proceed further. If I ignore and try to debug then the debugger gets stuck at ble_stack_init(). I think this may be the reason for unresolved functions. Please help. I am using ble_app_hrs example

RE: Problem running/debugging nRF51822 GCC example project

Guest — Fri, 09 Aug 2013 05:49:34 GMT

Hi, there is this one guide on how to get Eclipse, GCC and the Nordic SDK working on a Linux machine. http://www.funwithelectronics.com/?id=168 I tried following it but didn't get very far. Maybe you'll have more luck.

RE: Problem running/debugging nRF51822 GCC example project

Bastiaan — Fri, 09 Aug 2013 05:49:34 GMT

RE: Problem running/debugging nRF51822 GCC example project

Bo Nystedt — Thu, 08 Aug 2013 09:06:46 GMT

Hi A year ago I tried hard to install "nRF51 Development with GCC and Eclipse (nAN-29) ver. 1.0 on an Ubuntu machine but had no success. Have now read somewhere that some people have succeded in the above mentioned task and got it running. I would appreciate the slightest hints where to get information so I do the same. I love to program with assembly instructions on Linux machines to create filters for signals in the time and frequency domains. Regards Bo

RE: Problem running/debugging nRF51822 GCC example project

Mike — Sat, 27 Jul 2013 02:04:14 GMT

And while ammending the debug instructions, also correct the 'mon speed 10000' line which should only read 1000, no?

RE: Problem running/debugging nRF51822 GCC example project

Mike — Sat, 27 Jul 2013 01:54:20 GMT

Yes, indeed, this is much better than the workaround for DSF I posted. With the standard debugger the memory view works now too!

I would suggest quickly ammending nAN29

RE: Problem running/debugging nRF51822 GCC example project

Mike — Sat, 27 Jul 2013 01:46:33 GMT

I'd like to contribute a workaround to at least one of these annoying issues, the "No source found". This is a common error, with common / simple solutions, but not in this case. Running gdb from the command line the source files are recognized, but not in the eclipse debugger.

The workaround for this was to simply an alternate / additional source lookup path, relative to source folder, as show in the attached screenshot.

I no longer get the "No source found" errors, and more importantly set breakpoints!

As for the unresolved __INLINE... that's less of an issue. From quick googling it seems similar errors are known and will likely "resolve themselves" in future CDT releases.

Capture.PNG

RE: Problem running/debugging nRF51822 GCC example project

Viktor — Thu, 25 Jul 2013 06:55:07 GMT

Everything seems to be working fine now :) Thanks for your support!

RE: Problem running/debugging nRF51822 GCC example project

Hung Bui — Wed, 24 Jul 2013 12:07:31 GMT

Hi Viktor,

We have been able to reproduce the same issue by update Eclipse to Kepler version. Before, I used Eclipse Juno as used in nAN29.

The workaround that worked for me on Kepler is to select "Standard GDB Hardware Debugging Launcher" instead of "GDB (DSF) Hardware Debugging Launcher" as stated in nAN29.

Could you please try and let me know the result ?

RE: Problem running/debugging nRF51822 GCC example project

Viktor — Wed, 24 Jul 2013 11:04:01 GMT

I have a little bit on new info: I have changed names of all the folders in the project, so that they contain no spaces, and I have set all the project file paths to be absolute. Some people have suggested that this helped them when getting the "No source file named XXX" error with GDB. Now instead of: No source file named C. I get the error: No source file named C:\Nordic-Semiconductor\nRF51-SDK\Nordic\nrf51822\Board\pca10001\blinky_example\main.c. Which is strange, as this file clearly exists.

RE: Problem running/debugging nRF51822 GCC example project

Viktor — Tue, 23 Jul 2013 12:41:41 GMT

The results with v4.74a are the same. Another thing of note is that after I halt the debug session, I can no longer see the device and I have to recover it using nRF Go studio before I can try another debug session.

RE: Problem running/debugging nRF51822 GCC example project

Hung Bui — Tue, 23 Jul 2013 12:11:12 GMT

I noticed that you are using GDB beta version. Could you upgrade to the latest version, v4.74a ? www.segger.com/jlink-software.html It seems the debugger reset the target after "...Breakpoint reached @ address 0x00015066"

RE: Problem running/debugging nRF51822 GCC example project

Viktor — Tue, 23 Jul 2013 11:31:22 GMT

Importing the paths from the other project helped, thanks! I'm sending the GDB log bellow. I ran the program through breakpoint set at buttons_init() - Nothing happened and the execution didn't stop. After that I pressed the halt button - In the log it's at the point right after Starting target CPU...

SEGGER J-Link GDB Server V4.73d (beta)

JLinkARM.dll V4.73d (DLL compiled Jul 10 2013 19:00:54)

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OB-SAM3U128 V1 compiled Feb 5 2013 15:27:51
Hardware: V1.00
S/N: XXXXXXXXX
Checking target voltage...
Listening on TCP/IP port 2331
Connecting to target...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00000000 (Data = 0x20001BD0)
JTAG speed set to 10000 kHz
Target endianess set to "little endian"
Flash download enabled
Selecting device: NRF51822
Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Downloading 16160 bytes @ address 0x00014000
Downloading 16112 bytes @ address 0x00017F20
Downloading 6436 bytes @ address 0x0001BE10
Downloading 8 bytes @ address 0x0001D734
Downloading 1116 bytes @ address 0x0001D73C
Writing register (PC = 0x0001caf5)
Read 4 bytes @ address 0x0001CAF4 (Data = 0x68024808)
Read 2 bytes @ address 0x00015066 (Data = 0xF7FF)
Read 2 bytes @ address 0x00015066 (Data = 0xF7FF)
Read 2 bytes @ address 0x00015066 (Data = 0xF7FF)
Setting breakpoint @ address 0x00015066, Size = 2, BPHandle = 0x0001
Starting target CPU...
...Breakpoint reached @ address 0x00015066
Reading all registers
Removing breakpoint @ address 0x00015066, Size = 2
Read 4 bytes @ address 0x00015066 (Data = 0xFAEDF7FF)
Reading 64 bytes @ address 0x20003FC0
Starting target CPU...
Debugger requested to halt target...
WARNING: CPU could not be halted
Reading all registers
ERROR: Can not read register 0 (R0) while CPU is running
ERROR: Can not read register 1 (R1) while CPU is running
ERROR: Can not read register 2 (R2) while CPU is running
ERROR: Can not read register 3 (R3) while CPU is running
ERROR: Can not read register 4 (R4) while CPU is running
ERROR: Can not read register 5 (R5) while CPU is running
ERROR: Can not read register 6 (R6) while CPU is running
ERROR: Can not read register 7 (R7) while CPU is running
ERROR: Can not read register 8 (R8) while CPU is running
ERROR: Can not read register 9 (R9) while CPU is running
ERROR: Can not read register 10 (R10) while CPU is running
ERROR: Can not read register 11 (R11) while CPU is running
ERROR: Can not read register 12 (R12) while CPU is running
ERROR: Can not read register 13 (R13) while CPU is running
ERROR: Can not read register 14 (R14) while CPU is running
ERROR: Can not read register 15 (R15) while CPU is running
ERROR: Can not read register 16 (XPSR) while CPU is running
ERROR: Can not read register 17 (MSP) while CPU is running
ERROR: Can not read register 18 (PSP) while CPU is running
ERROR: Can not read register 24 (PRIMASK) while CPU is running
ERROR: Can not read register 25 (BASEPRI) while CPU is running
ERROR: Can not read register 26 (FAULTMASK) while CPU is running
ERROR: Can not read register 27 (CONTROL) while CPU is running
ERROR: Can not read register 15 (R15) while CPU is running
Read 4 bytes @ address 0x00000000 (Data = 0x00000000)
GDB closed TCP/IP connection
Closing remote socket
Waiting for GDB connection...

RE: Problem running/debugging nRF51822 GCC example project

Hung Bui — Tue, 23 Jul 2013 11:00:40 GMT

Hi Viktor,

It seems it could be the gdb issue. I tried your project here without any problem.

Could you send us the GDB log when you debugging and trying to run through a break point ?

You can find in the attachment, the log when I tested your project here with a break point set at buttons_init().

Regarding your errors, you would need to add the paths to the C/C++ General ->Paths and Symbols -> Includes -> GNU C You can import the path from the ble_app_hrs project in the nRF6310 folder.

About the "could not be resolved" errors, it was the issue with eclipse when interpret __INLINE function. I think you can ignore the error for now.

gdb.PNG

RE: Problem running/debugging nRF51822 GCC example project

Viktor — Tue, 23 Jul 2013 06:37:48 GMT

Hi, thanks for the answer :) I made sure that I triple checked the Debug settings before I posted a question, so I think they should be correct. I'm sending screenshots of them anyway. Actually I made a different stupid mistake - I was trying to use the example project for the nRF Go board when I'm trying to develop for the PCA10001 :facepalm: . I fixed that now and wrote my own makefile for the PCA10001 ble_app_hrs example, since there is none provided. The program builds and runs fine, as far as I can tell, but the problems with debugging remain, as I described in my previous post. In fact, I am getting even more "could not be resolved" errors from Eclipse. I'm attaching my project files and a screenshot of all the errors too. I tried adding paths to all the included files, which give me errors, to project settings->C/C++ General->Paths and symbols->Includes but it didn't help. I'm using: ARM gcc ver. 4.7.4 GNU tools ARM embedded 4.7 2013q2 Eclipse Kepler Release, build id: 20130614-0229 SEGGER J-Link GDB server V4.73d Again, please let me know if you need more info.

Edit: Oh, and I should probably mention that I'm running Windows 7 Professional, Service pack 1

ble_app_hrs2.zip

RE: Problem running/debugging nRF51822 GCC example project

Hung Bui — Mon, 22 Jul 2013 12:45:34 GMT

Hi,

Could you upload your project files ( ble_app_hrs) folder and the screenshots when you configure GDB Hardware Debugging. Note that in Start up tab you would need to scroll down for more option.

Could double check that you followed properly Chapter 2 in the nAN29 App Note ? There is a little change in the path to ble_hrs_gcc_s110_xxaa.out so that _build folder is now under gcc folder.

Could you provide the version of gcc Arm, Eclipse and GDB server ?