The connected emulator does not support serial wire output (SWO)

RE: The connected emulator does not support serial wire output (SWO)

Nguyen Hoan Hoang — Tue, 02 Sep 2014 23:11:42 GMT

How many break points did you set ? try with max of 3 first, see how it goes. I remember sometimes Eclipse does that when I set more than the max breakpoints supported by the jtag probe. Some are limited to 4 max. I think the lite version has that limit.

RE: The connected emulator does not support serial wire output (SWO)

Jeffrey Tang — Tue, 02 Sep 2014 21:25:15 GMT

Relative discusson on launchpad

answers.launchpad.net/.../240419

RE: The connected emulator does not support serial wire output (SWO)

Jeffrey Tang — Tue, 02 Sep 2014 21:05:58 GMT

Hi,

I tried rebuild the project and make no difference.

After searching developerZone, it seems my problem is actually the same as this one(Not be able to stop at breakpoint):

devzone.nordicsemi.com/.../

But I tried Hung Bui's approach and but not working for me.

RE: The connected emulator does not support serial wire output (SWO)

Nguyen Hoan Hoang — Tue, 02 Sep 2014 20:43:57 GMT

I saw this happened when the code was not compiled with Debug info or source is out of sync. Other than that, don't what else it could be. Try to do a clean and build.

RE: The connected emulator does not support serial wire output (SWO)

Jeffrey Tang — Tue, 02 Sep 2014 20:03:53 GMT

The program does run withou crash, since I could use an iOS App to discover and connect with the BLE evaluation boards.

It seems a bug of Eclipse or GNU ARM Plug-in. For example, if I set breakpoint at line 1239 rtc1_init();

At assembly window, it shows the breakpoint is at 1239 rtc1_init(), which is just source code inserted into assembly window, instead of at the real true instruction address 0x1c810: bl 0x1d314 rtc1_init

If I set breakpoint at assembly window address 0x1c810, Eclipse & GDB can stop at the address without problem

Source Window

Assembly Window

My debug configuration for Source Tab

My Console Output during debug

I switched my GNU ARM tool chain from 4.7 2013q1 to 4.8 2014q2, and the problem got solved (hopefully )

Per the discussion here,

answers.launchpad.net/.../240419

it seems when gcc uses relative path to compile and link the source codes, the build output contains the relative path, somehow, some GDB version can only resolve absolute path and will not be able to add breakpoint since it could not find the source file.

RE: The connected emulator does not support serial wire output (SWO)

Nguyen Hoan Hoang — Tue, 02 Sep 2014 19:24:06 GMT

your program most likely crashes before reaching main. Find your ResetEntry function and put a breakpoint there. It should stop there if your Eclipse setup works correctly.

RE: The connected emulator does not support serial wire output (SWO)

Nikita — Tue, 02 Sep 2014 19:16:48 GMT

There is no SWO in nRF51822, see this.

Don't know about breakpoint problem, but if you're using softdevice then see this.