X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=tcl%2Ftarget%2Fkx.cfg;h=51703e69d1c8549687ba9d3916e234b6b5e9c88d;hp=7b0351706a9420d3cbf63f5eed40719aeed6e5ed;hb=a0b76360b874607f2aa075e764891f129b5ff0f9;hpb=437925c1415ac1f7d5b1b1bb4dcfb4898849d499

diff --git a/tcl/target/kx.cfg b/tcl/target/kx.cfg
index 7b0351706a..51703e69d1 100644
--- a/tcl/target/kx.cfg
+++ b/tcl/target/kx.cfg
@@ -44,7 +44,20 @@ 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 " Expect problems connecting to a blank device without boot ROM."
+   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