"error in final launch sequence" FRDMK64F debug problems

[unclemike]

I am getting a "error in final launch sequence" when I try to debug.  I have looked at posts from Rahul PS and Erich Styger and everything they mention seems to be correct.  I was debugging ok for a few days and then I started getting the error.  I don't remember doing anything that could break the debugger.  It was working when I shut down KDS, broken when I started KDS the next day.

When I start debugging, the "Problems" tab shows a screen of red text that immediately disappears before I can read it, and then several seconds later I get Rahul PS's result, shown in the attachment.

I am using KDS 3.1.0 with KSDK 1.3.  Windows 10 on Mac running VMware.  (I have been running vmware for years, no problems, even Codewarrior 6.x for 9S08 MCU's runs just fine .)

I have also installed Mac versions of KDS and KSDK,  but trying to debug there has a different set of problems. If you have gotten debugging working on a Mac, I would love to hear from you.

Thank You

Michael

[BlackNight]

Hi Michael,

basically this message says that it is not able to launch/run the debugger. There could be many reasons for this, even to the point that the connection to the GDB server is blocked by a firewall or that a virus scanner has removed some files.

What kind of debug interface are you using? P&E? openOCD? Segger?

Can you crosscheck your debug panels/settings.

Can you verify as well your PATH Windows system variable? I have seen issues with some GNU tools if the PATH has ";;" in there.

I hope this helps,

Erich

[unclemike]

Hi Erich:

Thanks for the response, and also all the work you do on mcuoneclipse and these forums.  Where do you find the time??

I was trying to use the frdmk64f's openOCD debugging on win10.  It was working for three days and then I started getting the "error in launch sequence" message.  After it quit working on win10, I tried a Mac install.  There was some kind of update to the frdmk64f, and openOCD was not there in the debug configuration dialog.  Debugging on the Mac also did not work.  Now, when I plug in the frdmk64f, a drive appears named 'mbed'.  If I hold the reset button when I plug in the frdmk64f, a drive appears that is named 'bootloader'.  Is this normal?  Also, there is a red LED on the frdmk64f,  when it is on, things don't work, but I can't find any info on it. 

So, some question are:

Does the presence of the 'mbed' drive indicate a problem?  Did I change things when I tried to debug on a Mac?  If I have, how do I put it back?  I didn't see "openOCD" in the debug configuration dialog on the Mac, but there was a jlink option there. I thought maybe the openOCD pretended to be some kind of j-link device.

Is there anyplace with more detail on the frdmk64f?  What does the red LED mean?

Is there anyplace with more detail on how to use a frdmk64f on a Mac?  Is it normal for there to be no openOCD available?  I would prefer to stay in windows, but maybe VMware is doing something to cause problems.

Thanks for your help

Michael

[BlackNight]

Hi Michael,

thanks! And about finding the time: I'm using a secret time travel technology: dangerous, but effective to get more done ;-)

If the board shows up as mbed, then the mbed/CMSIS-DAP firmware is loaded or running. You only can debug that with openOCD. But openOCD is not includeed in KDS for Mac OS X. Mac OS X only supports the J-Link firmware.

That it shows up as BOOTLOADER if you plug it in with the reset button pressed is normal. Then you can load a different firmware. So if you want to use the board on Mac, load the Segger Firmware (OpenSDA V2 (E.g. FRDM-K64F boards): Download JLink_OpenSDA_V2_2015-10-13.zip) available on SEGGER - The Embedded Experts - OpenSDA / OpenSDA V2  while in BOOTLOADER mode (see https://mcuoneclipse.com/2014/11/01/illustrated-step-by-step-instructions-updating-the-freescale-fre... ).

The red LED indicates that the board is doing a reset. So if this one is on, the K64F is resetting all the time. In that case typically OpenOCD/CMSIS-DAP is not able to get hold of the K64F. In that case, follow steps outlined in https://mcuoneclipse.com/2014/04/19/recovering-frdm-k64f-mbed-board/  to recover your board.

Oh, and one thing to add: there are sometimes power-up issues with the FRDM-K64F board: unplug it and re-plug it quickly again. Sometimes this helps (power-on with the capacitors already loaded).

I recommend to use either P&E or Segger firmware with the board.

I hope this helps,

Erich

PS: on another note: in my university classes I had three independent cases where Windows 10 somehow erased the OpenOCD application, so the board was reverted back to Bootloader mode. Not sure if you are seeing this problem too. It seems to be related to Windows 10, and appens both for the 'mbed' bootloader (as on the FRDM-K64F) and as well for the original OpenSDA bootloader (developed by P&E).