FRDM-KL26Z

[haonguyen]

Got the FRDM-KL26Z today and followed the Quick Start Quide.

After loading the OpenSDA application MSD-FRDM-KL26Z_Pemicro_v112.SDA and disconnect/reconnecting the USB cable.

The FRDM-KL26Z no longer enumerate as FRDM-KL26Z.  In fact I don't see any activity, e.g. green LED doesn't come on..

I can still power up on Bootloader mode by holding down the reset button and attaching usb cable.

What am I doing wrong?  Any help would be appreciated.

[Kan_Li]

Hi Hao Nguyen,

The v114 is the latest SDA firmware, did it work on your side? Please kindly let me know if the problem is still there.

Have a great day,
B.R
Kan

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

[haonguyen]

Still not working.  Same result...  This is the steps I did.

1. Press hold reset button and plug in USB cable

2. board powers up with green LED and shows up as BOOTLOADER on my PC

3. drag and drop file MSD-DEBUG-FRDM-KL26Z_Pemicro_v114.SDA to root directory of BOOTLOADER drive.

4. unplug USB cable, wait couple seconds then reconnect USB cable.

result

board doesn't seem to power up, i.e. no green LED

device manager doesn't show any new device...

[BlackNight · Accepted solution]

What is your host operating system? Windows 8?

Note that there is a problem with the bootloader and Windows 8, you need a Windows 7 machine.

Erich

[mjbcswitzerland]

Erich

Do you know why the boot loader doesn't work with Windows 8? Is it due to the fact that Win 8 always writes an invisible file to newly attached drives (something to do with speeding up searches in future connection or something) or is there another problem?

regards

Mark

[BlackNight]

Hi Mark,

yes, I think this is the source of the problem (FRDM Board Bootloader fails with Windows 8.1 Preview | MCU on Eclipse). A similar problem exists on Mac computers too. Such an MSD bootloader implementation needs to be prepared to deal with 'wild' accesses to such a virtual MSD device.

P&E fixed it with the latest firmware/bootloader update (New P&E OpenSDA Firmware v114 | MCU on Eclipse)

But you need a Win7 machine to make that transition.

Erich

[mjbcswitzerland]

Hi Erich

Ok, that sounds like this, which was introduced with Win 8.1. There is in fact a workaround for Win 8.1 since this can be disabled in a setting called "Do not allow locations on removable drives to be added to libraries"  as discussed here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-hardware/how-do-i-prevent-system-volume-...

This should allow the update to be made on a Win 8.1 machine and then the setting reversed when finished.

I had to make the uTasker MSD bootloaders Win 8.1 proof early on in the year - since what it writes is invisible it is not obvious (at first) what happens but a tool like XYplorer sees invisible system volume information that is "secretly" written.

Regards

Mark

[haonguyen]

That did the trick.  Had to go to a Windows 7 machine to get it to work.

Thanks Erich!

[mjbcswitzerland]

Hi

Something can't have worked correctly. When the PE Micro OpenSDA debugger is loaded the green LED will light and the board is seen as a hard drive "FRDM-KL26Z".

You look to be loading an old version - I have attached the one that I use [MSD-DEBUG-FRDM-KL26Z_Pemicro_v114.SDA] which is a lot newer (a year or so newer), which doesn't have any problems.

Regards

Mark