I've got an FRDM-K22F board and I'm trying to upload a simple test application. It doesn't seem to work using either the SDA-USB programmer or a Multilink Universal.
When I plug in the SDA-USB cable to my computer, I get a pop-up showing files mbed.htm and FAIL.txt. Sounds like that's probably a Win10 issue. The most recent discussions of this are from the Win8.1 preview era; the only fix I saw required the user to update the board with newer firmware, using a Win7 computer. Is there any more recent fix that doesn't require Win7?
Multilink Universal: when attempting to upload, I get this error message:
Loading programming algorithm ...
Error! Enabling module timed out.
Error enabling module just selected.
Error loading programming algorithm - load aborted.
Error occured during Flash programming.
WARNING - NO RESET SCRIPT FILE HAS BEEN CONFIGURED TO RUN!!!
TO MODIFY THE RESET SCRIPT SETTINGS, USE THE FOLLOWING MENU OPTION:
CONFIGURATION -> AUTOMATED SCRIPT OPTIONS
PE-ERROR: Error downloading to the device.
I've seen other discussions where the issues were related to wrong MCU selection, but I've confirmed that the correct MCU is selected in Debug Configuration (K22FN512M12).
Any idea what's going on here? both lights (orange and blue) are illuminated on the board. The Multilink Universal seems to correctly identify the board when it's attached based on the Debug Configuration window.
System details: Win10, Kinetis Design Studio 3.2.0
-previously, I was connecting the Multilink to the SDA header. The Multilink recognized target power and the correct MCU. However, I suspected that this might be the wrong header and switched to the JTAG/SWD header. The Multilink does not recognized target power on this header. Is this related to jumper configuration?