Feb 24, 2015
07:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 24, 2015
07:46 AM
Hello
in the datasheet and reference manual is written, that only four times it is possible to reprogram the UC-pages (UCB:user configuration block).
What happens if it will be repogrammed more than four times?
For me it seems, that the controller will be destroyed. I am not able to connect to the ASC BSL anymore. Also the programm in the flash is not running anymore.
Thanks!
in the datasheet and reference manual is written, that only four times it is possible to reprogram the UC-pages (UCB:user configuration block).
What happens if it will be repogrammed more than four times?
For me it seems, that the controller will be destroyed. I am not able to connect to the ASC BSL anymore. Also the programm in the flash is not running anymore.
Thanks!
- Tags:
- IFX
6 Replies
Feb 26, 2015
12:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 26, 2015
12:52 AM
Did you erase and reprogram the UCB (eg. changing the password) for more than 4 times?
Feb 26, 2015
10:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 26, 2015
10:00 AM
Yes. I am developing an asc bsl. During developing I erased and reprogrammed UCB more than four times.
I did not realize the maximum limit of four.
Is the controller now broken or is it possible to make it alive again?
I did not realize the maximum limit of four.
Is the controller now broken or is it possible to make it alive again?
Feb 26, 2015
09:03 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 26, 2015
09:03 PM
We have a limit of 4 for UCB erase/reprogram. In general it might be able to go for more than 4 times (or even more than 10) before something happens.
Feb 27, 2015
02:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 27, 2015
02:41 AM
... before something happens
What does this exactly mean?
Is the controller broken forever, if the maximum limit of 4-10 UCB erase/program cycles is exceeded?
Why is there such a low limit? Is it becaus of memory chip size/costs ?
Not applicable
Mar 02, 2015
12:30 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 02, 2015
12:30 AM
Hi olnol,
When the UCB is erase more than 4 times, the data on the UCB could be corrupted.
Hence, during the startup, the startup firmware is unable to read data from UCB which content protection configuration.
As stated in the Reference Manual, "Over-cycling the UCBs can also lead to an unusable device"
UCBs are logical sectors, and as such the allowed number of program/erase cycles are limited.
When the UCB is erase more than 4 times, the data on the UCB could be corrupted.
Hence, during the startup, the startup firmware is unable to read data from UCB which content protection configuration.
As stated in the Reference Manual, "Over-cycling the UCBs can also lead to an unusable device"
olnol wrote:
Why is there such a low limit? Is it becaus of memory chip size/costs ?
UCBs are logical sectors, and as such the allowed number of program/erase cycles are limited.
Mar 04, 2015
02:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 04, 2015
02:43 AM
With repsect to the failure of the device, slightly violating the number of program/erase cycles usually just leads to long term reliability issues with respect to the data retention no longer reaching its specified values.
Doing so under desk/lab conditions while developing/debugging software should usually not be an issue, but yes, eventually the device may be rendered broken if sectors, especially the UCBs, are cycled too often.
I assume you are using the UCBs to configure the flash protection and/or BMI configuration? Could it also be that you may have written a bad configuration value?!
Doing so under desk/lab conditions while developing/debugging software should usually not be an issue, but yes, eventually the device may be rendered broken if sectors, especially the UCBs, are cycled too often.
I assume you are using the UCBs to configure the flash protection and/or BMI configuration? Could it also be that you may have written a bad configuration value?!