FRDM-K64F board with KDS_3.0.0, KSDK_1.3.0 and GNU_ARM_Eclipse_tools.

[daveyoung]

I am using a FRDM-K64F board with KDS_3.0.0, KSDK_1.3.0 and GNU_ARM_Eclipse_tools.

I have imported the "bubble_level_ftm_frdmk64f" example and compiled it with no Errors. When I run the Debug I receive the following error message:

"An internal error occurred during: 'Launching bubble_level_ftm_frdmk64f debug cmsisdap'.

ilg.gnuarmeclipse.debug.gdbjtag.dsf.GnuArmServicesFactory.<init>(Ljava/lang/String;Ljava/lang/String;)V"

Does anyone have any tips as to how I can find the cause of this error any rectifie the problem

regards

David Young

[daveyoung]

Thank you for your replies.

I have changed from Mbed to PEmicro, because I am using a PC with windows 8.1. Now I can load example programs.

Can anyone tell me where I will find information about the system variables of such as KSDK_PATH?

David

[daveyoung]

Found variables defined in KSDK Help.

Ton more brings another day of detective work, trying to find the answers to my errors

DAVID

[ZhangJennie]

Hi David,

in addition to David reply. I also have some comments.

1. first i suggest you remove .metadata in your current workspace to remove old associations. then restart KDS agian.

2. then i suggest you test the problem is in a specific project or a common issue for all project. you can create a new K64F project with wizard then test if it can be downloaded to flash successfully.

if this new project have connection problem too, I suggest you check the connection problem with this article:

Summary of FRDM-K64F open source debug interface

3. if the problem is only in bubble_level_ftm_frdmk64f sample. let's go through it.

a,  make sure ksdk_platform_lib_K64F12 project is built before bubble_level_ftm_frdmk64f.

b, clean bubble_level_ftm_frdmk64f  and rebuild it.

c,  check device manager, what connection interface does your board contains? choose the correct interface for launching debugger.

d, I made video of bubble_level_ftm_frdmk64f launching debugger on my side. please fyi.

can this help you?

Have a great day,
Zhang Jun

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

[DavidS · Accepted solution]

Hi David,

I just ran your test mostly successfully.  The first time I tried to grab control it wouldn't but with FRDM-K64F sometimes a re-plug of USB cable (and optional press reset button) before trying to Debug helps.  The error I got was:

First off do you have the latest FRDM-K64F MBED firmware?  Go here to check and/or get it: Firmware FRDM K64F - Handbook | mbed

My version when opening the MBED drive DETAILS.TXT is "Version: 0221".  The latest.

Second when you have plugged in the FRDM-K64F has it enumerated as following picture shows?

Third once the library and application are compiled, and you are going to debug the application do you have the following settings shown in your DEbug Configuration window:

Once I clicked Debug I was ready to go and run without issue.

Regards,

David