topic Re: FRDM-K64 Target Connection Fail in Kinetis Software Development Kit

FRDM-K64 Target Connection Fail

ben2 — Thu, 15 Nov 2018 07:42:27 GMT

Hi All,

Good day.

I have just bought a FRDM-K64 evaluation kits and following the tutorial step by step to test on it. Unfortunately, I am having the communication issue between the evaluation kits to the mcuXpresso IDE.

anyone can assist on this issue or anyone is facing the same problem?

please advice, Thank you very much.

Regards,

Ben.

Re: FRDM-K64 Target Connection Fail

andy1 — Tue, 20 Nov 2018 15:40:18 GMT

I have this same problem every single time I reconnect my dev board to the USB debugging port. There is a workaround but you have to perform it EVERY SINGE TIME, so it is frustrating and time consuming when you are working on something that requires you to disconnect and reconnect the USB! Hopefully someone has a more permanent fix. It's honestly kinda ridiculous that a problem like this exists and remains undocumented with a development kit! It doesn't give one much confidence in the ecosystem as a whole!:smileyangry:

In order to get around this:

Open the "GUI Flash Tool" in the toolbar (the DIP looking icon)
Select OK when it finds the target ("MBED CMSIS-DAP" for my K22 freedom board)
In the "Target Operations" section click on "Resurrect locked Kinetis device"
Hit "Run"

It will connect, complete the script and now you'll be able to run the samples.

Oh yeah another peculiarity: On my K22 board at least, the LED is a 3-color and the firmware seems to be written for a different iteration of the board/LED. So it doesn't change colors like you'd expect when you run the demos that change the LED; blinky, level, etc... But if you look at the schematics it's pretty easy to figure out how to change the GPIO settings to get it to change to the correct colors. It's actually a pretty good, easy activity to learn how the pins/ports work.

If anyone knows a permanent fix for the debug port that would allow us to avoid running the resurrect script every time we connect, it would be much appreciated!!!

Re: FRDM-K64 Target Connection Fail

Carlos_Mendoza — Wed, 21 Nov 2018 18:38:02 GMT

Hello Ben Cheong,

Please make sure you are using the latest MCUXpresso IDE and the latest OpenSDA firmware application in your board:

MCUXpresso IDE|Eclipse-based Integrated Development Environment (IDE)|NXP

OpenSDA Serial and Debug Adapter|NXP

Once you update the OpenSDA firmware application you will need to delete the Launch Configuration files in your project ({projname}{debug solution}Debug.launch and {projname}{debug solution}Release.launch) and create them again, simply highlight the appropriate project in the ‘Project Explorer’, and then in the Quickstart Panel click on Debug 'Project Name', alternatively click the blue bug icon to perform the same action.

Also, please make sure there are no hanging debug processes by clicking on the "Clean up debug" icon:

Hope it helps!

Best Regards,
Carlos Mendoza
Technical Support Engineer

Re: FRDM-K64 Target Connection Fail

Carlos_Mendoza — Wed, 21 Nov 2018 18:45:18 GMT

Hello Andrew,

I have not seen the behavior you mention, does this happen to you with any project? Have you tried using other OpenSDA applications?

Also, what is your application configuring? Usually the Mass Erase is needed when the device has been secured or protected:

How (not) to Secure my Microcontroller | MCU on Eclipse

Best Regards,
Carlos Mendoza
Technical Support Engineer

Re: FRDM-K64 Target Connection Fail

andy1 — Mon, 26 Nov 2018 16:42:30 GMT

Carlos,

This happens with every project that I have imported from the SDK examples. (Both modified and not) I am using the latest version of MCUExpresso. I have not tried any other OpenSDA applications nor have I attempted to update OpenSDA firmware yet. I will do that when I have time.

Much like Ben, I first encountered this running the tutorials after I first got my board. I have multiple FRDM-K22F kits that I ordered at a later date and they all exhibit the same symptoms! I also recently installed the toolchain on my laptop and faced the same issue, so I know it's not a particular problem with my development machine or a specific dev kit.