X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=tcl%2Ftarget%2Fklx.cfg;h=b41dbf78e5d1d71bdf142f25a6efc08f494ff8bc;hp=1a2ee6798e13067d967611e5d64b46243cfe5de5;hb=a0b76360b874607f2aa075e764891f129b5ff0f9;hpb=437925c1415ac1f7d5b1b1bb4dcfb4898849d499

diff --git a/tcl/target/klx.cfg b/tcl/target/klx.cfg
index 1a2ee6798e..b41dbf78e5 100644
--- a/tcl/target/klx.cfg
+++ b/tcl/target/klx.cfg
@@ -43,7 +43,19 @@ adapter_khz 1000
 
 reset_config srst_nogate
 
-if {![using_hla]} {
+if {[using_hla]} {
+   echo ""
+   echo "!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!"
+   echo " Kinetis MCUs have a MDM-AP dedicated mainly to MCU security related functions."
+   echo " A high level adapter (like a ST-Link) you are currently using cannot access"
+   echo " the MDM-AP, so commands like 'mdm mass_erase' are not available in your"
+   echo " configuration. Also security locked state of the device will not be reported."
+   echo ""
+   echo " Be very careful as you can lock the device though there is no way to unlock"
+   echo " it without mass erase. Don't set write protection on the first block."
+   echo "!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!"
+   echo ""
+} {
    # Detect secured MCU or boot lock-up in RESET/WDOG loop
    $_CHIPNAME.cpu configure -event examine-start {
       kinetis mdm check_security