Closed ccchang12 closed 4 years ago
@ccchang12 thank you for raising this issue.Please take a look at the following comments:
Have you correctly specified which version of Mbed OS you are using (tag or sha)? We cannot automatically identify a release based on what you have provided.
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.
@ciarmcom , Mbed-OS version is 5.15.1
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2595
@ccchang12 Please check the fix proposal.
@kivaisan I think it is OK to fix this issue.
@ARMmbed/mbed-os-maintainers This issue can be closed as fixed.
@0xc0170 This issue can be closed.
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-2306
Description of defect
When the EC2x driver reset module, the soft_power_on() only waits "RDY" message for 5 seconds. But in my test, the EC2x module reset needs 11 second and cause reset fail. Quectel engineer also replies the reset procedure takes about 11 seconds. I think you should increase the timeout.
Target(s) affected by this defect ?
K64F + EC21
Toolchain(s) (name and version) displaying this defect ?
ARM Compiler 6.12
What version of Mbed-os are you using (tag or sha) ?
mbed-os-5.15.1
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli
How is this defect reproduced ?
For mbed-os-example-cellular, if the cellular module is not in device ready state (e.g. , does not call iface->disconnect() in last test), it will call the soft_power_on().