The current Maxim BLE driver only implements the old BLE API
which is deprecated and will be removed soon. Once an updated
BLE stack for Maxim becomes available, BLE feature can be
re-enabled.
set_ip_address API can be used to set a static IPv4 address or IPv6 link-local
address to network stack.
This is needed for example in cellular use cases where device gets multiple IP
addresses from cellular context.
cc03296c27 Merge branch 'release_internal' into release_external
59397d17c4 Fixed Wi-SUN border router restart after settings change
8295a43668 PAE authenticator TLS authentication limit based on dynamic value
2776cfef50 RPL config update not re-start whole BR again just increment version number and with new parameters.
bec4d48946 Fixed FHSS testing now it follow configured channel count not a wi-sun configured Default.
b9cad9d362 Remove floating point literals from Thread code
423a48f48b RPL link etx validation update
git-subtree-dir: features/nanostack/sal-stack-nanostack
git-subtree-split: cc03296c27fbe26663182d90586e2d31f140e300
This change adds 'sectors' configuration option into 'targets.json' to enable bootloader for Nuvoton targets.
Though 'arm_pack_manager/index.json' has `sectors` available, Nuvoton's cmsis pack 'Nuvoton.NuMicro_DFP.pdsc' doesn't have 'sectors' entries and they must add into `index.json` manually. But not apply to all chip subfamilies.
To support custom board which uses a different chip subfamily, add 'secotors' into 'targets.json' for all Nuvoton targets which enable Flash IAP.
Rework TDBStore::calc_area_params so that it can handle situations where
the block device size is not an even multiple of the sector size (while
retaining its ability to handle non-uniform erase sizes).
This avoids intermittent asserts on boards where TDBStore is implemented
in internal flash, in which case the size of the block device varies
with the application size and a minor change (or a shift in optimization
level) can shift TDBStore from an odd to an even number of sectors.
Issue: The problem is that there is a race condition introduced in that the LWIP thread is relying on the
interface as it is taken down by a application thread while calling disconnect.
In disconnect api called from application context, whd_emac_wifi_link_state_changed() will refer to netif interface
structure in its callback api netif_link_irq(netif). This netif will be cleared by remove_etherent_interface().
whd_emac_wifi_link_state_changed will post message to tcpip_thread. tcpip_thread will process the message and
call the callback api netif_link_irq(netif)
Calling sequence is whd_emac_wifi_link_state_changed -> remove_etherent_interface(). Hence there is a timing issue
that netif might be cleared first before tcpip thread process the message netif_link_irq(netif)
Fix: remove_etherent_interface() will post message to tcpip thread and tcpip thread process the message delete_interface()
which will actually remove the inferface from the netif_list.
Calling sequence is whd_emac_wifi_link_state_changed() message post -> remove_etherent_interface() message post.
message processing order netif_link_irq(netif) -> delete_interface().
Since both the processing is handled in single thread, processing of message is handled sequentially.
Lingkai Dong
jeromecoutant
Martin Kojtal
Rajkumar Kanagaraj
Kimmo Vaisanen
Arto Kinnunen
Chun-Chieh Li
Kyle Kearney
George Beckstein
Arun S
Yoshihiro TSUBOI
MarceloSalazar