Release candidate for mbed-os-5.9.1 #7228
Conversation
|
/morph build |
|
/morph mbed2-release |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputBuild failed! |
Build : SUCCESSBuild number : 2354 Triggering tests/morph test |
Referencing to "UG257: EFM32 Pearl Gecko PG12 Starter Kit User's Guide - Chapter 4" (https://www.silabs.com/documents/public/user-guides/ug257-stk3402-usersguide.pdf) it should be like in this commit.
* Updated pinout of EXP header from pre-production to production * Move assignment of PF7 to SPI_2 to be compatible with the new SPI flash routing
* Since mbed does not overwrite itself, make the flashing routines run out of flash by default * Report a writeable size of 4 bytes (previously erroneously reported a full eraseable page as the minimum write size)
* IRQ handling got updated previously to a non-functional state when both callbacks were registered (it'd fire a fall callback for both rise and fall events). With this update, that faulty behaviour is corrected. Due to delays between the detection of the edge and the handling of the interrupt (and the fact that information about which edge you received on the pin is not stored anywhere), there is no way to be absolutely sure which edge got triggered on the pin. Therefore, we make a best-guess effort by looking at the pin state at the time of IRQ handling, and fire a callback as if that was the end state of the event. This will usually work out fine, except in cases were the signal is toggling faster than the IRQ handler's response time. In that case, a user won't get both callbacks (as expected for a pulse), but only the last event. * Stripped some dead code.
I fixed redeclaration of type name "bool_t" for target Renesas because this typedef has been defined in rtx_core_ca.h by #6273.
- Set network stack to store event queue so that mbed::mbed_event_queue() call is not needed every time call_in() is called - Added dns state variables and enum (states are: created, initiated and cancelled) - Corrected DNS response handling so that if DNS server returns that host name is unknown the DNS query is not tried again - Reorder mutexes in nsapi_dns_query_multiple_async() - Created nsapi_dns_query_async_initiate_next() function to initiate the next DNS query from the queue after delete of previous query - Added dsn_timer_running variable to supervise DNS timer start/stop - Changed cancel function to only mark query as deleted and moved deletion to timer function. This allows to run socket close on DNS thread - Added new nsapi error NSAPI_ERROR_TIMEOUT for DNS (and other) timeouts
Considers both versions - synchronous and asynchronous. Earlier the underlying stack was trusted to do this check.
This LoRaRadio test set adds basic tests which can be run with a single HW.
After rtc_free, RTC gets inaccessible from CPU domain but keeps counting.
Ensure the SysTimer isn't added to the timer list twice by adding an extra call to remove() inside suspend().
This API allocates a program buffer of 256 on the stack to ensure alignment. However, FlashIAP driver already ensures this alignment of the user data.
Prevents ticker upper layer initialization during test execution
Increases tolerance value for sleep_usticker_test to cover extra time needed for cpu stats computation (for more details see MBED_CPU_STATS_ENABLED). Prevent scheduling interrupt during ticker initialization (in lp_ticker_init) while test execution.
When all TX descriptors were reserved in a row so that TX buffer reclaim interrupt did not happen during reservation sequence, after the interrupt occurred, TX buffer reclaim did no longer free buffers. This happened because when all descriptors were in use, last free index pointed to consumed index.
adbridge
force-pushed
the
release-candidate
branch
from
b7392c6 to
92a4cb2
Compare
|
/morph build |
|
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Build : SUCCESSBuild number : 2355 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1978 |
Test : SUCCESSBuild number : 2140 |
Exporter Build : SUCCESSBuild number : 1979 |
Test : FAILUREBuild number : 2141 |
|
/morph test |
Test : FAILUREBuild number : 2142 |
|
Something odd happened with the NUCLEO_F429ZI devices. They've been power cycled. /morph build |
|
Damn it, meant for that to be a test, not build... |
Build : SUCCESSBuild number : 2356 Triggering tests/morph test |
Test : SUCCESSBuild number : 2143 |
Exporter Build : SUCCESSBuild number : 1980 |
No description provided.