Reinstall Pemicro MSD bootloader after mbed bootloader

[kirkg]

When I first got my frdm-kl25z board I was able to load the .srec files from the quick start zip file.  Since then I installed the mbed bootloader and have been successfully using that as well.  I'd now like to go back to the pemicro loader so I can try out coding using KDS, but I'm running into problems.  Here is what I have done:

1) reboot board to bootloader

2) Drag "BOOTUPDATEAPP_Pemicro_v111.SDA" into msd

3) reboot board again (this time it comes up in bootloader)

4) Drag "MSD-DEBUG-FRDM-KL25Z_Pemicro_v114.SDA" into msd

5) reboot board again

6) trying to drag ANY srec onto MSD

The small green led flashes, but the program never takes.  Readind the text file in the MSD says "Error 7"

Any ideas on how to get back?  I can put the mbed bootloader back on and everything works as it did before, I just can't get the KDS srec version to work again.  Thanks

[BlackNight]

Between step 3 and 4 you need to press reset to enter bootloader mode again, see

http://mcuoneclipse.com/2014/11/01/illustrated-step-by-step-instructions-updating-the-freescale-free...

And step 2) is only needed if you need to update the bootloader (this is needed only once).

Erich

[kirkg]

Erich,

Thanks for the reply.  I'm following that instruction set you listed, but the result is the same.  After the final reboot (unplug/plug) the device shows up an MSD with name FRDM-KL25Z.  If I read LastStat.txt is says "Ready" and the green LED is solid.  If I then drag an srec file onto it the green light starts blinking (it looks like 7-8 pulses then pauses and repeats) and the the LASTSTAT.txt file reads "Error 7".  It's almost like there is something about the last mbed application on the flash it doesn't like and can't write over.

Also if I put the mbed bootloader back on, the last mbed .bin file (mbed program) I wrote to it is still there and functioning correctly, showing the pemicro bootloader isn't altering the flash contents at all.

Kirk

[Hui_Ma]

Hi Kirk,

I also do a test with FRDM-KL25Z board, everything is ok on my site.

I am using attached MBED FRDM-KL25Z board image, and it could works.

After that, I hold FRDM-KL25Z board reset button and enter into BOOTLOADER, then load attached [MSD-DEBUG-FRDM-KL25Z_Pemicro_v114.SDA] firmware.

Then, it will be recognized as [FRDM-KL25Z] MSD disc and load attached application [blinky_green.srec] image, which will run as expected.

Wish it helps.
best regards
Ma Hui

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

[kirkg]

Ma Hui,

Thanks for the response.  I tried your files, but got the same result, I'm thinking something on my board is damaged.  The process I went through was:

1) unplug board

2) hold reset button and plug in.  Note that device shows up as MSD called Bootloader

3) Copy the MSD-DEBUG-FRDM-KL25Z_Pemicro_v114.SDA onto the drive.  LASTSTAT.txt says complete

4) unplug board, replug board.  Now MSD shows up as FRDM-KL25Z

5) drag blinky_green.srec into folder.  Small green LED starts to blink rapidly in pulse groupings of 7 (I think it's 7, but they are fast).  Reading LASTSTAT.txt after loading srec says "Error 7"

6) plug/unplug board no change.

7) pound head against wall....

8) unplug board, hold reset, plug in board.  Opens as MSD called bootloader.

9) drag mbed bootlaoder back on.

10) unplug/plug in board

11) previously installed mbed app still on and functioning as before.

12) try dragging new mbed app on.  This works too.

Thanks

Kirk

[BlackNight]

I have seen cases were virus scanners have a bad impact. Can you disable it and try it without virus scanner active?

Another option: use the DOS/cmd prompt to copy the file to the FRDM-KL25Z drive

Erich

[kirkg]

Erich,

Thanks I will try that as well, but is there any reason to believe the virus scanner would act differently between the mbed bootloader and the pemicro bootloader?

Kirk

[BlackNight]

that might depend on the virus scanner I think. Just wanted to throw in a different angle.

Erich

[kirkg]

Note : Same as a previous reply where I replied to wrong message in email.

Erich,

One more point of information is that when I first got the board, and before installing mbed, I was able to successfully drag/drop the precompiled example srec files into the pemicro boot loader.  The problems have all been related to trying to get back to the starting state.  Thanks again

Kirk

[kirkg]

The best I can tell from the "Error 7" and the Console debug message I get from KDS is that with the PEMicro bootloader the board is "Unable to enter background mode".  Does this help or tell you anything?  Thanks

