IWe're using a Flasher ARM to program Kinetis K60 CPU.
When the K60 Flash-swapping (for field software upgrade) is enabled within my custom firmware, the K60 gets into some kind of secured mode.
This is no problem on the field, as the custom firmware has the capability to upgrade itself.
In develolopment, we use the J-LINK command shell with the command: "unlock kinetis".
This gets the K60 out of its "secured" mode and it's ok to program it with JTAG again.
For production we use the Flasher ARM controlled by its RS232 interface.
Brand new "unsecured" units works well and the K60 gets its custom firmware.
When the production gets a "secured" K60 it can't be programmed.
The question is, if it's possible to "unlock kinetis" via the RS232 interface?
Our production host is using ARM and Linux.
Any other solution to unlock?
When the K60 Flash-swapping (for field software upgrade) is enabled within my custom firmware, the K60 gets into some kind of secured mode.
This is no problem on the field, as the custom firmware has the capability to upgrade itself.
In develolopment, we use the J-LINK command shell with the command: "unlock kinetis".
This gets the K60 out of its "secured" mode and it's ok to program it with JTAG again.
For production we use the Flasher ARM controlled by its RS232 interface.
Brand new "unsecured" units works well and the K60 gets its custom firmware.
When the production gets a "secured" K60 it can't be programmed.
The question is, if it's possible to "unlock kinetis" via the RS232 interface?
Our production host is using ARM and Linux.
Any other solution to unlock?