We are pleased to announce the mbed OS 5.4.3 release is now available. This release includes new target support for nRf52840 and UBLOX_C030. There are also a number of bug fixes to improve the stability of the code and improvements to the tools.
Here is a full list of all changes and fixes in this release...
The following list of known issues apply to this release:
Ports for Upcoming Targets
Fixes and Changes
- 3951: [NUCLEO_F303ZE] Correct ARDUINO pin
- 4021: Fixing a macro to detect when RTOS was in use for the NRF52840_DK
- 3979: KW24D: Add missing SPI defines and Arduino connector definitions
- 3990: UBLOX_C027: construct a ticker-based wait, rather than calling wait_ms(), in the
- 4000: Add some type checking of configs
- 4003: Fixed OBOE in async serial tx for NRF52 target, fixes #4002
- 4012: STM32: Correct I2C master error handling
- 4020: NUCLEO_L011K4 remove unsupported tool chain files
- 4046: USBHOST : fix device disconnection from hub during hub port reset
- 4049: tools - turn off page alignment of sections
- 4065: K66F: Move bss section to m_data_2 Section
- 4014: Issue 3763: Reduce heap allocation in the GCC linker file
- 4030: [STM32L0] reduce IAR heap and stack size for small targets
- 4060: lpc1768: Remove invalid use of IP_SOF_BROADCAST_RECV option
- 4070: Elide adding regions to profile when empty
- 4072: Removed superfluous space
- 4085: Fix mbed-cli issue #468. Add LPCTargetCode.lpc_patch to POST_BINARY_WHITELIST
- 4101: Modify semihost_disabledebug() to support more interface FW revs
- 4109: NUCLEO_L476RG : minor serial pin update
- 3911: IAR exporter: extended debugger settings template with modifiable options needed for Nordic targets
- 3982: Ticker - kl25z bugfix for handling events in the past
- 4112: Only link in LPC17xx ethernet ISR as needed
- 4098: Raise error when mbed_app.json is bad
Using the release
You can fetch the mbed OS 5.4.3 release from the mbed-os GitHub repository, using the tag "mbed-os-5.4.3". Please feel free to ask any questions or provide feedback on this release here, or to contact us at email@example.com.
Please log in to start a discussion or ask a question.