Kirk

[BlackNight]

To me this "unable to enter background mode" says that it cannot halt the KL25Z so it can be debugged with the OpenSDA.

So the K20 is not able to take control over the KL25Z.

Erich

[kirkg]

Does this sound like a potential hardware failure then, or bootloader issue (since I have a newer version that you)?  The fact that the mbed bootloader seems to work, but the pemicro one doesn't suggests firmware.  Any chance I can replace the newer firmware on my board with the older one you have to see if that solves it?  If so where can I get them?  Thanks

Kirk

[Hui_Ma]

Hi Kirk,

Which PC OS you are using?

best regards,

Ma Hui

[kirkg]

Windows 8.1

[Hui_Ma]

Hi Kirk,

If you want to debug the FRDM-KL25Z board with KDS IDE software, it need to load [DEBUG-APP_Pemicro_v108.SDA] to <BOOTLOADER> disc.

BTW: I still waiting for Pemicro feedback about FRDM-KL25Z Mass Storage/Debug App issue.

Thank you for the patience.

Wish it helps.
best regards
Ma Hui

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

[kirkg]

Hui,

Problem solved some how.  I tried to update to DEBUG-APP_Pemicro_v108.SDA like

you suggested, but after doing that it never appeared as a MSD in windows.

I went back to the PEMicro folder and reinstalled the

MSD-DEBUG-FRDM-KL25Z_Pemicro_v114.SDA file once again to try and get back

to the previous state, and it started working this time!!  I can even debug

in KDS now!!  I can now even successfully switch between the mbed and

pemicro bootloaders so something about installing the v108 version then

overwriting it saved the day.  Thanks again

Kirk

P.S.  As a side note, it appears that I can now drag/drop both srec files generated by KDS and bin files generated by mbed into the PEMicro MDS and they all run.  The mbed ones now start to run immediately like the KDS ones, where as with the mbed bootloader you have to press reset.  Is this behaviour expected, or did I create a franken-frdm?  Now that mbed app seem to seemlessly run, there is no need to go back to the mbed bootloader, am I missing something?

[kirkg]

I celebrated too soon.  Everything seemed to work, but then the board (with the v114 PEMicro bootloader) stopped letting me load any programs (bin or srec).  I was able to recover by going back to the mbed bootloader, installing a previous program (and running it), and reinstalling the v114 PEMicro bootloader.  This worked a couple times, but eventually the board would again flake out and stop loading programs (always giving the previous Error 7).  At this point the none of the previous tricks are working (not even loading the v108 bootloader first), so I'm back where I started with a board that ONLY works with the mbed bootloader.  The thing that seemed to cause the board to flake out and no longer accept any programs (yes I tried pressing reset and unplug/plugging it) was the KDS debugging.  It would let me do it a couple of times, then it would no longer connect and KDS would give errors about not connecting to the device.

[zaharr_]

Hi Kirk,

I am sorry you are having issues with your FRDM-KL25z board. Can you please share your MBED application, so I can try to reproduce the sequence of steps you are following.

Thank you,

Zahar

P&E

[kirkg]

Zahar,

Attached are the mbed bootloader and an example mbed program, but this behaviour isn't specific to 1 mbed program.  Thanks for the help and hopefully you can reproduce this.

Kirk

[zaharr_]

Hi Kirk,

I tried switching the OpenSDA application to MBED and back to P&E MSD/DEBUG and did not see any problems under Windows 7 and 8. I am able to take advantage of programming a .s19/.bin files via MSD in standalone fashion.

At the same time, after your mbed_timer_blink_KL25Z.bin is programmed into target KL25z device I did not see an LED on the board blink. I am attaching a knowingly good simple blinking led program for you to try to program via MSD.

The contents of your INFO_SDA.HTM file indicate that your P&E firmware gets properly loaded onto your Freedom board. Are you able to run a standard run control interactive debug session (under Codewarrior, KDS, IAR, Atollic, Keil) using P&E OpenSDA on your FRDM-KL25z board? Do you happen to have access to a different FRDM-KL25z board?

Best Regards,
Zahar

P&E

[kirkg]

Zahar,

Interesting, that mbed_timer_blink_KL25Z.bin blinks fine on my board when the mbed bootloader is installed.  I don't have access to another board at this time (that's another long story), but I'll try to connect to the board in KDS.  The times I have previously connected via KDS are when the board was correctly allowing me to copy to the programs over via MSD as well.  When the control stopped working I could no longer copy programs via MSD either.

Kirk