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.
Part Number: CC3220MODA
I'd like to know what will happen to RAM during hibernation.
Especially memory fragmentation, is there any possibility that fragmented memory remains after hibernation(RTC wake-up).
Would it be okay to regard both cold-boot/POR and wake-up-from-hibernation is same in RAM standpoint?
There is no RAM memory retention at hibernation mode (if we not count few bytes of RTC and retention registers). If you need RAM retention you need to use LPDS (low power deep sleep. Power management of CC3220 device is described at this video.
Please click to "Verify Answer", if your question was answered.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Jan D:
I understand there is no retention at HIB mode and I'm using retention registers for this purpose.
What I'm asking is if it is 100% sure that RAM fragmentation will be cleared after hibernation.
In reply to YunJung Kim:
Sorry, I don't understand your question, because it really not make sense. How do you expect that content of RAM can retain if RAM is not powered at HIB?
btw ... content of RAM si cleared by ROM bootloader after POR or exit HIB from security reasons.
A weird bug that makes a bad_alloc exception which is recovered itself accidentally led to this weird question.
(This application runs seconds and enters HIB hours repeatedly)
And I wasn't able to find a description of RAM behavior during hibernation so I guessed if the RAM power is not intentionally off, this could happen.
If you have, could you share a link or document number I can read about the details?
I am not aware about any official documentation. This topic was discussed few times at e2e forum. You can try to search for this older threads.
Your application should be designed according this two facts:
If you think that your application code can be affected by undetermined/previous state of RAM, you should change this. Because this is definitely not correct.
But if I should guess, I think that reason of you issues lies somewhere else then not determined state of RAM after startup.
Thanks for your advice!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.