Release candidate for mbed-os-5.9.2 #7375
Conversation
|
/morph build |
|
/morph mbed2-release |
Build : FAILUREBuild number : 2479 |
Build : FAILUREBuild number : 2480 |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
|
Looks like we have genuine failures for some BLE tests for targets : |
Fixes one error: IOTCLT-2638 Hardfault during reconnection retry with Thread
Previously get_mac_address on a ThreadInterface returned the EUI-64 reported by the radio driver. This was required for commissioning, but was inconsistent with other interfaces, and the API concept. 5.9.0 inadvertently changed this so that get_mac_address returned the actual MAC address used by the radio, which is a hash result of the EUI-64 for Thread. The original "return the EUI-64" form was somewhat faulty, as get_mac_address would not return the EUI-64 set by set_device_eui64() or another mechanism before connect() was called. Rather than revert to old behaviour, add a new API to get the device EUI-64 to ThreadInterface, alongside the existing set API.
Test echoes 50000 random length ethernet frames between CTP echo server and device.
1. Problems were seen on the LPC54628 as the ADC clock source was too high 2. Moved the pin configuration to set Analog mode to the end of the function Signed-off-by: Mahesh Mahadevan <[email protected]>
A peer device that sends a connection parameter update may get block if it doesn't receive a response. This patch accept the peer request unconditionnally. At some point this event will be managed by the application.
No need for driver level hardware IPv4/TCP/UDP/ICMP checksum insertion since LWIP and nanostack handles those already. Related to issue: #7227
"aes.c" file name conflict in Maxim platform and mbedtls.
This saves memory on platforms without network interface.
Original wait time is not enough for UART to flush out before deepsleep on some targets.
Code was written using MBED_CONF_DEFAULT_* but the mbed_lib.json file that created these values is prefixed with "nsapi" and therefore final macros are MBED_CONF_NSAPI_DEFAULT_*
This commit fixes the issue reported in #7285. If the radio is unable to transmit, its a fatal error and can happen both while joining or sending a normal packet. In the case of such a catastrophy we ought to tell the application that this happened. A fix for the radio driver will also be patched.
In serial_tx_active and serial_rx_active functions, we check the internal state value with HAL_UART_STATE_BUSY_TX = 0x21U, HAL_UART_STATE_BUSY_RX = 0x22U, It seems that value can also be : HAL_UART_STATE_BUSY_TX_RX = 0x23U,
It has been noticed that there is a problem with us ticker on NRF_52840 board after 32 bit counter has been used for us ticker on NRF52 family boards. Currently NRF52 symbol is defined only for MCU_NRF52832 (not for MCU_NRF52840) and based on this symbol 16 or 32 bit counter is selected (16 bit for NRF51 family and 32 for NRF52 family). Since MCU_NRF52840 defines NRF52840_XXAA and provides 32 bit counters, 32 bit counter should be selected also when NRF52840_XXAA symbol is defined.
adbridge
force-pushed
the
release-candidate
branch
from
14b8b2e to
a2d763f
Compare
|
Regenerated without the offending BLE test update. |
Build : SUCCESSBuild number : 2481 Triggering tests/morph test |
Test : SUCCESSBuild number : 2256 |
Exporter Build : FAILUREBuild number : 2118 |
|
If only Jenkins CI nodes would stop leaving... /morph export-build |
Exporter Build : FAILUREBuild number : 2119 |
|
Third time's the charm? |
Exporter Build : SUCCESSBuild number : 2120 |
No description provided.