Open amq opened 3 years ago
@ARMmbed/team-silabs Please review
@amq thank you for raising this issue.Please take a look at the following comments:
How can we reproduce your issue?
NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'. This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirrored to our internal defect tracking system or investigated until this has been fully resolved.
@ciarmcom updated
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3820
Under light load, everything is mostly fine, most of the time. But when I tried a stress test, there are many problems.
If you add locks, all works as expected? Shall they be added?
Under light load, everything is mostly fine, most of the time. But when I tried a stress test, there are many problems.
If you add locks, all works as expected? Shall they be added?
I was also involved in this issue together with @amq and some other colleagues. We finished some tests today. Our modification in this case was to disable deep sleep before any initialization of the QSPI-drivers, effectively forcing you to do dynamic allocation if you don't want to make changes in the drivers yourself.
We have 7 devices that experienced problems with this during regular use (not entirely sure why only a few units was affected) and adding locks fixes the issue for all these 7. We have also used the stress test above to test more units and adding the locks solves the issue in all our cases.
Our original setup (some devices not behaving correct & most units failed during stress testing):
// FLASH INIT HERE
int main() {
// FLASH READING/WRITING HERE
mbed_start_application(POST_APPLICATION_ADDR);
}
Our testing setup (all tested devices so far behaving correct):
int main() {
sleep_manager_lock_deep_sleep();
// FLASH INIT HERE
// FLASH READING/WRITING HERE
sleep_manager_unlock_deep_sleep();
mbed_start_application(POST_APPLICATION_ADDR);
}
Hi @0xc0170 , and progress on this issue yet? Thanks in advance!
@ciarmcom @0xc0170
Hi guys, any news on this issue?
@ARMmbed/team-silabs Can you have a look?
Description of defect
According to the reference manual of EFM32GG11, QSPI is not available in EM2 (deep sleep), but I don't see any locks preventing deep sleep in mbed-os.
Under light load, everything is mostly fine, most of the time. But when I tried a stress test, there are many problems.
Target(s) affected by this defect ?
EFM32GG11
Toolchain(s) (name and version) displaying this defect ?
All
What version of Mbed-os are you using (tag or sha) ?
Any
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
Any
How is this defect reproduced ?
Here's a stress test I used: