
NO.:
W62410 API
VERSION:
A
PAGE
110
Deleting messages (garbage collection):
When using the
DeleteMessage
command, the message is in fact not removed from the external storage
memory. The message is only marked as to be removed but it still occupies the same amount of memory
as previously! To the host controller it will look like as if this message is effectively deleted and cannot
be accessed. All information returned to the host controller by the CHIPSET concerning messages
already take into account as if this message has been deleted although it is in fact still present in the
external storage memory. To actually free up the occupied external storage memory one has to perform a
garbage collection. Be aware that this can take several seconds for Flash memory. As explained in the
API command section one can perform a garbage collection in two ways:
1) Do the garbage collection in one go. The big disadvantage is that the CHIPSET can take several
seconds to perform this action, which is not desired in some, time critical, situations.
2) Do the garbage collection in several steps, which each take only a very short time. In this way, the
host controller can respond much quicker to time critical situations before continuing with the next
stage of the garbage collection. Remember that all stages of a garbage collection have to be
completed before the garbage collection is actually completed. Stopping in between will not have
freed up any memory. Only when the last stage of the garbage collection has been executed all freed
up memory will be released. Remark that even when a garbage collection is not completely finished it
is possible to do a recording.
The above information is the exclusive intellectual property of Winbond Electronics and shall not be
disclosed, or reproduced without permission from Winbond.