K60D100 - N0 source available for 0xfffffffe

[yds]

Hi all,

I am using KDS 3.0.0 and KSDK 1.3.0. and trying to debug a C++ project to my custom board PK60N512VLQ100. But when I debug it, it shows "No source available for 0xfffffffe" and disassembly at 0xfffffffe: "Unable to retrieve disassembly data from backend".

Demo-program works just fine.

Read suggestions in the forum and tried a few of them but nothing works.

How do i solve it??

Any help would be greatly appreciated.

Thank you,

YS

[yds · Accepted solution]

Hi all,

I found the solution to my problem!!!!!

I had missed a setting in the C++ linker option i.e. to tell the linker to use the Flash file and so the problem.

I read this: http://http//mcuoneclipse.com/2014/06/15/tutorial-diy-kinetis-sdk-project-with-eclipse-startup/

Checked the settings in my project and found out what was causing the problem. :smileyhappy:

Anyways, Thanks.

[Alice_Yang]

Hello yds,

About the C++ project on KDS , does this can help you ?

Transitioning to C++ with KDS, KSDK, and Processor Expert

Hope it helps

Alice

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[yds]

Hi Alice,

I checked the link and it does not solve my problem.

The program is hitting some sort of breakpoint. The GDB tells me:

Program received signal SIGTRAP, Trace/Breakpoint trap.

0xfffffffe in ?? ().

What does this mean? and how to solve it?

Thanks,

YS

[Alice_Yang]

Hello yds,

Before you download  the project , please disable all of the breakpoints , and try again.

[yds]

Hello Alice,

I have not set any breakpoint in my program. I checked the breakpoints window to make sure of this.

Why do you suppose this is happening??

I have attached GDB logs. Please look into it.

Thanks,

YS

[mstroven]

It seems like your processor is getting a reset while your code is running...  Try putting a scope on the reset line to verify.  Do you have the reset pin pulled up externally?  If not, try a 4.7k pullup to Vdd.