-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CY8CKIT_062S2_43012 Test Fails #13076
Comments
@maclobdell thank you for raising this issue.Please take a look at the following comments: We cannot automatically identify a release based on the version of Mbed OS that 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. |
cc @ARMmbed/team-cypress |
Not sure about the cordio failures yet, but the sleep failures are probably the same as #12434 (known issue, fix in progress). |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
7 similar comments
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
@maclobdell it has been 5 days since the last reminder. Could you please update the issue header as previously requested? |
I updated the tag to |
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. |
@kyle-cypress as #12434 is now fixed can this be closed ? |
Yes, I believe this can be closed. The Cordio failure can be tracked in #13295. |
…CYW43XXX Cordio HCI driver incorrect handles lock/unlock deep-sleep entry, as results it allows to put PSoC6 in to deep-sleep when CYW43xx does not expect this (the host_wake_up pin in ACTIVE_LOW state, which means hat host must be in ACTIVE mode ). Now, CYW43XXX Cordio HCI driver has the following MCU deep-sleep locking scenarios/flows: a) A BT device or MCU does not support Low Power mode (MBED configuration does not include MBED_TICKLESS, DEVICE_SLEEP, DEVICE_LPTICKER or CYCFG_BT_LP_ENABLED features). In this case, CyH4TransportDriver locks deep-sleep in the initialize() function and unlocks the terminate() function. b) A BT device and MCU support Low Power mode. In this case, the control of the unlock/lock of the deep-sleep functionality will be done in bt_host_wake_rise_irq_handler and bt_host_wake_fall_irq_handler handlers. Finally, CyH4TransportDriver unlocks the deep-sleep in terminate() function (if it was locked before) by checking the bt_host_wake_active flag. Fixes ARMmbed#13076, ARMmbed#13700, ARMmbed#13295.
Description of defect
The following test result in FAIL with
CY8CKIT_062S2_43012
andMbed OS 6.0
.See full test summaries:
CY8CKIT_062S2_43012_GCC_ARM_results.txt
CY8CKIT_062S2_43012_ARM_results.txt
Target(s) affected by this defect ?
CY8CKIT_062S2_43012
Toolchain(s) (name and version) displaying this defect ?
GCC Arm compiler 9
Arm compiler 6
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.0.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.1
mbed-cloud-sdk 2.0.8
mbed-flasher 0.10.1
mbed-greentea 1.7.4
mbed-host-tests 1.5.10
mbed-ls 1.7.10
mbed-os-tools 0.0.12
full list of python packages
How is this defect reproduced ?
The text was updated successfully, but these errors were encountered: