Other Parts Discussed in Thread: SYSCONFIG, UNIFLASH
Tool/software:
Dear sirs,
in a simple blinking-application (example from sdk) one can include NVM configuration using sysconfig.
All the tools are latest version. Uniflash, CCS and TI-XDS110.
If SW-DP is enabled and debug access is enabled (completly the default configuration), the application can be downloaded and debugged in CCS. Also using the script "Factory reset auto" is available and working.
If SW-DP is still enabled and only debug access is disabled, the application still can be programmed. But after a power cycling which activates the new configuration, the application is still running correctly, but there is no further connection with XDS possible.
Tool message is:
Subsequently neither Uniflash nor CCS is able to reset the µC and re-enable the debug-access. The tool´s documentation states that excatly for that scenario the "factory reset auto" sequence which uses the DSSM is what should be done.
But it does not work if a connect is not working. The tools seem to be faulty for that scenario.
What do we need to do to gain control over the cpu again in that case?
Thank you for any help
