SDK 8.1 debugging fail

RE: SDK 8.1 debugging fail

Kyu — Thu, 21 May 2015 06:59:45 GMT

This problem is solved!

The problem is from project target.

I am using uvision5.

But I opened the uvision4 project. \arm4...

Now I am using the example under \arm5_no_packs, and every things work well!!

I hope other developer don't make this mistake like me..

RE: SDK 8.1 debugging fail

MartinBL — Wed, 20 May 2015 11:35:49 GMT

So now you are able to program you example onto your board, but not debug? Can you see that the example is actually working (without running in debug mode)? Would it help to turn down the Optimization level to 0? The example works fine on my PCA10001 board, but it is a little hard to follow the debugger when Optimization is set to level 3. Setting it to 0 makes it easier.

RE: SDK 8.1 debugging fail

Kyu — Wed, 20 May 2015 07:07:17 GMT

this problem is happen when I test it with pca10001. I guess it occurs from RAM size because of new softDevice(8.0.0), and this example target 51422AC but my chip is 51822AA.

RE: SDK 8.1 debugging fail

Kyu — Wed, 20 May 2015 01:45:18 GMT

I can download well.

But I can not debug.

My board is power on, and every line is not disconnected.

This is my debugger set up.

[edit] I put the programming algorithm.

debugging mode is started now.

But I think address range is not fit.

It doesn't start from main function.

RE: SDK 8.1 debugging fail

Nick Pelis — Tue, 19 May 2015 17:40:57 GMT

I get this message too when my custom board is unpowered and I attempt to flash new firmware into it. Make sure Keil can see the target CPU (listed as SWD 0x0BB11477 on mine):

If you don't see the target CPU, check all the connections between your Keil host and the target device.