The On-Chip Flash Programmer does not remember the settings (OSCCLK, DIVSEL, FLASH API etc) on my system. It also forgets that I told it that I don't want to see a certain warning dialog again. Any way around this?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
The On-Chip Flash Programmer does not remember the settings (OSCCLK, DIVSEL, FLASH API etc) on my system. It also forgets that I told it that I don't want to see a certain warning dialog again. Any way around this?
It only retains the settings within the same CCS session. In other words, you can close and open the Flash plugin multiple times within the same CCS session and it retains the setting. However, with each new session of CCS, it prompts for these settings again. I think it is just designed to work this way.
Ok, so it's not a bug, it's a feature? :D
It would be OK if I could start CCS once at 8am and close it at 5pm - same session, no problem with On-Chip Flash programmer settings.
But CCS is not a particularly stable application - the faster I work, the bigger the source files -> the more often it crashes. And then this "feature" becomes very annoying.