Hi Martin
The Kinetis can lock out JTAG depending on the Flash configuration setting (starting at Flash address 0x400), however this shoudln't be possible with uTasker/Rowely due to two reasons:
1) The setting is defined in
kinetis.cconst KINETIS_FLASH_CONFIGURATION __attribute__((section(".f_config"))) __flash_config
= {
KINETIS_FLASH_CONFIGURATION_BACKDOOR_KEY,
KINETIS_FLASH_CONFIGURATION_PROGRAM_PROTECTION,
KINETIS_FLASH_CONFIGURATION_SECURITY,
KINETIS_FLASH_CONFIGURATION_NONVOL_OPTION,
KINETIS_FLASH_CONFIGURATION_EEPROM_PROT,
KINETIS_FLASH_CONFIGURATION_DATAFLASH_PROT
};to set values that are don't activate this. If you check in the binary file loaded (
uTaskerV1_4.bin) you should find that the 16 byte form address
0x400 are
00 00 00 00 00 00 00 00 ff ff ff ff be 03 ff ff2) Rowley Crossworks doesn't program code to this range - when dowloading you should have seen a warning that the loaded code didn't match that verified in Flash and, when a list of differences is generated, it shows that several bytes in this are are still at 0xff in Flash.
The JTAG pins are not used in the project and I haven't heard of anyone being able to lock out a debugger with them; I don't think that they suffer from the same lock out possibility that the Stellaris JTAG ports do.
There is some more info here about locking chips, including a link to Keil resources that supposedly can recover in some circumstances:
http://forums.freescale.com/t5/Kinetis-ARM-Cortex-M4/Secured-Kinetis-device/td-p/91305However, I don't think that it is possible to lock a board with the project unless the Flash configuration were to be explicitly changed to do it and a different loader to the Rowley one used.
What message does Rowley give? Sometimes I find that I need to power cycle the board and restart Crossworks. Also, after installing MQX (to get an idea about the Wifi driver being used) I could no longer work with any P&E tools (including OSJTAG) without reinstalling the P&E drivers.
Regards
Mark
P.S. Try also CW10.2 (or maybe it is CW11 now) and try a mass erase using its inbuilt Flash loader tool.
Also try running the P&E Firmware Information Utility from their Formware Updater package to check that the drivers/OSJTAG are OK