FRDM-K82 using OpenSDA

shauldorf · ‎12-08-2016

Few months ego I have seen reports about possible damage when using FRDM-K82F OpenSDA Firmware in windows 10 environment.

My question is if the problems still exists or has been solved.

Tx

Shaul

kerryzhou · ‎12-11-2016

Hi shaul dorf,

This issue will be solved in the bootloader reversion opensda v2.2.

Now, you can try to refer to this post:

https://mcuoneclipse.com/2016/06/26/how-to-recover-the-opensda-v2-x-bootloader/

And use the beta opensda v2.2 on your side:

https://developer.mbed.org/questions/68997/How-to-recover-FRDM-K22F/#answer10413

Wish it helps you!

Kerry

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

shauldorf · ‎12-12-2016

Thanks

Is there any schedule for OpenSDA c2.2 new version
What is the status of |PEMicro and J-Link, is it safe to use them?

BR

Shaul

kerryzhou · ‎12-12-2016

Hi Shaul dorf,

Please refer to this post:

Freedom OpenSDA Firmware Issues Reported on Windows 10

The schedule is not given out, if I get the update information, will let you know.

You can use the PEMicro and JLINK, it is support the win10 now, but just as suggest, you need to replace the default CMSIS-DAP application with a Segger JLink or P&E OpenSDA application before using a Windows 10 computer.

Wish it helps you!

Have a great day,
Kerry

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

mjbcswitzerland · ‎02-03-2017

Hi All

I am wondering how to use the P&E Micro version so that it would be possible to debug on the FRDM-K82F board?

When I try to load the P&E version (the newest is MSD-DEBUG-FRDM-K82F_Pemicro_v118.SDA) it just reports that there is not enough space on the disk to copy it. P&E has just debugger versions (no MSD) for FRDM-K22 and FRDM-K64 which work but not such for the FRDM-K82.

Pre-loaded mbed version allows copying files to the board from Win 7 but loses the file when connected to Win 10. It doesn't support debugging and doesn't offer a VCOM serial port. At mbed there is no mention of support for the board and no new versions found.

Any ideas how to work though what looks like a availability of working support?

Regards

Mark

BlackNight · ‎02-03-2017

Hi Mark,

I don't have a K82F, but are you using the version from 2017_01_31 (P&E Microcomputer Systems: Over 30 years as an Industry leader in Embedded Systems Development Tools... )?:

I saw errors about 'not enough space' in combination with virus scanners or some 'MSD indexing devices'. Best if you copy the .SDA file from a DOS prompt.

I hope this helps,

Erich

mjbcswitzerland · ‎02-03-2017

Eric

Yes, I tried that version.

I think that the problem is that the FRDM-K82F (and other FRDM boards) are delivered with mbed bootloaders. These show the disk space (also in DOS) as 96k in size. The P&E MSD + Debug application is 200k in size and so can't be copied (also not in DOS). I do have a suspicion that the SDA files are also code in some way and can only be loaded if the P&E Bootloaer is installed.

I had the same problem with other FRDM boards such as the FRDM-K64F but P&E Micro also has a debug-only ".bin" in the package for that the board which can be loaded and is adequate for some debugging (but misses a VCOM and USB-MSD). Therefore I tend to have multiple boards - one with the mbed (which does VCOM and USB-MSD but can't debug) and one with P&E in case I need to quickly do some low level debugging.

Unfortunately I don't know where to get a new bootloader that will need to be loaded via JTAG first that will then allow a version to be loaded that will work with Win 10 and also allow debugging.

It seems that the mbed FRDM-K82F support is very half-hearted - the link on the boot loader leads to a non-existent ARM page - they don't even have anything on the official web site about the board (no new version that corrects the Win 10 issue, whereas FRDM-K22F and FRDM-K64F do) yet the FRDM-K82F, is a year or so old, is delivered with their loader which doesn't actually work (just to copy form Win 7) and doesn't allow corrections....

I have installed a secondary boot loader with USB-MSD and CDC so that can basically work but will probably need to fall-back on a HW Jtag method in case of specific debugging requirements - or use the TWR-K82F board instead.

There still seems to be be quite a mess with these tools - each time losing several hours to do a couple of simple checks ;-(

Regards

Mark