This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Debugging nRF51 with Eclipse - Console shows binary garbage

Hi,

i am using Eclipse 'Mars' and Segger V5.10c to debug some of the SDK examples. The Eclipse command line shows only binary garbage. How can I get the garbage readable?

I used this guide to setup my working environment. Afterwards I able to compile the examples and run them. But whenever the console switches to 'SEGGER J-Link GDB Server V5.10c - Terminal output channel' there is only binary stuff on the command line: image description

My debug configuration:

image description

I have shortened the application to

int main(void)
{
    for (;;)
    {
    	int i = 1;
    	i += 1;
    }
}

but Eclipse still shows output on it's internal Terminal.

If I launch

JLinkGDBServer -device nrf51422 -if swd -speed 1000 -port 2331

and

arm-none-eabi-gdb nrf51422_xxac_s130.out
target remote localhost:2331
monitor reset
monitor device = nrf51422_xxac
continue

in the Terminal I am able to debug and there is no output in both Terminals.

  • Hi Florian,

    Could you update the question with a screen shot ? Also with some more description on your steps of testing.

  • Hi Florian,

    We haven't seen this before. Please make sure that GDB server path is correct (you can try to put the absolute address, instead of ${jlink_path..) Please let me know the gcc version you are using. And please update Segger Jlink to latest version.

    One thing you can try is to run GDB server separately and use the GDB client console arm-none-eabi-gdb.exe to debug. This way you don't need Eclipse and can rule out if the issue is with Eclipse. You can have a look here to know how to debug with arm-none-eabi-gdb.exe and Segger GDB server. You can use .axf file instead of the .elf file.

  • Hi again Florian,

    Sorry for late response, it's been busy lately.

    I noticed that you have Semihosting and SWV in the Console log, in my case and in the tutorial it was JLinkGDBServerCL.exe, maybe it was because you are using Linux.

    But what if you try to uncheck the check box for "Allocate console for semihosting and SWO" ? And were you able to stop at a break point ? Have you made sure you installed Cross compiler, J-link Debugging and Packs ? as described in "Setting up Eclipse the first time" ?

Related