1. If I want to use this feature so I should activate it only for series production, right !? During development it should be better NOT active since no debug session is possible !?
Yes, you are right. Flash protection is to prevent hacker to read and edit the software inside the XMC4000 flash. Hence this should be done during production after you had programmed the flash.
2. If the flash protection is activated the Startup SW clears the DCF and DDF after power-up,
so while the my App.-SW is running I do not need to clear the DCF & DDF again if I want to do read/write access to the flash e. g. for firmware update, is it correct ?
This is taken care by the startup software and there is no need to be involve with DCF and DDF.
3. In case of flash protection is active and I still want to debug I could do following:
a) change the bootmode (!= internal pflash)
No it is not possible. To unprotect the flash you have to erase the UCB.
b) connect the Jtag debugger, download a software (executable on PSRAM) which deletes the UCB0 (with correct passwords), after power-on the debug interface is not locked anymore ?
For firmware update, there is a temporary unprotect feature which allows user to update the firmware as many times as you wish. The protection is active again automatically after a hardware reset.
4. About "Resume Protection", as I understand it: after disabling e. g. the read protection, the read protection is enabled again after reset,
or I could do a "Resume Protection". I am wondering how the code fetch can be done after a "Resume Protection" ? (Misunderstanding on my part ?)
See 3b
You can have a feel of the protection feature using Memtool (see attached ppt). Please note that there is limited number of times you can reprogram the UCB (about 10 times) after that the MCU will be lock out forever. Other than that, please also remember your password.
