-
Notifications
You must be signed in to change notification settings - Fork 3k
Release candidate for mbed-os-5.5.4 #4824
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
Conversation
Signal wait was always returning success even in case of error.
…y at startup regardless of the value set in the constructor. Issue #3863
When disabling GPIO irq, also the falling / rising edge settings need to be reset (EXTI_RTSR and EXTI_FTSR registers). If not reset, the same EXTI line can be later enabled again with a wrong Rising / Falling configuration. This was especially seen and reported in ci-test tests-api-interruptin on NUCLEO_F446RE target where DIO2=PA_10 and DIO6=PB_10 were successively tested: as they are sharing the same EXTI_LINE (EXTI_10), this resulted in calling the irq_handler with wrong IRQ_FALL/IRQ_RAISE parameter and donothing being called in loop.
In case we've run through the entire GPIOs loop, withouth finding a matching interrupt, we're in the case of a spurious interrupt, let's raise an error to track it down.
Now that rising / falling edge detection is disabled in the gpio_irq_disable function, we also need to restore it when gpio_irq_enable gets called.
Set copy_method and reset_method in targets.json which is needed for htrun.
Partially reverts 2ddf4b3
The subtlety of where to mark functions as weak created an issue for at least one user, so added a warning in the documentation.
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 101 All exports and builds passed! |
@studavekar No examples were compiled, that's why it finished so fast. |
@theotherjimmy looks like exporter is returning an empty set for targets
|
see #4837 |
/morph test-nightly |
/morph mbed2-release |
/morph export-build |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputBuild failed! |
776ed10
to
c511e96
Compare
Result: ABORTEDYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 106 Exporter Build failed! |
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
/morph mbed2-release |
/morph test-nightly |
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 108 All exports and builds passed! |
@0xc0170 Update examples time! |
No description provided.